**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.
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..
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 :)
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..😊
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,
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..😊
@@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?
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
I think you are an incredible educator...thank you for sharing your gift...I appreciate everything you have made so much easier for me.
This was so helpful. I fully understand how to create and make sense of decision table testing. I wish you were my teacher! Thank you again.
Thank you for the video , this is the only valid tutorial on youtube for the decision table :)
**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.
Thanks for such clear instructions .
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..
Thank you for the example!
Thank you so much, great explanation!
You're very welcome! Keep watching and sharing.
Excellent explanation for beginners. Great job 👍
Simply THANK YOU
You're welcome!
Keep watching for more videos and tutorials.
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🙏
Thank you
Thank you sir
great 👍
Thanks for the visit
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 :)
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..😊
@@sravansran2109 wow thanks hey
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,
Please visit this full istqb foundation level playlist- ruclips.net/p/PLL34mf651faPON2szXlzCsTTYl3mh3s-T
@@softwaretestingmentor Thanks sir this is really helpful. This is still valid for 2022 exams right ?
How did you determine 8 columns are required?
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..😊
@@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?
Yes
could you explain why 8 columns? There was no explanation for that...
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
1.5x
OMG THANK YOU!
Thank you very much. Keep watching and sharing.