i. Decision table testing is black box test design technique to determine the test scenarios for complex business logic.

ii. Decision tables provide a systematic way of stating complex business rules, which is useful for developers as well as for testers.

iii. Decision tables can be used in test design whether or not they are used in specifications, as they help testers explore the effects of combinations of different inputs and other software states that must correctly implement business rules.

iv. It helps the developers to do a better job can also lead to better relationships with them.

v. Testing combinations can be a challenge, as the number of combinations can often be huge.

vi. Testing all combinations may be impractical if not impossible.

vii. We have to be satisfied with testing just a small subset of combinations but making the choice of which combinations to test and which to leave out is also important.

viii. If you do not have a systematic way of selecting combinations, an arbitrary subset will be used and this may well result in an ineffective test effort.

Importance of Decision Table:

Essentially it is a structured exercise to formulate requirements when dealing with complex business rules. Decision tables are used to model complicated logic. They can make it easy to see that all possible combinations of conditions have been considered and when conditions are missed, it is easy to see.