Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Gliffy Diagram
nameall_in_one
pagePin23

How to set it up

  1. Create a new Scrum project or use an existing one.
  2. Add Test, Precondition, Test Set, Test Plan, Test Execution and Sub-Test Execution issue types to the project. This can easily be done using a shortcut available in the Summary section within the project settings (see  Project Settings: Summary) for editing the Issue Type Scheme used by the project. You can also be do it from within Jira administration > Settings > Issues > Issue Type Schemes.
  3. In the project settings, within the Test Coverage section (see Project Settings: Test Coverage), define the Covered Issue Types (i.e., the testable entities such as the typical requirements, user stories, epics). On the left side, you can see all available Issue Types. Drag the ones you want (e.g., Story, Epic) to the Covered Issue Types and save the settings.

...

Gliffy Diagram
nameseparated
pagePin34

How to set it up

  1. Create a Scrum project or use an existing one for managing the "Requirements Project".
  2. Create another project (it can also be a Scrum project) for managing the "Test Project". 
  3. In the "Test Project", add Test, Precondition, Test Set, Test Plan, Test Execution and Sub-Test Execution issue types to the project. Remove all other issue types. This can easily be done using a shortcut available in the Summary section within the project settings (see  Project Settings: Summary) for editing the Issue Type Scheme used by the project. You can also be do it from within Jira administration > Settings > Issues > Issue Type Schemes. 
  4. In the "Requirement Project" project settings, within the Test Coverage section (see Project Settings: Test Coverage), define the Covered Issue Types (i.e. the testable entities such as the typical requirements, user stories, epics). On the left side, you can see all available Issue Types. Drag the ones you want (e.g., Story, Epic) to the Covered Issue Types and save the settings.

...

Gliffy Diagram
namededicated_test_repository_scenario
pagePin34

Tip
titleTest Execution Versioning

If you plan to have separate projects for managing Requirements/Defects and Tests Executions and you want to analyze Requirements by version, then your Requirement's project version names must match the names of the Test Execution's project.

...

Gliffy Diagram
namecompletely_separate_scenario
pagePin45


How to set it up

  1. Create a Scrum project or use an existing one for managing the "Requirements Project".
  2. Create another project (it can also be a Scrum project) for managing the "Test Project". 
  3. Create another project (it can also be a Scrum project) for managing the "Test Executions Project" 
  4. Create another project (it can also be a Scrum project), for managing the "Defects Project". 
  5. In the "Test Project", add Test, Precondition and Test Set issue types to the project. Remove all other issue types. This can easily be done using a shortcut available in the Summary section within the project settings (see  Project Settings: Summary) for editing the Issue Type Scheme used by the project. You can also be do it from within Jira administration > Settings > Issues > Issue Type Schemes. 
  6. In the "Test Executions Project", add Test Plan and Test Execution issue types to the project. Remove all other issue types.
  7. In the "Requirement Project", add the Sub-Test Execution issue type.
  8. In the "Defects Project", add the Bug issue type.
  9. In the "Test Executions Project", add Test Plan and Test Execution issue types to the project. Remove all other issue types.
  10. In the "Requirement Project" project settings, within the Test Coverage section (see Project Settings: Test Coverage), define the Covered Issue Types (i.e., the testable entities such as the typical requirements, user stories, epics). On the left side, you can see all available Issue Types. Drag the ones you want (e.g., Story, Epic) to the Covered Issue Types and save the settings.

...

Gliffy Diagram
nameisolated_test_repository
pagePin23

Info

Users implementing this scenario might gain huge benefits if they are able to synchronize the requirements in the other tool and Jira.

...