Decision Table Testing

Great job on starting a new lesson! After reading this lesson, click Next 👉 button at bottom right to continue to the next lesson.

Decision table testing is a technique to test software by using a table to represent the combinations of inputs and expected outputs (actions ) of a software feature. You test using each column of the table and validate if each output is present. You test if the software works correctly with different logic and rules. Decision table testing is typically used to test software requirements, with a large number of conditions.

Decision Table Testing Examples

• You test a login feature. You create a table to show the combinations of username, password, and login status. You test each column of the table and validate if the action is correct.
• You test a money transfer feature. You use a table to show the combinations of account approval, OTP match, sufficient balance, and transfer status. You test each column of the table and test the actions.
• You test a flight booking feature. You use a table that has the combinations of destination, date, availability, and booking status. You test each column of the table and test the actions.
• You test a calculator feature. You create a table with the combinations of numbers, operators, and results. You test each column of the table and validate the output in each column.

Tips for Decision Table Testing

• Use different test techniques to identify the input conditions and output actions, such as equivalence partitioning, boundary value analysis, etc.
• Test both valid and invalid combinations to test how the software handles them.
• Test the relevant feature of the software that depends on the input conditions.
• Use appropriate tools to automate the testing tasks, such as generating test inputs, generating combinations of test inputs, executing tests, and reporting results.

FAQ (interview questions and answers)

1. What is the purpose of decision table testing?
   The purpose of decision table testing is to test complex business logic and rules by using a tabular representation of test inputs and action outputs.
2. What is the advantage of decision table testing?
   It simplifies the tests by showing all possible combinations in a clear and concise way.
3. What are the challenges of decision table testing?
   It can be difficult to create and maintain decision tables for large and complex software requirements, such as nested requirements or nested exceptions. It can be hard to trace the test cases back to the requirements.
4. Is decision table testing a type of black-box testing?
   Yes, it is a technique that tests the software without leveraging the knowledge of its code or structure.

Remember to just comment if you have any doubts or queries.