This guys explains really well, has a good english, the video quality and sound are good and saved me from reading really complicated related books. Thank you.
@QA110 жыл бұрын
Many thanks, Armando. You are welcome.
@jimmymemon3 жыл бұрын
People like you are the ones who really need to be appreciated and supported. I can not tell you, how thankful I am!! Teaching is not a joke!! I wish there was a way in this world where our universities could at least identify that whether a person with a white paper degree can teach or not!! Thank you so much!! God Bless you!!
@user-iv5pj2of5z9 жыл бұрын
very good explanation!!!!!! the best one in the internet I found. Thks very much!!!!
@chanpreets107 жыл бұрын
awesome...this actually fetched me 15 marks in my end semester exams..thanks a lot :)
@QA17 жыл бұрын
Good to know, well done.
@hungnguyen061610 жыл бұрын
Hey, you saved me. Im reading ISTQB foundation syllabus, but have no idea until I watched your video. Easy and clear. Many thanks from Vietnam.
@QA19 жыл бұрын
Glad that you liked this video. Thank you for your comment. Regards, Inder.
@paramjitbhuller59228 жыл бұрын
I have seen many videos but the way u teach is awesome.No doubt left
@QA18 жыл бұрын
Many thanks for your input.
@nooralqaoudjato92718 жыл бұрын
Thank you so much. Thanks to this video I have understood something that I couldn't get in class!
@hmshhmsh28647 жыл бұрын
best one in the internet I found. Thanks very much for this explain !!!!
@surendragokavarapu18507 жыл бұрын
Got in a single shot...Thank you very much for this video. And subscribed in a single view :)
@Muhammad-pk8fi4 жыл бұрын
Couldn't have explained any better. Thank you so much sir.
@adarsham18642 жыл бұрын
This video is heaven for me never thought I would be qa ...this video helped me lot .
@sunthar.c15957 жыл бұрын
Your sharing is very useful. Understood about Decision Table in a single view. Thank you.
@QA17 жыл бұрын
Good to know. All my test design videos are at the link, kzbin.info/aero/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc
@sunthar.c15957 жыл бұрын
Software and Testing Training Thanks again.. :)
@hanza693 жыл бұрын
Thank u so much. This was so clear and easy to understand
@QA13 жыл бұрын
@Hanza Eigal - Thank u for your comment!
@lilbiskit1237 жыл бұрын
Very good tutorial. Clearly explained and easily understandable . Thank you :)
@Muhammad-pk8fi5 жыл бұрын
Beautiful, Explained the entire lecture in 15 mins
@QA15 жыл бұрын
Many thanks for your comment.
@nageswararaogarine62462 жыл бұрын
Well Explained. I have been looking for these type video. Thanks a lot
@afrozshaik52743 жыл бұрын
Fabulous explaination sir I don't have words to say
@erickquintero71157 жыл бұрын
very helpful, when i heard the voice, and the accent is indian, I'm sure it is legit! good job!
@QA17 жыл бұрын
Thank you.
@manisharao43847 жыл бұрын
very good explanation sir..understood in one go...thank you sir.......
@lavie68447 жыл бұрын
it is very much helpful and a perfect video to get well known about it
@mukeshrai20047 жыл бұрын
4. what we use the following for critical applications 1. use case testing 2. decision table 3. state transition 4. multiple condition condition
@mapharifilter2784 жыл бұрын
I was struggling with decision table but know I am a master since I watched this
@QA14 жыл бұрын
Maphari - That is awesome :) Thanks for your sub. You may also like my Equivalence Partitioning and Boundary Value Analysis tutorial at kzbin.info/www/bejne/q6rHcqygprmGn9k
@ananddesh6 жыл бұрын
Hi, very nice video, one thing as we are not finally testing all possible combinations (with low risk), better mark these TCs with low priority. And keep all 8 combinations in Test Suite. For further iterations we can skip those testing. But I feel for 1st round, we should not skip mentioned TCs and test all combinations.
@QA16 жыл бұрын
Many thanks, Anand. In the library example, it may not be possible to test all condition combinations, depending on the system implementation. For example, If User is not registered, Oustanding Fees and Borrow Book controls may be disabled or hidden. Yes, in the email example, we should test all combinations.
@evitadsouza30744 жыл бұрын
this is just an awesome channel , so crisp and clear . Thankyouu
@QA14 жыл бұрын
@Evita D'SOUZA - Thank you for your comment.
@mahibalay7 жыл бұрын
I watched many videos on D T, but this video is awesome
@QA17 жыл бұрын
Many thanks, Mahesh. You may find my other Test Design tutorials e.g. Equivalence Partitioning, Boundary Value Analysis, Use Case Testing etc. useful. The link is kzbin.info/www/bejne/q6rHcqygprmGn9k
@faisalahmed94344 жыл бұрын
Thanks for clearing the concept!
@ElsayedAlhanafy8 жыл бұрын
Really clear explanation ... thanks a lot!!!
@TheVoyager344 жыл бұрын
Extremely clear and helpful explanation, thanks a lot!
@QA14 жыл бұрын
Many thanks for your comment and sub. All my Test Design tutorials are available in KZbin at kzbin.info/aero/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc
@poojanb35667 жыл бұрын
Thank u so much, Now i understood clearly...
@GrafMKristo10 ай бұрын
I don't get it. When you 10:59 say "It doesn't matter" - how is this supposed to affect number of cases? Do we still test all alternating values or just pick random of them?
@QA110 ай бұрын
Graf MKristo - "how is this supposed to affect number of cases?" You would get the number of cases after simplifying the decision table. If you continue viewing this video, you would see that there are 4 columns after simplification. That means that you would have 4 cases. When I say at 10:59 that "It doesn't matter", it is the first case. When testing that case, you would pick a random value (because the output doesn't depend on it) or that field may just be disabled or blank in your application.
@sadanandrajmane94264 жыл бұрын
Explanation was👏👏fab Thanks for the video
@QA14 жыл бұрын
@Sadanand Rajmane - many thanks. You can check all other Test Design tutorials at the link, kzbin.info/aero/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc
@arunss50023 жыл бұрын
Thanks man, This helped a lot.
@maqboolahmed32505 жыл бұрын
Very Helpfull for my SQA Paper !
@QA15 жыл бұрын
Awesome, thanks.
@annavasinevska27446 жыл бұрын
Great video and explanation, thank you so much. Also your answers to the questions in comments were helpful for me as well.
@QA16 жыл бұрын
That is awesome, Анна Гайда. FYI - all my Test Design tutorials are available at one place at the link, kzbin.info/aero/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc
@ሚሚ5 жыл бұрын
Another excellent video.
@thomasstarupjrgensen24946 жыл бұрын
Very good video, with clear explanation, thx very much.
@QA16 жыл бұрын
Many thanks, Thomas. Please see my Test Design Tutorials playlist at kzbin.info/www/bejne/q6rHcqygprmGn9k
@vaishnavichittoor80305 жыл бұрын
Amazing. Thank you!
@yawacheampong63074 жыл бұрын
very useful information shared. simplified lecture. Thanks
@kyawn51154 жыл бұрын
Great delivery!
@QA14 жыл бұрын
Thank you very much.
@jddbhfgwdfhfh Жыл бұрын
Best example and explanation
@QA1 Жыл бұрын
Anket Ambekar - Thank you for your comment! Please feel free to ask any questions related to software testing, development, DevOps etc. You can use my new Software Testing course (94 lessons) at inderpsingh.blogspot.com/p/software-testing-course.html
@KevinCastillo-hh1fn5 жыл бұрын
Very complete example :D, thanks for the video
@QA15 жыл бұрын
Kevin Castillo, you are welcome. Thank you.
@mohammedanik77647 жыл бұрын
very very helpful....thank you sir
@vinaykumarreddy58096 жыл бұрын
good work sir . Now got to know what decision table is exactly
@QA16 жыл бұрын
Thank you, GVK. My other Test Design tutorials like Equivalence Partitioning, Use Case Testing etc. are available at kzbin.info/www/bejne/q6rHcqygprmGn9k&list=PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc
@rishitech84019 жыл бұрын
nyc work plz write d book.....
@farookseeru38 жыл бұрын
wonderful. simple n crisp
@sasiniishara3582 ай бұрын
Thank you sir
@QA12 ай бұрын
All the best
@soniyamota65539 жыл бұрын
Thanks for sharing this video..It was of great help.can u pls share some videos or slides on how to solve decision table problems for ISTQB exam
@QA19 жыл бұрын
Soniya Mota Thank you for your comment. My videos on test design are meant to explain the techniques of Equivalence Partitioning, Boundary Value Analysis, Decision Tables and State Transitions.At present, I have no interest in the ISTQB exam so not planning to create any videos on the same. Thank you for liking this video.
@upekshawanniarachchi4021 Жыл бұрын
Well explained. Thank you.
@QA1 Жыл бұрын
@Upeksha Wanniarachchi - Thank you for your comment! If you want to solve software testing problems, participate in the polls regularly at www.youtube.com/@qa1/community
@kritichawla25878 жыл бұрын
Great video for foundation building. Could you explain the following: Consider time represented as hh:mm:ss. Valid time is 00:00:00 - 23:59:59. If times valid, they are added to be displayed. Draw decision table & generate test cases?
@QA18 жыл бұрын
Hi Kriti, thank you for your question. The decision tables document complicated logic. In your 24-hour time format, the test design technique that we can use is Equivalence Partitioning. There are three input data - hour, minute and seconds. For hour, there are two invalid partitions (-1,-2,...) and (24,25,...) and one valid partition (0 to 23). Similarly for minutes and seconds. Please see my video on Equivalence Partitioning at kzbin.info/www/bejne/q6rHcqygprmGn9k
@adebowaledollars14 жыл бұрын
@@QA1 thank you for this answer, I get confused on what technique to use in different scenarios, as I just started training to become a software tester.
@QA14 жыл бұрын
@adebowaledollars1 We can use Equivalence Partitioning and Boundary Value Analysis techniques in case some test data is valid and other test data is invalid. Decision Tables are useful when there are multiple conditions to consider. State Transition charts are useful when we know the different SUT states (and their inputs and outputs). You may check out all my Test Design Techniques tutorials at the link, kzbin.info/aero/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc
@adebowaledollars14 жыл бұрын
@@QA1 thank you for your reply. I'm happy I came across your page. Also, must I obtain a certification, e.g ISTQB?
@QA14 жыл бұрын
Sure. You can check out ISTQB Foundation Certification course at the affiliate link, www.eduonix.com/istqb-foundation-training-new/UHJvZHVjdC0xMjY4NTYw
@pranaykargutkar7 жыл бұрын
Easy to understand explanation...thank you Sir
@QA17 жыл бұрын
You are welcome, Pranay. Please find all my Test Design tutorials at the link, kzbin.info/aero/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc
@pranaykargutkar7 жыл бұрын
+Software and Testing Training .. I am already following you and watching all the tutorials. All of them are useful . I am new to this Industry and very much loving your explanations.
@naani553 жыл бұрын
thank you so much .. can you please upload video on orthogonal array testing
@QA13 жыл бұрын
Thank you for your suggestion. I uploaded the ORTHOGONAL ARRAY TESTING video at kzbin.info/www/bejne/r4mzi3-cp8eSgLc
@Daffh0999 жыл бұрын
Thank you. This was very clear and helpful.
@QA19 жыл бұрын
Daffodil Hines Glad that you found my video useful. Thank you for your support.
@mcanallyjess9 жыл бұрын
nice videos man. Makes my software testing course really easy. subbed and liked
@QA19 жыл бұрын
Jess McAnally Thank you so much.
@ClarionCaww5 жыл бұрын
Great work!
@erfanakhtarjahan78146 жыл бұрын
Thank you for the detailed explanation on Decision Table Testing. Just a query, is 'simplifying a decision table' also known as 'collapsed decision table'?
@QA16 жыл бұрын
Erfan, you are welcome to this channel. No, collapsed decision table is something else. That involves prioritizing the condition combinations (to focus on most likely conditions during testing).
@tanakaruzvidzo44509 жыл бұрын
very useful thank you!
@amanpreetsahdev54545 жыл бұрын
Your videos are awesome. God bless you. Cleared all doubts.
@QA15 жыл бұрын
Many thanks, Amanpreet. Next, you should practice making the decision table yourself. That would give you more confidence.
@amanpreetsahdev54545 жыл бұрын
@@QA1 Thanks Sir. Can you help me out with 1 advice. I have done my graduation and postgraduation in IT. Also have done GNIIT in past. But didn't pursue with that field. Worked as a Paralegal in KPO for 3 years after that was on break for 4 years due to maternity. Now want to resume my career in IT and that too for New Zealand or Canada. Can you please suggest can i make my career in IT without any prior experience and if yes in which domain? Will testing will be ok without any experience? And if yes which testing software? Manual testing or automation. I want something in which no coding should be needed.
@QA15 жыл бұрын
Hi, as you know, it is difficult to secure a job with any experience. You can see tips to get a job in software testing in my video at the link, kzbin.info/www/bejne/Z6nUlZyahrSBnK8
@QA15 жыл бұрын
Some technical skills or coding skills is needed in test automation. You can check out my Test Automation playlist (40 videos) at the link, kzbin.info/aero/PLc3SzDYhhiGXVcy8EcrTSfwsC-v8EUZvg
@amanpreetsahdev54545 жыл бұрын
Thanks a lot. God bless you 😊
@shreedharchavan70332 жыл бұрын
Its great that expected result give correct error in example 1, but there is one problem of security. For better security practices, we say "incorrect email or password" for every invalid input.
@QA12 жыл бұрын
It's a user experience design tradeoff that needs to be made. "Incorrect email or password" is more secure by hiding the exact error, but it is also more inconvenient to the user who has to check both the email and password for mistakes in submission.
@aapzehrsteurer90002 жыл бұрын
True, but also irrelevant for the topic at hand.
@diksha57469 жыл бұрын
Thank you!
@nadawalid690110 жыл бұрын
simple and clear explanation, really thank you
@QA110 жыл бұрын
Nada, glad that you liked this video. Thank you.
@venkykotta455210 жыл бұрын
Software and Testing Training Hell sir,Your videos are very helpful to me.Thank You Very Much.Could you please upload video on Testing Metrics?
@serunagasravanthi57609 жыл бұрын
its very very useful to learners
@QA19 жыл бұрын
Kommisetti Naga Sravanthi Thank you so much.
@serunagasravanthi57609 жыл бұрын
sir your videos gave me confidence
@serunagasravanthi57609 жыл бұрын
is there any speech regarding cause effective graph..
@kotlaganeshkumarreddy73864 жыл бұрын
Thank you so much sir.......
@punitgupta0710 жыл бұрын
Great work sir, solved all my problem
@QA110 жыл бұрын
Thank you, Punit. You may want to view the other test design videos, Equivalence Partitioning and Boundary Value Analysis at kzbin.info/www/bejne/q6rHcqygprmGn9k and State Transition Testing at kzbin.info/www/bejne/n4Lan5Kgd7Zmb80
@manojsaxena307010 ай бұрын
Very good explanation
@QA110 ай бұрын
Manoj, thanks! Best wishes, Inder P Singh
@poojanb35667 жыл бұрын
Thanks for ur response, if u explain me wid one more example means it vl helps me to understand it better. M searching for a job if i understand these concepts clearly means it vl be very usefull for me so plz....
@QA17 жыл бұрын
Earlier, I gave the example of email which had one Action (Expected Result). In the video, I have the second email example which has two Actions (Expected Result and Show Page). In the second example, consider the first three columns of the decision table. You will notice: a) Email is blank in these columns b) Password has the values of Blank, Invalid and Valid c) Expected Result is the same (Error: Please enter email) in these columns d) Show Page is same (Login Page). What does this mean? This means that Password can be any value (Blank, Invalid or Valid) but if the Email is Blank, we get the same Actions (Error: Please enter email) and the Login page is shown. This means that this decision table can be simplified by combining the first three columns into a single column with i) Email as Blank ii) Password as Don't Care or - iii) Expected Result as Error: Please enter email iv) Show Page as Login Page
@manojkumawatmanojbedwal7 жыл бұрын
Good explanation
@sushantlokhande36916 жыл бұрын
Sir ,I really like ur video.Plzzz Sir make the more videos on software testing concept. 1's again thnxxx👍👌
@QA16 жыл бұрын
Hi Sushant, thank you for your comment. Please check out my other Software Testing tutorials at kzbin.info/www/bejne/q6rHcqygprmGn9k
@Catch_the_picture Жыл бұрын
Thank you for sharing!!
@QA1 Жыл бұрын
Ema - Thank you for your subscription and wonderful comment 🙏
@nataliianataliia24422 жыл бұрын
Thank you for the examples with explanation! For ex., the test case title will stand for "Check if a user is registered, a user has no outstanding fees, a user is under borrow limit, the system allows to borrow a book". Is it ok?
@QA12 жыл бұрын
@Nataliia Nataliia - This is in continuation with the conversation on LinkedIn. Actually, you could create a table of User Types (User, Administrator) as columns and Actions as rows. Then put, Yes or No in the different cells. And no, the test case title is too long; it could be "Check if a user can borrow a book".
@nataliianataliia24422 жыл бұрын
@@QA1 thank you! Interesting Do you have examples with these roles? How can I find you on Facebook?
@QA12 жыл бұрын
@Nataliia Nataliia - I am not active on Facebook. You can message me on LinkedIn please. Thank you.
@QA12 жыл бұрын
My LinkedIn profile link is www.linkedin.com/in/inderpsingh/
@valanboonkaewkwan39596 жыл бұрын
Thank you very much. It's very helpful
@QA16 жыл бұрын
You are welcome. My other Test Design techniques tutorials are at kzbin.info/www/bejne/fmqYg4trr6t_maM&index=3&list=PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc
@srinavyasatyavarapu17563 жыл бұрын
Great . thank you 🙏
@QA13 жыл бұрын
@Srinavya Satyavarapu - A decision table is useful because it shows us the condition combinations in a systematic format. Please like share this tutorial, if possible. And thank you for your comment.
@mariummagdy43595 жыл бұрын
thank you so much
@praveenvk12903 жыл бұрын
Video was really good and easy to understand the concept clearly but in this video, second possibility of calculating the number of combinations was 2^no.of.combinations which was wrong. Actually it must be reverse i,e no.of.combinations^2
@QA13 жыл бұрын
Many thanks for your kind words! Could you let me know where exactly have I explained " 2^no.of.combinations"? In the first Email example, I said "2 ^ No. of True/ False conditions". Also, what is the reason of your formula, "no.of.combinations^2"?
@praveenvk12903 жыл бұрын
@@QA1 Hi Sir, at 3:32 minute of your video, you said that total no.of.combinations = 2^ no.of.combinations, as this is applicable only for 1st possibility of Email condition itself. If we consider 2nd possibility of same Email condition you took blank is also one of the input then total inputs are 3. So, now as per the above formula for total no.of.combinations will be 2^no.of.combinations i,e 2^3=8 combinations which so not correct. total no.of.combinations must be 3^ no.of.cobinations i,e 3^3=9. That's my opinion.Thanks
@QA13 жыл бұрын
@Praveen V K - Thanks for your reply with the timestamp! Basically, at 2:53 and 3:50, I mentioned that No. of combinations = No. of condition1 values * No. of condition2 values. That is the general formula that you should use to build your decision table. When I mentioned 3:32 No. of combinations = 2 ^ No. of True / False conditions, that is a special case where the values are binary (only two possible values e.g True or False, 0 or 1, absent or present). So, it is Not Applicable to 2nd example because there Email has 3 values (blank, valid and invalid) and Password too has the same 3 values. Another useful tool in testing combinations is Orthogonal Array. I think that you will like 😊 the tutorial at kzbin.info/www/bejne/r4mzi3-cp8eSgLc
@praveenvk12903 жыл бұрын
@@QA1 Thanks for your patience to reply. Now I got clarified with the concept.Thanks once again
@QA13 жыл бұрын
@Praveen V K - I am lucky to have a viewer like you who is serious about learning. Well done 👍 You are always welcome in Software and Testing Training channel - Inder P Singh
@suganyabasker47033 жыл бұрын
Thanks very useful
@QA13 жыл бұрын
@baskker b - Test Design Techniques: kzbin.info/aero/PLc3SzDYhhiGWW0TzISFKqAN_ic8DnZvVc
@mutantstargaming365 Жыл бұрын
Very nice bro
@monalibhattacharjee5479Ай бұрын
Very good good
@ingenuitysupersike28205 жыл бұрын
Grate Video very good explanation.I want to ask that what is the different between cause effect graph and decision table.Can some one answer??
@QA15 жыл бұрын
Many thanks. The first difference between Cause Effect graph and Decision table is the layout. The CE graph is in the shape of a fishbone which the Decision table is a set of rows and columns. Another difference is that the CE diagram needs brainstroming to come up with possible causes while the Decision table is more straightforward combination of conditions and actions. You can refer my tutorial on Cause and Effect Analysis at kzbin.info/www/bejne/ppbdiqGaqL5qiq8
@itscaesar.7946 жыл бұрын
Excellent explanation !! Thank u very much
@QA16 жыл бұрын
You are welcome. You may also like my Use Case Testing tutorials etc. at kzbin.info/www/bejne/fmqYg4trr6t_maM
@itscaesar.7946 жыл бұрын
I have watched that too !! thanx for that
@QA16 жыл бұрын
Thank you, TechGuy. Please check out my Test Automation tutorials on JMeter, LoadRunner, Selenium, programming concepts etc. at kzbin.info/aero/PLc3SzDYhhiGXVcy8EcrTSfwsC-v8EUZvg
@shweta27068 жыл бұрын
Thanks a lot .
@pragyajain61189 жыл бұрын
Its really helpful...
@QA19 жыл бұрын
pragya jain Thank you. Please subscribe for more videos on test design.
@g2k2434 жыл бұрын
Thank so much.
@QA14 жыл бұрын
You are welcome to my Software and Testing Training channel.
@janbiengabrielledaniel43536 жыл бұрын
Damnn .. simple but good !!
@MisterSkraetsch8 жыл бұрын
Thanks! :)
@sitatejovathi8 жыл бұрын
very nice!
@changchiayu128810 жыл бұрын
Thank you. You save me!
@QA110 жыл бұрын
Chang, you are welcome. Thank you for your comment :)
@trent24397 жыл бұрын
In the library example we simplified the Decision table. That's fine, there is no issue there from a logic perspective. But it appears that the Decision table, once simplified like this, does not explicitly and literally provide all the combinations that a tester will need to test. What I mean is that when we leave a field as "don't care", (i.e. a hyphen), it is up to the tester to create the test case where "don't care" is True, and then create a test case where "don't care" is False. In other words, the tester still has to write those explicit test cases. My point is that when we create and simplify the Decision table, there is in fact a certain level of interpretation required by the tester; i.e. the Decision table is not going to explicitly and literally provide each and every True and False value. Is my understanding correct?
@QA17 жыл бұрын
Hi Trent, thank you for taking the time to write this important point. Here is my reply. Let us take a step back. What is the use of a decision table? It is a way to document complicated logic. The decision table clarifies the requirements more accurately than just English sentences. That in itself is beneficial to the tester. Hitting only the simplified combinations (4 in the library example) takes less time than hitting all the combinations (8 in the library example) in the decision table. Further, if the user is not registered, they CANNOT borrow the book. The system should disallow entry of No outstanding Fees or Under borrow limit. So, there is no need of the tester entering True or False values for these two fields. In other words, the tester can just enter that the user is not registered and the system should immediately decide that they are not allowed to borrow a book. Hope this makes it clearer. Thank you. Inder
@trent24397 жыл бұрын
Hi Inder; Yes I agree with the logic. But the point of testing is to make sure the coding was done properly. So even if the "Registered" field is False, it's always possible that if the "Outstanding Fees" field is True, for example, that the result is they can borrow the book, because the Developer has not coded correctly. I mean, isn't that the purpose of testing; to ensure that the AUT performs as it should? That being said, perhaps what you are doing here is finding a balance between testing workload and risk. The risk being there was a defect and we did not catch it because we did not do the test case I mentioned in my example.
@QA17 жыл бұрын
Hi Trent, yes, the purpose of testing is to ensure that the AUT functions as it should. In the library example, if the user is not registered, the UI to set No outstanding fees and Under borrow limit should be DISABLED. If the AUT allows setting these last two flags despite an unregistered user, it a bug in the AUT UI design because it wastes user effort and gives false expectations to its function. In this video, I am NOT saying to run a subset of the test cases based on risk and constraints (that is a separate topic in test planning). The tests should cover ALL the combinations.
@trent24397 жыл бұрын
OK, good. Yes, the AUT should disable those other fields if the Registered field is false. I hadn't considered that was built in to the design of the app but of course that makes complete sense. Thanks.
@trent24397 жыл бұрын
Correction on my last comment: I made reference to *fields*. We're talking functionality here; nothing to do with fields. I was thinking about the actual cells of the Decision table instead of the AUT. lol.
@meghaj4094 жыл бұрын
Sir plzz make video on control flow testing : statement coverage path coverage etc ....And also on data flow testing: du path dc path etc ....Plz sir I realy need this
@QA13 жыл бұрын
@Megha Jain - Control Flow Testing is explained in Path Testing tutorial at kzbin.info/www/bejne/ql6mZHWqbMtkg5o Data Flow Testing tutorial is at kzbin.info/www/bejne/o5C3gmCgqMuFra8 Thank you.
@vibuthan2 жыл бұрын
Thank you
@ashishdhiman74795 жыл бұрын
very good explanation
@QA15 жыл бұрын
@Ashish Dhiman - Many thanks for your comment.
@prem6558 жыл бұрын
very nice
@rufimn5 жыл бұрын
Hello, Even though i know EP and BVA, i am confused to distinguish when to use EP, BVA and when to use Decision table. Let's say for e.g in the "Login" and "Password" example when we are testing different combinations of Login and Password, wouldn't we first test: 1/Login and Password input boxes using EP or BVA to first check if these accepts valid inputs AND THEN after we are satisfied that these two boxes only accepts inputs as per the requirements, we then check 2/Combinations of those inputs using Decision Table?? Please clarify. Thanks,
@QA15 жыл бұрын
Yes, we can. Or we can use the decision table, in order to first ensure that all test conditions are working. Then, use EP and BVA to design test data wherever we have to use a non-blank value (there are only 4 non-blank values out of 8 in that decision table). Thank you for your question.
@rufimn5 жыл бұрын
Thanks for clarifying. I think we should FIRST use EP or BVA to make sure our input fields do accept valid data and reject invalid data and then use DT... If we use EP or BVA after , we are not sure about our input fields data.. Makes sense ??? I didn't understand "There are only 4 non-blank values out of 8(There are 9 tc's) in that decision table"??? We have to design test data for 2 input fields "email" and "password" ??
@QA15 жыл бұрын
It is a decision to take the low-hanging fruit first or not. Testing the Email and Password fields fully needs many tests e.g. password needs to have min. number of characters. It also needs to have a combination of letters, digits and special characters, must not be one of the 3 previously used passwords or whatever other rules are present in the password policy followed by the system. Therefore, I would prefer testing the decision table conditions FIRST, because there are only 4 test conditions to test! Regarding your question, there are only 4 non-blank values (denoted by T or True in my Email Example decision table in my tutorial). F or False in that decision table implies that the tester does not provide an input. Thanks.
@rufimn5 жыл бұрын
Yup, that makes sense. But it also implies that passing or FAILING of EP/BVA testcases doesn't have any impact on DT testcases when DT cases are executed first ?? In other words, DT testcases are independent of the result of EP/BVA testcases for the same input fields?? Yes, now i got your point of 4 non-blank values. Btw, the min no of testcases or the no of testcases (to achieve full coverage) for a decision table doesn't depend on the number of conditions , rather the outcome of the conditions. For e.g 2 conditions(True or False) can give us 4 testcases to achieve full coverage and the same 2 conditions(Blank, Valid, Invalid) in your example can give us 9 testcases to achieve full coverage. Somewhere i read that it depends on the number of conditions , so if no of conditions are 3, its 2^3 = 8 min testcases to achieve coverage. Could you please clarify. Thanks :)
@rufimn5 жыл бұрын
Sometimes in the video i am lost, like for e.g, When you expand the Email and Password table to 9 testcases, can you apply the formula 2^ n here?? I didn't get this point because if we use the formula it will always give us even number of testcases and here we have 9??? Some logic is there where i am lost.
@kapilrana423510 жыл бұрын
thanks! this is relay helpful.
@QA110 жыл бұрын
Thank you, Kapil.
@sonalsingh83024 жыл бұрын
Great job 👍
@QA14 жыл бұрын
@Sonal - You are welcome to the Software and Testing Training channel. Regards, Inder
@srideviatkuri9807 жыл бұрын
Hello Sir, Will there be any pattern followed while mapping True or false for each condition to cover all permutations and combinations. Like for example .. if start with all False for Condition1 , and Condition2 with 1 true and rest all false .. etc this way.. Thank you
@QA17 жыл бұрын
Yes, there is a pattern. The first condition would alternate False and True. The second condition would alternate a couple of False values and a couple of True values. And so on. have explained it in the video so please view it again.
@bibingeorge78226 жыл бұрын
Superb ..
@QA16 жыл бұрын
Thank you. You may also like my Equivalence Partitioning and Boundary Value Analysis tutorial at kzbin.info/www/bejne/q6rHcqygprmGn9k
@MrPmandizzle10 жыл бұрын
when would you use a mix of both boundary value analysis and decision table based black-box testing?
@QA110 жыл бұрын
You can use both these test design techniques as applicable. In the email/ password example shown in this video, for example, we can use boundary value analysis on the the password test data. Let us say that the password has to be a minimum of 8 characters and a maximum of 20 characters. We can use a 7 character password and a 21 character password as invalid passwords. And use 8 character and 20 character passwords as valid passwords. Does this answer your question?
@abhishekamaurya58026 жыл бұрын
maja aa gaya sir thanks
@QA16 жыл бұрын
Welcome, Abhisheka.
@msraoswetha82509 жыл бұрын
Thank u sir ur clses very hlped me.
@QA19 жыл бұрын
msrao swetha Hi Swetha, many thanks for your comment. Please view my playlist with 5 hours of useful software testing videos at kzbin.info/aero/PLc3SzDYhhiGWuMK03uYO-UENAx0s2woWM
@msraoswetha82509 жыл бұрын
K sir i will see. Nd thank u
@msraoswetha82509 жыл бұрын
But sir didn't give me video cls about paths , path product Nd regular expressions.plz send me that video also
@msraoswetha82509 жыл бұрын
Hi sir.. I joined in the course. That is manual vth selenium course. So can u give me some suggitions for get job.pls sir its my request..
@QA19 жыл бұрын
msrao swetha If you joined the course at an institute, you could ask them if they can refer you to some test automation/ manual testing job opportunities. Thank you.
@bandipratima3 жыл бұрын
very helpful .Thank you
@QA13 жыл бұрын
Thank you 🙏 If you want to learn Structured Test Design/ White Box Testing, I have some new tutorials too, at kzbin.info/www/bejne/ql6mZHWqbMtkg5o
@josedavidrobles79015 жыл бұрын
How to determine number of combinations for decision table conditions? What if I have more than 3 conditions? Do I keep multiplying by 2 each time?
@QA15 жыл бұрын
I have mentioned the way to determine the No. of combinations in this tutorial. Basically, it is the product of all conditions' values. If there are, say, 4 binary conditions (True or False), it will be 2*2*2*2 = 16 conditions. Yes, you can keep multiplying by 2 each time there is an additional binary condition. Else, multiply by the number of values possible values e.g. 3 (Blank, Valid, Invalid) as in the Email example.