Page History

...

Issue types used for Testing:

Test

Test should be created within the ticket of a story. It represents one test case, with one or more steps. A story should have at least one Test linked to it, but it could be more depending on the story. These Tests should be added to a Test Plan at the start of a sprint. A Test also has different statusses:

1. BackLog: added to a story but not yet defined
2. To Do: the sprint has started, the requirements are clear, so the Test could be picked up to create the test steps, even if development has not yet started
3. In Progress: the story is being developed or even development is done. The Test should be created and defined. Steps should be described and the expected results should be clear 
4. Done: the Test itself is finished and ready to be executed as soon as the development of the story is done and reviewed and the ticket is set on 'Ready for test"

The Test itself should not be linked to a sprint, but the Test Plan of which this test is a part of should be.

Pre- Condition

Abstract initial steps that mast be ensured before starting the test.

• Manual or Automated (mapped to background clause in case of Cucumber)
• Reusable - may be linked to multiple Tests

Test Plan

When? How? Naming convention. Status updates ISSUE etc. Set the best practice and min requirementsTo be created at the start of each sprint and linked to that sprint. It is just needed to create an empty Test Plan, which can be filled with Tests created for each story in the sprint. The name should reflect the naming of the sprint, for example "DMS Test Plan sprint 1", "DMS Test Plan sprint 2" etc.

Test Set

When? How? Naming convention. Set the best practice and min requirements. 

...