Versions Compared

Old Version 12

changes.mady.by.user user-0caa0

Saved on

compared with

New Version 13

changes.mady.by.user Sergio Freire

Saved on

Key

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

...

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. This is how to do it.


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. 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.  
  5. In the "Test Executions Project", add Test Plan, Bug and Test Execution issue types to the project. Remove all other issue types.
  6. In the "Requirement Project", add the Sub-Test Execution issue type.
  7. 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.

...