1. Decision Table Based Testing
Vishv Talwar
Navdeep Kunwar
Deepjal Chhetri
Aarushi Garg
Aakash Sachdeva

2. Why Decision Table is important?
Decision table testing is black box test design technique to determine the test scenarios for complex business logic.
We can apply Equivalence Partitioning and Boundary Value Analysis techniques to only specific conditions or inputs.
Decision tables are very much helpful in test design technique – it helps testers to search the effects of combinations of different inputs. 

3. Steps to create a decision table with an example
Let’s take an example of a finance application, where users pay money – monthly Repayment or year wise (the term of loan). If user chooses both options, the system will create a negotiation between two. So, there are two conditions of the loan amount, mention in the given below table,

4. Next, recognize all of the combinations in “Yes” and “No” (In Table 2)
Next, recognize all of the combinations in “Yes” and “No” (In Table 2). In each column of two conditions mention “Yes” or “No”, user will get here four combinations (two to the power of the number of things to be combined).

5. In the next step, recognize the exact outcome for each combination (In Table 3). In this example, user can enter one or both of the two fields. Each combination is sometimes referred to as a step.

6. Advantage of decision table technique:
Any complex business flow can be easily converted into the test scenarios & test cases using this technique.
Such type of table are work iteratively, means the table created at the first iteration is used as input table for next tables. Such iteration can be carried out only if the initial table is unsatisfactory.
These tables guarantee that we consider every possible combination of condition values. This is known as its “completeness property”.

7. What is Decision Table Testing?
Decision Table Testing is a good way to deal with a combination of inputs, which produce different results. It helps reduce test effort in verifying each and every combinations of test data, at the same time ensuring complete coverage
Example: To understand the importance of Decision Table Making we will see an example, let's consider the behavior of Flight Button for different combinations of Fly From & Fly To.
Rule 1:When destination for both Fly From & Fly To are not set the Flight Icon is disabled. In the decision table, we register values False for Fly From & Fly To and the outcome would be False, which is Flights Button will be disabled. Likewise, you can decide different outcome for different situation

8. Rule 2: When Fly From destination is set but Fly to is not set, Flight button is disabled. Correspondingly, you register True for Fly from destination in the decision table, and the rest of the entries are false.
Rule 3: When Fly from destination is not set but Fly to destination is set, Flight button is disabled and you make entries in the decision table.
Rule 4: only when Fly to and Fly from destinations are set, Flights button is enabled and you make the corresponding entry in the decision table.

9. Decision Table testing for purchasing chemical

10. Decision table testing
A supermarket has a loyalty scheme that is offered to all customers. Loyalty card holders enjoy the benefits of either additional discounts on all purchases or the acquisition of loyalty points, which can be converted into vouchers for the supermarket or to equivalent points in schemes run by partners. Customer without a loyalty card receive an additional discount only if they spend more than $100 on any one visit to the store, otherwise only the special offers offered to all customers apply

11. Decision table testing
Rule 1
Rule 2
Rule 3
Rule 4
Conditions
Customer without loyalty card T F
Customer with loyalty card
Extra discount selected -
Spend > $100
Actions
No discount Y N
Extra discount
Loyalty points

12. Decision table testing
3rd Example (ATM Decision table
Rule 1
Rule 2
Rule 3
Rule 4
Rule 5
Conditions
User Inserts Valid Card F T
User Enters Valid PIN -
Three Invalid PINs attempted
Sufficient balance for the request
Actions
Reject Card Y N
Prompt to Reenter PIN
Eat the Card
Dispense Requested Cash