Decision table testing is based on the condition testing technique, but relies on the requirements rather than the code.
A decision table describes different system behaviours depending on combinations of condition states.
Decision table testing is based on the condition testing technique, but relies on the requirements rather than the code.
A decision table describes different system behaviours depending on combinations of condition states.
Requirements
The «Room Booking» form allows you to reserve a meeting room for a specific period of time.
The form has four input parameters: Meeting duration, Room, Confirmation required, Email address.
When the Confirmation required checkbox is selected, the Email address field becomes mandatory.
| Event | Message |
|---|---|
| Successful booking |
The {room_name} room has been successfully booked for {duration}.
|
| Attempt to book the «Andromeda» room for less than 1 hour |
The Andromeda room cannot be booked for less than 1 hour.
|
| Attempt to book with the Confirmation required checkbox selected but without email |
Enter your email for confirmation.
|
From the requirements it follows that processing the form may lead to three different results shown to the user, depending on the combination of input parameters.
| Condition | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Room is Andromeda? | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ||||||||
| Duration ≥ 1 hour? | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ||||||||
| Confirmation required? | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ||||||||
| Email provided? | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ||||||||
| Result | ||||||||||||||||
The {room_name} room has been successfully booked for {duration}.
|
✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | |||||||
The Andromeda room cannot be booked for less than 1 hour.
|
✗ | ✗ | ✗ | ✗ | ||||||||||||
Enter your email for confirmation.
|
✗ | ✗ | ✗ |
Уровень повышен!