Term
| What is Decision Table Testing? |
|
Definition
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. |
|
|
Term
| Example: How to make Decision Table for Upload Screen |
|
Definition
Consider a dialogue box which will ask the user to upload photo with certain conditions like –
You can upload only '.jpg' format image.
File size less than 32kb.
Resolution 137*177.
If any of the conditions fails, the system will throw corresponding error message stating the issue, and if all conditions are met, photo will be updated successfully. |
|
|
Term
| Why is Decision Table Testing is important? |
|
Definition
This testing technique becomes important when it is required to test different combination. It also helps in better test coverage for complex business logic.
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 the 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 n is 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. |
|
|
Term
| Why is Decision Table Testing is important? |
|
Definition
This testing technique becomes important when it is required to test different combination. It also helps in better test coverage for complex business logic.
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 the 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 n is 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. |
|
|
Term
| Advantages of Decision Table Testing |
|
Definition
When the system behavior is different for different input and not same for a range of inputs, both equivalent partitioning, and boundary value analysis won't help, but 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 a better coverage for testing.
Any complex business conditions can be easily turned into decision tables.
In a case where we are going for 100% coverage, typically when the input combinations are low, this technique can ensure the coverage. |
|
|
Term
| Advantages of Decision Table Testing |
|
Definition
When the system behavior is different for different input and not same for a range of inputs, both equivalent partitioning, and boundary value analysis won't help, but 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 a better coverage for testing.
Any complex business conditions can be easily turned into decision tables.
In a case where we are going for 100% coverage, typically when the input combinations are low, this technique can ensure the coverage. |
|
|
Term
| Disadvantages of Decision Table Testing |
|
Definition
| The main disadvantage is that when the number of input increases, the table will become more complex. |
|
|
