Versions Compared

Key

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

...

Gliffy Diagram
nameall_in_one
pagePin12

How to setup it

  1. Create a Scrum project or use an existing one;
  2. Add Test, Pre-ConditionPrecondition, 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; it can also be done from within Jira administration > "Settings" > "Issues" > "Issue Type Schemes";
  3. In the project settings, withi n 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 and then you can drag the ones you want (e.g. Story, Epic) to the "Covered Issue Types". Don't forget to save the settings at the bottom of the page.

...

Gliffy Diagram
nameseparated
pagePin23

How to setup it

  1. Create a Scrum project or use an existing one, for managing the "Requirements Project";
  2. Create another project (it can be a Scrum project), for managing the "Test Project"; 
  3. In the "Test Project", add Test, Pre-ConditionPrecondition, Test Set, Test Plan, Test Execution and Sub Test Execution issue types to the project and remove 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; it can also be done 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 and then you can drag the ones you want (e.g. Story, Epic) to the "Covered Issue Types". Don't forget to save the settings at the bottom of the page.

...

Another common use case for Xray is to have a dedicated project for Test (and Pre-Condition Precondition and Test Set) issues. Test Executions are the responsibility of other project(s). This separation allows to manage permissions more effectively, so maybe only a few testers have permission to write tests and others only have permission to execute.

...

Gliffy Diagram
namededicated_test_repository_scenario
pagePin23

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.

...

  1. Create a Scrum project or use an existing one, for managing the "Requirements Project";
  2. Create another project (it can be a Scrum project), for managing the "Test Project"; 
  3. Create another project (it can be a Scrum project), for managing the "Test Executions Project"; 
  4. In the "Test Project", add Test, Pre-Condition Precondition and Test Set issue types to the project and remove 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; it can also be done 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 and remove 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 and then you can drag the ones you want (e.g. Story, Epic) to the "Covered Issue Types". Don't forget to save the settings at the bottom of the page.

...

Gliffy Diagram
namecompletely_separate_scenario
pagePin34


How to setup it

  1. Create a Scrum project or use an existing one, for managing the "Requirements Project";
  2. Create another project (it can be a Scrum project), for managing the "Test Project"; 
  3. Create another project (it can be a Scrum project), for managing the "Test Executions Project"; 
  4. Create another project (it can be a Scrum project), for managing the "Defects Project"; 
  5. In the "Test Project", add Test, Pre-Condition Precondition and Test Set issue types to the project and remove 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; it can also be done 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 and remove 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 and remove 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 and then you can drag the ones you want (e.g. Story, Epic) to the "Covered Issue Types". Don't forget to save the settings at the bottom of the page.

...

Gliffy Diagram
nameisolated_test_repository
pagePin12

Info

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

...

  1. Create a Scrum project or use an existing one, for managing the "Test Project"; this one will also be handled as being a requirements like project;
  2. In the "Test Project", add Test, Pre-Condition Precondition and Test Set issue types to the project and remove other issue types except the issue type to be handled as a requirement and the Bug. 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; it can also be done from within Jira administration > "Settings" > "Issues" > "Issue Type Schemes"; 
  3. In the "Test 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 and then you can drag the ones you want (e.g. Story, Epic) to the "Covered Issue Types". Don't forget to save the settings at the bottom of the page.

...