I'm not really sure how my prof managed to make it so that boundary value testing seemed like the hardest thing ever, it is pretty simple after all :D Thank you
@atiyawarsi111 - Yes, this video is not on current affairs or celebrity news. It explains the timeless techniques of equivalence classes and boundary values.
I was really confused before seeing this video but after seeing your video my mind is fresh I can understand concepts easily and clearly thank you so much
Hello from Ukraine. Thank you very much. You have helped me understand these test design techniques. I’ll try to watch all your videos, and thank you again.
Yet another awesome video. The first time I get to enjoy and thoroughly understand EP and BVA after a series of work related seminars on them! Thank you!
the explanation is so clear that i would never forget the concept throughout my career... very well executed.. simple language.. simple examples... awesome flow of explanation..
Thanks for the video. A single comment: At 0:47 unit testing is characterized as white box testing. I would say that UTs should be black box tests, as testing to the interface (rather than the implementation) of the unit allows the unit to be refactored as necessary and the existing test suite to be used to validate the refactoring.
Thanks for your comment but I disagree to an extent. It is feasible to look within the unit in unit testing because, by definition, a unit is the smallest logical set of code. In white box unit testing, we can test the unit providing input test data to test each statement, each branch and each path within the code. If unit testing is done as black box, we can miss interesting tests. E.g. let us say a class reads the application configuration file in a private method. Black box unit tests (that do not worry about the implementation) will not test what happens when the app configuration file is missing or locked by another process. Unit testing is done as black box testing as you have mentioned. That is called integration testing i.e. when we test only the interfaces of the units and do not worry about their implementation.
nileena dharan Hi Nileena, Actually, I wanted to provide multiple examples so that these test design concepts become very clear to the viewer. Also, the car example in my State Transition Testing turned out a bit complex :):) Thank you for your comment. Regards, Inder
Thanks for the reply.I have been in the Testing field for about 11 years,recently had to face a client evaluation which required brushing of the testing concepts. Your videos helped me thoroughly .Thank you once again.
i went to ISTQB foundation course and I left without understanding this, I passed the course bt BVA and EP I never understood. watching this video made thing so easy1 thank you
You are very welcome! There are other Test Design Technique tutorials , starting from Decision Table Testing (another awesome technique) at ua-cam.com/video/ED2iJXkdhCQ/v-deo.html&pp=iAQB
@Priti Jadhav - Thank you! This video is part of the Software Testing Tutorials playlist (more videos are being uploaded) at ua-cam.com/play/PLc3SzDYhhiGWuMK03uYO-UENAx0s2woWM.html
Thank you, Hema. You can view my remaining Test Design videos like Decision Table Testing, Use Case Testing etc. (with subtitles) at the link, ua-cam.com/video/ED2iJXkdhCQ/v-deo.html
Hey thank you for the video, easy examples, good way to explain the techniques, I hope you upload more videos with the rest of the techiques, regards from Mexico
Thank you, Ayusi. All other test design tutorials like decision table testing, use case testing etc. are at the link, ua-cam.com/video/ED2iJXkdhCQ/v-deo.html
Liliana Marian Glad that you liked this video. Thank you for your comment. You can find the videos on decision table testing and state transition testing in my Test Design playlist at ua-cam.com/play/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc.html
Many thanks, Cynthia. You may like my other two videos on test design techniques: - Decision Table Testing Explained with Examples at ua-cam.com/video/ED2iJXkdhCQ/v-deo.html - State Transition Testing at ua-cam.com/video/iQwn_jBQ39k/v-deo.html
Careful - in Equivalence partitioning you are not restricted to pick only one value from a partition. There may not be much use for more values, but you are not limited to one
Thank you for your suggestion. I have uploaded my video on Cohesion and Coupling (it is in my Programming Concepts playlist). The link of this video is ua-cam.com/video/lt_USS_B-jg/v-deo.html
Great video. Your '18 to 80 years EXCEPT 60 to 65 years' example has two equivalent, valid partitions. What boundary values do you choose? Do you choose boundary values for each of the two individual, valid partitions? Or, do you treat the two partitions as one combined partition and choose boundary values for that? Thanks.
Thanks for the appreciation! For this example, you should choose boundary values for each of the two individual valid partitions. For the valid partition 18 to 59 years, the boundary values would be 17,18,59 and 60. For the valid partition 66 to 80 years, the boundary values would be 65, 66, 80 and 81. These boundary values would also test the three invalid partitions, which are upto 17 years, 60 to 65 years and 81 years and above. Hope that I was clear in the above explanation!
+Omar Abood Actually, we can test with these inputs in a single test case. First, we can test with the invalid inputs (0, 32). Then, test with one valid input (28). I have explained writing such a test case in my video "How to write effective test cases quickly" at ua-cam.com/video/-VvQKEvsPpE/v-deo.html
Are you picking an actual value and placing it in the test data for a test case, or are you giving the partitions in the test data and just allowing the tester to pick for themselves?
Hi Christopher, any value in a specific partition can be the input test data for a test case. But, it is important to test each valid as well as invalid partition. The tester can pick any value in each partition.
But to clarify for example for the test case for valid input for the 1 to 30 date field example, in the test data do you say "any value from 1 to 30" or do you pick a random one and put say "5". I just wondering because if you just put "5", every time the tester runs that test case they will always use "5". I hope this makes sense. Thanks in advance!
@shambhavi Sidgiddi - You are welcome to the Software and Testing Training channel. Next, you can view the Decision Table Testing, Use Case Testing tutorials etc. at ua-cam.com/video/ED2iJXkdhCQ/v-deo.html
shirshendu ghosh Thank you, Shirshendu. You may like my other videos in my Test Design playlist at ua-cam.com/play/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc.html
Hi Monika, the same testing techniques are used for white box testing. For example, when I unit test my code, I use Equivalence Partition testing to test each input class. And Boundary Value Analysis to test the inputs at both sides of the boundary.
it is just absolutly awsum.. i hav a ques that when we use s/w testing Techniques EP and BVA ... means likes before writing test case or after...or somewhere else......and after EP and BVA what we do next..??
EP and BVA give us the test data that we should use in our test cases. E.g. If our test case has a test step, "Enter a date in the date field." We can apply EP and BVA. Then we can execute our test case with the values of Date=0,1,31,32. This means that we execute our test case 4 times, one for each date value.
irek garg Ideally, yes, we write down the test cases after performing EP/ BVA because EP/ BVA are test design techniques. It is also possible that the written test cases do not give the test data to execute i.e. it is up to the tester to design the test data at test run time. In such a case, the tester can perform EP/ BVA at test run time to determine useful test data to find more defects. No, its not mandatory to perform EP/ BVA (second para above) before writing the test cases but advisable only.
+Omar Abood In a test case, we write the input data with which the test case would be run. We should include input data from each valid partition (the system should accept such input). Also, we should include input data from each invalid partition (the system should reject such input). E.g. in a test case for date, we can have input data as 0, 32 (invalid inputs) and 1, 28 (valid inputs). Thank you for your question.
Thank you for the examples and explanation. I have a question on the example of 0.1, 0.2…0.8, 0.9 Is 0.8 the boundary or lower than boundary between 0.8 and 0.9 ? How is it correct to define?
@Nataliia Nataliia - Thank you for your question regarding BVA example #3 at 8:00. Now, the valid partition is from 0.2 to 0.8. The 0.8 is lower than the boundary. The boundary lies between 0.8 and 0.9. This means that you should test on either side of this boundary i.e. test with 0.8 and 0.9 values. In order to define the boundary values, you may imagine a number line from -infinity to 0.0 to 0.2 to 0.8 to 0.9 and above, with step of 0.1. Then, you may visualize the invalid partitions, the valid partition and the boundaries between the partitions.
I am planning to build a teaching website this calendar year. At present, I have a blog (since 2009) with many software testing articles at inderpsingh.blogspot.com/
I'm not really sure how my prof managed to make it so that boundary value testing seemed like the hardest thing ever, it is pretty simple after all :D Thank you
testing seemed like the toughest in class.Your video makes it simple and fun!Thankyou for uploading.
Thnku ur 9 y/o video is still helping future engineers
@atiyawarsi111 - Yes, this video is not on current affairs or celebrity news. It explains the timeless techniques of equivalence classes and boundary values.
I was really confused before seeing this video but after seeing your video my mind is fresh I can understand concepts easily and clearly thank you so much
Hello from Ukraine. Thank you very much. You have helped me understand these test design techniques. I’ll try to watch all your videos, and thank you again.
Thank you for your awesome comment 🙏 I have 9 videos on test design techniques at ua-cam.com/play/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc.html
Yet another awesome video. The first time I get to enjoy and thoroughly understand EP and BVA after a series of work related seminars on them! Thank you!
Thank you for your kind words. I am very glad that you liked this video. Inder.
the explanation is so clear that i would never forget the concept throughout my career... very well executed.. simple language.. simple examples... awesome flow of explanation..
Ayesha Chaurasia, thank you for your kind words.
Explained in a very easy way, really great , now i will always remember it.
Many thanks to you 😀. There are 8 other tutorials. You can view them at ua-cam.com/play/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc.html
This is incredibly useful. Thank you so much for this video. Great job explaining everything.
very clear and concise.... Very straight....Thank you sir...
@kivindra de silva - Thank you very much!
Thanks for the video. A single comment: At 0:47 unit testing is characterized as white box testing. I would say that UTs should be black box tests, as testing to the interface (rather than the implementation) of the unit allows the unit to be refactored as necessary and the existing test suite to be used to validate the refactoring.
Thanks for your comment but I disagree to an extent. It is feasible to look within the unit in unit testing because, by definition, a unit is the smallest logical set of code. In white box unit testing, we can test the unit providing input test data to test each statement, each branch and each path within the code. If unit testing is done as black box, we can miss interesting tests. E.g. let us say a class reads the application configuration file in a private method. Black box unit tests (that do not worry about the implementation) will not test what happens when the app configuration file is missing or locked by another process.
Unit testing is done as black box testing as you have mentioned. That is called integration testing i.e. when we test only the interfaces of the units and do not worry about their implementation.
Very clear explaination sir,Very Helpful thank you
Thanks for such a wonderful explanation
What a great and simple explanation. And with so many examples. Great video!
Beautifully explained...Thanks !!! Cleared all my doubts 🙂
Thank u so much . Very well explained
Truly Simple and highly Informative !! Thanks so much.
so confused how to say these concept in class,but after your video i got knowledge on it
Very useful information. I have watched all your videos in one go.It was quite a bite i must say.Please keep up the excellent work
nileena dharan Hi Nileena, Actually, I wanted to provide multiple examples so that these test design concepts become very clear to the viewer. Also, the car example in my State Transition Testing turned out a bit complex :):) Thank you for your comment. Regards, Inder
Thanks for the reply.I have been in the Testing field for about 11 years,recently had to face a client evaluation which required brushing of the testing concepts. Your videos helped me thoroughly .Thank you once again.
nileena dharan Glad that my videos were helpful. Thank you for the good words.
Useful...Thank u very much man..god bless u...
Clear explanation with good examples, thanks for the help!
i went to ISTQB foundation course and I left without understanding this, I passed the course bt BVA and EP I never understood. watching this video made thing so easy1 thank you
Mbalie Keswa Excellent. Please browse the other videos in my Test Design playlist too, like Use case testing.
this explanation is too clear. Thank you
Thank you, Priyanka :)
Great video with very clear examples. Thank you for making this.
Well done. It is really helpful and easy to understand.
Very well explained. I never forget the defenition of EP and BVA. Thank you
Most welcome!
I have understood very very clearly now.
@santhosh R S - Thank you. Check out my other Test Design tutorials at ua-cam.com/video/ED2iJXkdhCQ/v-deo.html
Very clear explanation sir Thank you
Very clear explaination sir. Thank u!!!
very helpful! Very well explained! Thanks!
Thank you sir❤it really helps to understand this concept.
You are very welcome! There are other Test Design Technique tutorials , starting from Decision Table Testing (another awesome technique) at ua-cam.com/video/ED2iJXkdhCQ/v-deo.html&pp=iAQB
Great video and clear and precise explanation. thank you sir!
thanks brother You are really great ... my teacher teach this lecture but i can;t understand
Thank you sir...it clear my doubts ...plz upload such more videos
Glad to know that it cleared your doubts. I recently uploaded more test design videos. Please view at ua-cam.com/video/ED2iJXkdhCQ/v-deo.html
Thanks you so much for the video.
Helps a lot to understand both the techniques better.
Reena, you are welcome :) Will upload more videos in the playlist named Test Design. Thank you.
That would be wonderful and also if you can help me with statement coverage, branch and decision coverage.
very nice explanation and thnks you
It's 2k23 still helpfull for students 💥 I found this and so easily I understood that concept 😊
@Priti Jadhav - Thank you! This video is part of the Software Testing Tutorials playlist (more videos are being uploaded) at ua-cam.com/play/PLc3SzDYhhiGWuMK03uYO-UENAx0s2woWM.html
very good explanation .
It helped a lot Thank you !
Wao. Intelligent 🧠
I found your definition very easy to understand...thankeu for the vedio....
tanu pal You can check out my other test design videos in my Test Design playlist. Thanks for your comment.
Thank you for explaining.really it was very much informative and easy sir.
Thank you, Bhanu Prakash. Regards, Inder P Singh
Very clear explaination sir. Thank u :)
jus amazin..!! video..!! one of the best one to easily understand EP & BVA
Thank you, Hema. You can view my remaining Test Design videos like Decision Table Testing, Use Case Testing etc. (with subtitles) at the link, ua-cam.com/video/ED2iJXkdhCQ/v-deo.html
great explanation. Thank You sir
Great explanation sir..thank u
Great job, dude. Keep making useful videos.
Hey thank you for the video, easy examples, good way to explain the techniques, I hope you upload more videos with the rest of the techiques, regards from Mexico
Hi Armando, many thanks for your comment. I gave multiple examples for better understanding. Will upload more videos. Best regards, Inder.
very nice explanation !
Thank you what seems hard to understand is clearly understood now.
Hi Ravi, you can find all my Test Design tutorials at the link, ua-cam.com/play/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc.html
very simple explanation thank you
HI Nelisiwe, glad that you liked this tutorial. You can see my other Test Design Techniques tutorials at ua-cam.com/video/ED2iJXkdhCQ/v-deo.html
Good Informative..it's very helpful to us
Thank you, Saranya.
Thank you sir video is very helpful.
Hi this was really useful!
Do you have tutorial for Statement testing and coverage? also understanding flow charts?
NICE very clear explanation
Very informative.. thanks👍
@Shubham Prasad - thanks for your comment 🙏
Very useful video. Thank you very much..
Vijay - you are very welcome.
Thank you. Very well explained.
Vernon Dias Thank you, Vernon.
Very good explanation...Thanks.
Thank you, Mark. Appreciate your comment.
Very good explanation....thank you
Thank you, Ayusi. All other test design tutorials like decision table testing, use case testing etc. are at the link, ua-cam.com/video/ED2iJXkdhCQ/v-deo.html
a very good explanation, thank you!
Liliana Marian Glad that you liked this video. Thank you for your comment. You can find the videos on decision table testing and state transition testing in my Test Design playlist at ua-cam.com/play/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc.html
Thanks man, Very precise and perfect; Once again thank you.
Hi Poorna, thank you for your kind comment. You can check out my four other Test Design tutorials at the link, ua-cam.com/video/ED2iJXkdhCQ/v-deo.html
Thank you for this! 💕
Thanks for the video. Great explanation!
Many thanks, Cynthia. You may like my other two videos on test design techniques:
- Decision Table Testing Explained with Examples at ua-cam.com/video/ED2iJXkdhCQ/v-deo.html
- State Transition Testing at ua-cam.com/video/iQwn_jBQ39k/v-deo.html
nice explanation, thank you so much!
Thank you very much for your useful video
Thank you, you are welcome :)
Very good explanation thank you
@soumya vatte - Other Test Design tutorials e.g. Decision Table Testing are available at ua-cam.com/video/ED2iJXkdhCQ/v-deo.html
Thank you
Very nice video !! Thank you sir ! :)
very nice video sir
thank you very much...
You are welcome, Majid.
Thanks a lot....u explained it very well..👍
Kunal, thank you.
Thank you so much sir
thanks and very helpful
Good Job!!!Awesome
Many thanks to you, Viji.
gud one sir, thank you
Great video, thank you!
Appreciate your like. You can see all my Test Design tutorials at the link, ua-cam.com/play/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc.html
Careful - in Equivalence partitioning you are not restricted to pick only one value from a partition. There may not be much use for more values, but you are not limited to one
Thankyou so much for this wonderfull vedio.
Swati, you are most welcome :)
Thank-you. Sir
Amazing plz upload Cohesion And coupling with examples..
Thank you for your suggestion. I have uploaded my video on Cohesion and Coupling (it is in my Programming Concepts playlist). The link of this video is ua-cam.com/video/lt_USS_B-jg/v-deo.html
very nicely explained
Thank you so much 🙂
Great explain sir
Awesome. There are 4 other Test Design techniques tutorials at the link, ua-cam.com/play/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc.html
THANK YOU!!
Clearly explained!
Great video. Your '18 to 80 years EXCEPT 60 to 65 years' example has two equivalent, valid partitions. What boundary values do you choose? Do you choose boundary values for each of the two individual, valid partitions? Or, do you treat the two partitions as one combined partition and choose boundary values for that? Thanks.
Thanks for the appreciation! For this example, you should choose boundary values for each of the two individual valid partitions. For the valid partition 18 to 59 years, the boundary values would be 17,18,59 and 60. For the valid partition 66 to 80 years, the boundary values would be 65, 66, 80 and 81. These boundary values would also test the three invalid partitions, which are upto 17 years, 60 to 65 years and 81 years and above. Hope that I was clear in the above explanation!
So if I understand you right, I will need to write 4 test cases to properly test a date field? Thank you for your prompt reply
+Omar Abood Actually, we can test with these inputs in a single test case. First, we can test with the invalid inputs (0, 32). Then, test with one valid input (28). I have explained writing such a test case in my video "How to write effective test cases quickly" at ua-cam.com/video/-VvQKEvsPpE/v-deo.html
Are you picking an actual value and placing it in the test data for a test case, or are you giving the partitions in the test data and just allowing the tester to pick for themselves?
Hi Christopher, any value in a specific partition can be the input test data for a test case. But, it is important to test each valid as well as invalid partition. The tester can pick any value in each partition.
But to clarify for example for the test case for valid input for the 1 to 30 date field example, in the test data do you say "any value from 1 to 30" or do you pick a random one and put say "5". I just wondering because if you just put "5", every time the tester runs that test case they will always use "5". I hope this makes sense. Thanks in advance!
Instead of hard-coding the test data, I prefer "Pick any integer value from 1 to the last date of that month".
Great thank you for the info and also for providing these videos they are a great help!
Appreciate your kind words.
Tysm sir.nice explanation
@shambhavi Sidgiddi - You are welcome to the Software and Testing Training channel. Next, you can view the Decision Table Testing, Use Case Testing tutorials etc. at ua-cam.com/video/ED2iJXkdhCQ/v-deo.html
Thanks sir
nice explanation sir
shirshendu ghosh Thank you, Shirshendu. You may like my other videos in my Test Design playlist at ua-cam.com/play/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc.html
thanks so lot! love you...
Many thanks. Do view my other Test Design tutorials at ua-cam.com/video/ED2iJXkdhCQ/v-deo.html&list=PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc&index=2
hi could you please also explain about white box testing techniques..i will be thankful...this video is very useful
Hi Monika, the same testing techniques are used for white box testing. For example, when I unit test my code, I use Equivalence Partition testing to test each input class. And Boundary Value Analysis to test the inputs at both sides of the boundary.
it is just absolutly awsum..
i hav a ques that when we use s/w testing Techniques EP and BVA ... means likes before writing test case or after...or somewhere else......and after EP and BVA what we do next..??
EP and BVA give us the test data that we should use in our test cases. E.g. If our test case has a test step, "Enter a date in the date field."
We can apply EP and BVA. Then we can execute our test case with the values of Date=0,1,31,32. This means that we execute our test case 4 times, one for each date value.
means aftr performing EP and BVA we write test cases..?? and its mandatory or not to perform EP and BVA before writing Test Case..??
irek garg
Ideally, yes, we write down the test cases after performing EP/ BVA because EP/ BVA are test design techniques.
It is also possible that the written test cases do not give the test data to execute i.e. it is up to the tester to design the test data at test run time. In such a case, the tester can perform EP/ BVA at test run time to determine useful test data to find more defects.
No, its not mandatory to perform EP/ BVA (second para above) before writing the test cases but advisable only.
thanks a lot.. :)
kindly provide me any contact detail so that i can ask any doubt to you in future..//
irek garg
Have sent you the contact details. Thank you for your subscription :)
Tq so much it was useful
Thanks, Arun
Thanks you sir
Thanks so much, i have a question here, how can i use this in writing a test cases? thanks
+Omar Abood In a test case, we write the input data with which the test case would be run. We should include input data from each valid partition (the system should accept such input). Also, we should include input data from each invalid partition (the system should reject such input). E.g. in a test case for date, we can have input data as 0, 32 (invalid inputs) and 1, 28 (valid inputs). Thank you for your question.
Greatness
Nice!
Explanation 👌👌👌👌
Thanks, @Madhavi Sriramineni :)
Thank you for the examples and explanation.
I have a question on the example of 0.1, 0.2…0.8, 0.9
Is 0.8 the boundary or lower than boundary between 0.8 and 0.9 ? How is it correct to define?
@Nataliia Nataliia - Thank you for your question regarding BVA example #3 at 8:00. Now, the valid partition is from 0.2 to 0.8. The 0.8 is lower than the boundary. The boundary lies between 0.8 and 0.9. This means that you should test on either side of this boundary i.e. test with 0.8 and 0.9 values. In order to define the boundary values, you may imagine a number line from -infinity to 0.0 to 0.2 to 0.8 to 0.9 and above, with step of 0.1. Then, you may visualize the invalid partitions, the valid partition and the boundaries between the partitions.
@@QA1 Hi there, I still could not understand. Is there any time you should explain the concept?
SUPER BRO . tnx from dublin.
Glad you liked this video. You can find all my Test Design videos at the link, ua-cam.com/play/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc.html
do u ve teaching website , so that we can enroll ..?
I am planning to build a teaching website this calendar year. At present, I have a blog (since 2009) with many software testing articles at inderpsingh.blogspot.com/