...
draw.io Diagram | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
TM creates Tests (issue type) for all stories included into Sprint and associates them with Test Plan.
Tests should be created from the story:
2. When Tester starts work with the story, he/she creates Test Design for the story within the associated Test
Tester add test steps with all necessary data and Expected Results
3. The development is done and story is deployed for testing, Tester goes to the story and creates Test Execution for the newly created Test
4. To start test execution click icon "View runs" from the Story:
or click on "Execute in" in Test issue:
Test run will open in a new tab.
If you don't see the "View runs" icons in the Story, open the Test, scroll down to Executions. There is a Play (Run) button near each execution.
Click it and select Execute:
Please note: to be able to run the execution, it should be assigned to you. Otherwise you will not see the Execute button.
5. Tester executes all steps manually on test env and set the status for each step (Pass/Fail) within created Test Execution
Bugs should be associated with test step if found
6. Each Test Execution should be added to Test Plan by Tester
7. If bug was found and test step is failed, new Test Execution should be created after bug fix. Steps 3-6 should be repeated
8. Test is completed when all test steps are green for latest Test Execution
...
Planning per sprint
...