You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Using Fields

You can classify your tests in order to make it easier to organize & search for them. 

JIRA has many options to classify your issues using system fields or even create your own. Here some examples:

  • use labels to tag your Tests (or your Test Sets); if you start having many testers and your project grows, having a well-defined list of labels may help
  • use the priority field, so you can distinguish between tests
  • assign the Test to the proper component
  • Ask your JIRA Administrator to create your own custom fields

Using Test Sets


Xray gives you a new JIRA issue Type, named Test Set that enables you to get tests together into a list.


A Test Set is a collection of Tests. It often contains detailed instructions or goals as well as information on the configuration to be used during testing.

Test Sets are simple, flat lists of Tests that you can use as a basis for creating Test Executions or Test Plans. Since the Tests are grouped in some logical way, such as grouping all Tests related with regression testing or security, or all Tests for a specific component or some high-level feature/business case, a Test can be part of different Test Sets. Test Sets can also be used as a dynamic way to cover requirements.


Examples of Test Set

You can create test set for: 

  • Group Tests by UI Component
  • Group Test by Type (security, performance, functional 

Organize Tests in Test Sets

  • group tests in as many Test Sets as it makes sense to you, either because they're testing the same feature or the same UI component, or if they exercise the most critical use cases
  • classify your Test Sets, similarly to what you did for Tests

Organize Tests for regression testing

  • you can create a Test Set for this purpose and add a specific label to it (e.g., "regression"), and then you test for requirements of previous versions
  • you can create a "regression Test Set" for each version by cloning the previous version regression test set and add more tests


You're working on product v3.0 and want to do regression testing to make sure you have not broken anything. If the previous version, v2.0, had already some regression tests in a specific test set, then you can clone it and add some more tests for validating v2.0. 






The Test Repository concept enables the hierarchical organization of Tests at the project level by allowing you to organize Tests in folders.

  • No labels