0% found this document useful (0 votes)
48 views

Decisiontable

ste

Uploaded by

Prathamesh Patil
Copyright
© © All Rights Reserved
Available Formats
Download as PDF or read online on Scribd
0% found this document useful (0 votes)
48 views

Decisiontable

ste

Uploaded by

Prathamesh Patil
Copyright
© © All Rights Reserved
Available Formats
Download as PDF or read online on Scribd
You are on page 1/ 8
10728, 217 Pat @ GURU99 Decision Table Testing (Example) Decision Table Testing (Example) By Thomas Hamilton @ Updated December 3, 2022 Decision table testing is a software testing technique used to test system behavior for different input combinations. This is a systematic approach where the different input combinations and their corresponding system behavior (Output) are captured in a tabular form. That is why it is also called as a Cause-Effect table where Cause and effects are captured for better test coverage. A Decision Table is a tabular representation of inputs versus rules/cases/test conditions. It is avery effective tool used for both complex software testing and requirements management. A decision table helps to check all possible combinations of conditions for testing and testers can also identify missed conditions easily. The conditions are indicated as True(T) and False(F) values. In this Decision Table Testing tutorial, you will learn: Gurupo SVOLT|_sowsy J tps Awww. gurs88.comisecision table-esting hil EXPLORE MORE a 18 110728, 217 Pat Decision Table Testing (Example) ' GURUS9.COM Let’s learn with an example. Example 1: How to make Decision Base Table for Login Screen Let’s create a decision table for a login screen. m The condition is simple if the user provides the correct username and password the user will be redirected to the homepage. If any of the input is wrong, an error message will be displayed. Conditions Rule 1 Rule2 Rule3 Rule4 Username (T/F) F T F T Password (T/F) F F T T Output (E/H) E E E H Intps:iiwww.guru88.comidecsiontableesing tml 218 10728, 217 Pat Decision Table Testing (Example) Legend: * T-Correct username/password F - Wrong username/password E - Error message is displayed H- Home screen is displayed Interpretation: * Case 1 - Username and password both were wrong. The user is shown an error message. * Case 2- Username was correct, but the password was wrong, The user is shown an error message. * Case 3- Username was wrong, but the password was correct, The user is shown an error message. * Case 4- Username and password both were correct, and the user navigated to the homepage While converting this to a test case, we can create 2 scenarios, * Enter the correct username and correct password and click on login, and the expected result will be the user should be navigated to the homepage And one from the below scenario tps sw. qu1s88.comidecision table-esting hil sre 10728, 217 Pat Decision Table Testing (Example) Enter wrong username and wrong password and click on login, and the expected result will be the user should get an error message Enter correct username and wrong password and click on login, and the expected result will be the user should get an error message Enter wrong username and correct password and click on login, and the expected result will be the user should get an error message As they essentially test the same rule. Example 2: How to make Decision Table for Upload Screen Now consider a dialogue box that will ask the user to upload a photo with certain conditions like - 1. You can upload only ‘jpg’ format image 2. file size less than 32kb 3. resolution 137*177. Ifany of the conditions fails the system will throw a corresponding error message stating the issue and if all conditions are met photo will be updated successfully Let’s create the decision table for this case. Conditions Casel Case2 Case 3 Case 4 Case 5 Case 6 Case7 Format SPE PE SPE IPS Not.jpg Not jpg Not .jpg si Lessthan Lessthan 1 any bessthan Lessthan ve 32kb —32kb ~ ~ 32kb—32kb ~ Not Not Not resolution 137°177 137°177 137°177 B77 137°177 137°177 137°177 Autont Phata Error Freer Frrar Frear Frrar Frear tps sw. qu1s88.comidecision table-esting hil 48 10728, 217 Pat Decision Table Testing (Example) resolution size sizeand for format for mismatch mismatch resolution format and format mismatch mismatch resolution and size mismatch mismatc For this condition, we can create 8 different test cases and ensure complete coverage based on the above table. 1, Upload a photo with format ‘jpg’, size less than 32kb and resolution 137*177 and click on upload. Expected result is Photo should upload successfully 2. Upload a photo with format ‘jpg? size less than 32kb and resolution not 137*177 and click on upload. Expected result is Error message resolution mismatch should be displayed 3. Upload a photo with format ‘jpg’, size more than 32kb and resolution 137*177 and click on upload. Expected result is Error message size mismatch should be displayed 4. Upload a photo with format ‘jpg’, size more than equal to 32kb and resolution not 137°177 and click on upload. Expected result is Error message size and resolution mismatch should be displayed 5. Upload a photo with format other than ‘jpg’ size less than 32kb and resolution 137*177 and click on upload, Expected result is Error message for format mismatch should be displayed 6. Upload a photo with format other than ‘jpg’ size less than 32kb and resolution not 137°177 and click on upload. Expected result is Error message format and resolution mismatch should be displayed 7. Upload a photo with format other than ‘jpg’, size more than 32kb and resolution 137°177 and click on upload. Expected result is Error message for format and size mismatch should be displayed 8. Upload a photo with format other than ‘jpg’, size more than 32kb and resolution not 137*177 and click on upload. Expected result is Error message for format, size and resolution mismatch should be displayed tps sw. qu1s88.comidecision table-esting hil 58 10728, 217 Pat Decision Table Testing (Example) Why Decision Table Testing is Important? Decision Table Testing is Important because it helps to test different combinations of conditions and provides better test coverage for complex business logic. When testing the behavior of a large set of inputs where system behavior differs with each set of inputs, decision table testing provides good coverage and the representation is simple so it is easy to interpret and use. In Software Engineering, boundary value and equivalent partition are other similar techniques used to ensure better coverage. They are used if the system shows the same behavior for a large set of inputs. However, in a system where for each set of input values the system behavior is different, boundary value and equivalent partitioning technique are not effective in ensuring good test coverage. In this case, decision table testing is a good option. This technique can make sure of good coverage, and the representation is simple so that it is easy to interpret and use. This table can be used as the reference for the requirement and for functionality development since it is easy to understand and cover all the combinations. The significance of this technique becomes immediately clear as the number of inputs increases. Number of possible Combinations is given by 2 * n , where nis the number of Inputs. For n= 10, which is very common in the web-based testing, having big input forms, the number of combinations will be 1024. Obviously, you cannot test all but you will choose a rich sub-set of the possible combinations using decision based testing technique. Advantages of Decision Table Testing * When the system behavior is different for different inputs and not the same for a range of inputs, both equivalent partitioning, and boundary value analysis won't help, but a decision table can be used. * The representation is simple so that it can be easily interpreted and is used for development and business as well. * This table will help to make effective combinations and can ensure better coverage for testing tps sw. qu1s88.comidecision table-esting hil oe 110/23, 2:17 PM. Decision Table Testing (Example) * Ina case we are going for 100% coverage typically when the input combinations are low, this technique can ensure the coverage. Disadvantages of Decision Table Testing The main disadvantage is that when the number of inputs increases the table will become more complex Decision Table Testing Video Click here if the video is not accessible You Might Like: © What is Software Testing? Definition * 7Principles of Software Testing with Examples © \-Madel in Software Testing © STLC (Software Testing Life Cycle) Phases, Entry, Exit Criteria © Manual Testing Tutorial: What is, Types, Concepts Intps:iiwww.guru88.comidecsiontableesing tml 78 ‘110728, 217 Pat Prev Report a Bug, About About Us Advertise with Us Write For Us Contact Us Career Suggestion SAP Career Suggestion Tool Software Testing as a Career Interesting eBook Blog Quiz SAP eBook Execute online Execute Java Online Execute Javascript Execute HTML Execute Python © Copyright - Guru99 2022 Disclaimer | ToS Intps:iiwww.guru88.comidecsiontableesing tml Decision Table Testing (Example) Next Privacy Policy | Affiliate

You might also like