Page History
...
At this moment there will be no Tests yet in this Test Plan. When scrolling down this Edit screen, it is possible to add this Test Plan to the current screen:
2. Create one or more
...
Test tickets for each story on the board
For each story in this sprint it is possible to create one or more Tests.
...
This test should not be linked to the sprint, so make sure the correct Test Plan is added in order for this Test to be executed once the development of the story is done.
3. Defining the Test steps within the Test tickets
When the Test tickets have been created in step 2, it is possible to define the actual Test case in the newly created Test ticket. As many steps as possible can be added to each Test:
Within each step there is room for the actual action where a description is to be entered about the Test case. Test data (conditions) can be added in the second space. And in the last space there is a space for the expected results, to be extracted from the requirements and functional documentation. At this point it is also a possibility that questions about these requirements will come up, so this would also be a good time to get some extra confirmation from the PO or BA in case of doubts about the expected results.
After all test cases/test steps have been created and the tests have good coverage for this story, the Test ticket can be set to done, in order to know that this Test can be executed as soon as development and reviewing is done for the story.
| draw.io Diagram | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Overview
Content Tools