In this page you will be able to get an high-level overview of how to implement testing in your project.


Please take some time to learn about the terminology used in Xray and the relation between the several entities, by looking at Terms and Concepts.


Managing version oriented projects

In this use case, your project has one or more versions that you evolve as needed.

You may start with some requirements for v1.0 and later on create a v1.1 or a v2.0 release, as an example.

How do you then implement testing in this scenario?


Supose that you are working in version "XPTO" and you want to implement testing in it, in order to make sure that the features you deliver are correct.

Your workflow would be more or less:

  1. create "requirements" (e.g. Story, Epic or other similar issue types) and associate them with a version XPTO, through the FixVersion field
  2. create one or more Tests for validating each requirement; Tests can be created from the requirement issue screen

  3. create at least one Test Plan with the Tests you want to validate in version XPTO; don't forget to assign the Test Plan with version XPTO, through the FixVersion field

    Pleas see our Tips for planning tests, which explore the different possibilities you have concerning planning, including in Waterfall and Agile methodologies.


  4. from the Test Plan, create one or more planned Test Executions with the Tests that you want to execute. Each Test Execution is an abstraction of a "task for running some Tests" and can be assigned to specific users. Inside the Test Execution invidividual Test Runs may be reasssigned to some other users;
  5. from the Test Plan, create new Test Executions to validate all Tests or just with the ones that are, for example, failing