Used to model how a combination of conditions should lead to a certain action
A table can also have values other than true or false, such as numbers.
With non boolean conditions the number of possible combinations becomes bigger.
In such cases it is better to use other strategies like pair-wise combinational testing
Keep conditions independent
Use DC values when possible
Variants with DC values should not overlap
Add a default column
Consider non boolean conditions if conditions are mutually exclusive
If most conditions are non-boolean, consider using a different combinational testing technique