Introduction Xray

Xray for Jira is a Test Management tool (app) that provides the structure to organize, plan, and report with accuracy on the progress of testing as well as the readiness to deploy.
More detailed information for this app can be found on:  https://docs.getxray.app/display/XRAY/About+Xray

Issue types used for Testing

Test Image Modified

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:

...

The naming of the Test should reflect the naming of the corresponding story, but edited with the word "Test" as to make clear this is specially for testing. For example, if the title of the story is "Improve the interface" the Test should be named "Test Improve the interface"

Pre- Condition Image Modified

Pre-Conditions are generic steps that are not necessarily part of the actual Test case, but mostly used as some setup conditions before the real Test can start. These steps are reusable and may be linked to multiple steps. These pre condition should never be linked to any sprint.

Test Plan Image Modified

To 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 Image Modified

A Test Set is a collection of Tests that can be linked to each other for organizing purposes. These can be matched by subject or a specific part of the application. Using Test Sets can make looking up and re-using existing tests more easy and manageable. A Test can be linked to multiple Test Sets. It should be clear by naming the Test Set what the common factor of these Tests are, for examle "Test Set - parts master interface (DLITMPRT)" for all Tests regarding the parts master interface, regardless which story. A Test Set should not be linked to any sprint.

Test Execution Image Modified

Just like a Test Plan should a Test Execution always be linked to a sprint. Ideally the Test Execution should contain all Tests for every story in the current sprint. At this point just one Test Execution ticket is created for executing all Tests. It is possible to create that Test Execution ticket from the Test Plan ticket:

...

The naming of this Test Execution ticket should have a link to the sprint just like the Test Plan. Example: for Test Plan of sprint 1 it should be something like "Test Execution for Test Plan Sprint 1". At a later stage it could be more preferable to have more Test Execution tickets.

Sub Test Execution Image Modified

Repositories (PreRequisites)

Do we need / want repositories. If yes, what status, what naming convention etc. 

Test Process Workflow (draft)

Xray: Testing Process workflow within the Sprint YIS Project

Step-by-step guide

1. Create a new empty Test Plan

At this moment there will be no Tests yet in this Test Plan. When scrolling down this Edit screen, it is possible to add this Test Plan to the current screen:

2. Create one or more Test tickets for each story on the (Scrum of Kanban)  Project board

For each story in this sprint it is possible to create one or more Tests. 

...

This test should not be linked to the sprint, so make sure the correct Test Plan is added in order for this Test to be executed once the development of the story is done.

3. Defining the Test steps within the Test tickets

When the Test tickets have been created in step 2, it is possible to define the actual Test case in the newly created Test ticket. As many steps as possible can be added to each Test:

...

After all test cases/test steps have been created and the tests have good coverage for this story, the Test ticket can be set to done, in order to know that this Test can be executed as soon as development and reviewing is done for the story.

4. Creating a Test Execution ticket for this sprint

Once all the Test tickets have been created it is possible to get an overview of their status by looking at the XRay Test Plan Board just to see which Test tickets should still be completed.

...

If all steps succeed (green box), the ticket will appear as a Pass in both the Test Plan and the Test Execution ticket, as well as on the Xray Test Plan Board and in the story. Once all Tests from the Test execution/Test Plan have passed, the stories can be set to ready for deployment and the sprint can be closed.

Boards

XRAY Test Plan Board

Planning per sprint

Jira Project Board YIS- All test products

Issue type visible on board: Plan and Execution

Use Switch sprint at the top to filter on a specific sprint.

...