Basic Test Scenario creation with Decision Table
Hi folks, follow one basic example about Decision Table under Test Scenario definition. In my job, I have created this artefact with my Engineers, and We have had excellent test coverage results. This is a good brainstorm documentation, and It can provide a path for future automated scripts.
Usually, I work on this artefact with my team, during Sprint Planning session. However, as I sayd on my post about refinemment, the process to writeTest Scenarios starts on Grooming session, as a first draft and in this session my goals are:
- Eliminate existing knowledge gaps (when they exist)
- Share with Engineers knowledge about Test Scenarios
- Create new Test Scenarios when applicable
Now, some suggestion how to write scenarios on Decision Table mode:
Example:
GIVEN that a feed is received from application ABC
WHEN Campaign Name is equal to Customer Not Available
AND Group Name is in (US.A,US.B,US.B)
AND Entitlement is equal to Premium
THEN change the status from case to Need answer
Steps:
- Find the happy path: The information needs to match the Story/Feature goal. If I proceed with all actions/data defined on Acceptance criteria, I should match an expected results previous defined. (Lines in green on image above)
- Find Negative scenarios: If you set a wrong information, a data different from defined in the happy path… The story goal won’t be reached. (Lines in red on image above)
Of course this is a basic example, and It isn’t fit for all scenarios/companies or stories existents. This isn’t the silver bullet for test strategy. But, If you would like to start to think about Test Scenarios, Decision Table can help you. This strategy has helped to share Test Discipline with my Engineers and could help you too, with your challenges. Good luck.
