Software Testing Tutorial #36 - Decision Table Testing in Software Testing

Get all my courses for USD 5.99/Month - bit.ly/all-courses-subscription
In this Software Testing Tutorial, we will learn about decision table testing in software testing. Decision table testing is also known as the cause-effect table. Decision table testing is the software test design technique in a black box that is utilized for multiple outputs or on multiple conditions that are required to be tested.
🔸FREE Training's at training.rcvacademy.com 🔔SUBSCRIBE to CHANNEL: bit.ly/2YGU6JM
Help me in spreading the knowledge, please hit LIKE, SHARE, and SUBSCRIBE for the latest tutorials. More tutorial playlists below:
✅ ALL PLAYLISTS (Software Testing Mentor)🔸 / softwaretestingmentor
✅ ALL PLAYLISTS (RCV Academy)🔸 / @rcvacademy
✅ JIRA BEGINNER TUTORIAL🔸 bit.ly/jira-beginner-tutorial
✅ JIRA WORKFLOW TUTORIAL🔸 bit.ly/2EzKOEB
✅ JIRA ADMINISTRATION TUTORIAL🔸 bit.ly/36MPPFR
✅ JIRA TUTORIAL INTERMEDIATE🔸 bit.ly/Atlassian-JIRA-tutorials
✅ JIRA TUTORIALS🔸 bit.ly/jira-tutorials
✅ ZEPHYR TUTORIAL🔸 bit.ly/zephyr-for-jira-tutorials
✅ SOAPUI TUTORIAL🔸 bit.ly/Sopui-tutorial
✅ JSONPath TUTORIAL🔸 bit.ly/2sIZIFG
✅ POSTMAN TUTORIAL🔸 bit.ly/2PBbhI7
✅ ISTQB AGILE TESTER CERTIFICATION TUTORIAL🔸 bit.ly/istqb-agile-tester-cert...
✅ ISTQB FOUNDATION LEVEL CERTIFICATION TUTORIAL🔸 bit.ly/istqb-foundation-level-...
✅ CUCUMBER SELENIUM TUTORIAL🔸 bit.ly/cucumber-selenium-tutorial
✅ TESTRAIL TUTORIAL🔸 bit.ly/testrail-tutorial
✅ AGILE TUTORIALS🔸 bit.ly/agile-tutorials
✅ PYTHON TUTORIALS🔸 bit.ly/python-programming-tuto...
✅ PYTHON BEHAVE TUTORIALS🔸 bit.ly/python-behave-tutorial
✅ PRACTITEST TUTORIAL🔸 bit.ly/practitest-tutorial
✅ JAVA TUTORIAL🔸 bit.ly/2F1iL1B
✅ ZEPHYR TUTORIAL🔸 bit.ly/zephyr-for-jira-tutorials
🔶 ENROL IN MANY FREE TRAININGS ON RCV ACADEMY PORTAL 🔶
training.rcvacademy.com/
🔶 FOLLOW US ON TWITTER 🔶
/ rcvacademy
/ swtmentor
/ mrmverma
🔶 LIKE US ON FACEBOOK 🔶
/ softwaretestingmentor
/ rcvacademy47
🔶 OUR TUTORIAL WEBSITES 🔶
www.softwaretestingmentor.com
www.rcvacademy.com
🔶 GET MY TRAININGS ON UDEMY 🔶
www.udemy.com/user/manish68/
#SoftwareTestingTraining #SoftwareTestingTutorial #SoftwareTestingBootcamp #SoftwareTesting #QA #QATraining #QATutorials #RcvAcademy #SoftwareTestingMentor

[@hashcodehub6717]

Thank you for the video , this is the only valid tutorial on youtube for the decision table :)

[@estebanantonio2566]

Thank you for the example!

[@Newagetec]

Thanks for such clear instructions .

[@fluencycommunicationnonsto3242]

Excellent explanation for beginners. Great job 👍

[@RaviKumar-nz2lm]

Glass clear explanation...in single time i understood the topic after u explaining..wher as i couldn't able to follow multiple times listening others video on same topic..

[@NatashasVocals]

I think you are an incredible educator...thank you for sharing your gift...I appreciate everything you have made so much easier for me.

[@elnino61]

Thank you

[@gyanbaimishra9466]

Thank you sir

[@thabomoilwa6077]

Thank you so much, great explanation!

[@softwaretestingmentor]

You're very welcome! Keep watching and sharing.

[@ammygill9769]

Simply THANK YOU

[@softwaretestingmentor]

You're welcome! Keep watching for more videos and tutorials.

[@queendragonbee888]

OMG THANK YOU!

[@softwaretestingmentor]

Thank you very much. Keep watching and sharing.

[@manoj_mafiosi]

**Notes: Decision Table Testing in Software Testing - Software Testing Tutorial #36** **Introduction:** - Decision Table Testing, also known as Cause-Effect Table Testing, a crucial black-box testing technique for scenarios with multiple conditions. **Example: The Registration Portal Scenario:** - A registration portal with three mandatory fields: Name, Email, and Address. - The goal is to test the portal's success and error messages based on input values. **Creating the Decision Table:** - Use tools like Excel or Confluence to create a Decision Table. - Three input fields: Name, Email, and Address, resulting in eight possible combinations. **Decision Table Breakdown:** - **Scenario 1:** Name (Y), Email (Y), Address (Y) - Success Message: User should receive a success message. - Error Message: None. - **Scenario 2:** Name (N), Email (Y), Address (Y) - Success Message: None. - Error Message: "Name missing." - **Scenario 3:** Name (Y), Email (N), Address (Y) - Success Message: None. - Error Message: "Email missing." - **Scenario 4:** Name (Y), Email (Y), Address (N) - Success Message: None. - Error Message: "Address missing." - **Scenario 5:** Name (N), Email (N), Address (Y) - Success Message: None. - Error Message: "Name and Email missing." - **Scenario 6:** Name (N), Email (Y), Address (N) - Success Message: None. - Error Message: "Name and Address missing." - **Scenario 7:** Name (Y), Email (N), Address (N) - Success Message: None. - Error Message: "Email and Address missing." - **Scenario 8:** Name (N), Email (N), Address (N) - Success Message: None. - Error Message: "Name, Email, and Address missing." **Executing the Tests:** - Each scenario represents a specific test case. - Test each scenario with corresponding inputs and verify expected outcomes. - Error message text should match business requirements or specifications.

[@jeyhunaliyev1765]

great 👍

[@softwaretestingmentor]

Thanks for the visit

[@mollenruziwa8485]

I tried other channels, you explained this very well and now l understand thank you sir. Can you please do a tutorial on Collapsed DT🙏

[@kauserjaffari9790]

Hi Manish, greetings from Germany, amazing explanation can you elaborate how to reduce the test cases which has same output . Do you any example of collapsing the decision table thank you :)

[@sravansran2109]

hey kauser, in above example there are 3 conditions (name, email, address) then we conclude that there 8 possisble outputs (2^3=8), here 2 is sucessful message and error message (true/false)... In nutshell we can't reduce the output (test cases), for sure we need to test all the 8 testcases if it helpfull give me like..😊

[@mollenruziwa8485]

@@sravansran2109 wow thanks hey

[@ariana_1343]

How did you determine 8 columns are required?

[@sravansran2109]

In above example there are 3 conditions (name, email, address) then we conclude that there 8 possisble outputs (2^3=8), here 2 is sucessful message and error message (true/false)... if it helpfull give me like..😊

[@stephanieprolixity]

@@sravansran2109 ​ So, you just put 2 ^ of the number of however many conditions are defined and that’s how you verify how many combinations your table should display to make sure you covered everything?

[@ismailolalekan8160]

Yes

[@subhambhakat8494]

Hi sir, is there any playlist in your channel for learning different chapters for ISTQB testing exam (foundation level). I want to appear for the ISTQB exam but not able to find any suitable content. Please comment if you can help. Thanks,

[@softwaretestingmentor]

Please visit this full istqb foundation level playlist- kzbin.info/aero/PLL34mf651faPON2szXlzCsTTYl3mh3s-T

[@subhambhakat8494]

@@softwaretestingmentor Thanks sir this is really helpful. This is still valid for 2022 exams right ?

[@veliromn]

could you explain why 8 columns? There was no explanation for that...

[@simpledrawings3291]

Yes I was wondering the same thing. Please explain how you got the 8 columns?

[@sait5489]

There are 3 input conditions, Name, email, address, so there will be 2 power 3 . I.e 8columns will come. If there are 2 input conditions, 2 power 2 I.e 4 columns will come