Page History
...
- workflow status associated to the requirement issue (e.g. "New", "In Progress", "Closed")
- (coverage) status for some version, taking into account executions made for that version of the Tests that do validate the requirement
- "Requirement Status" custom field, the one that we will detail next
The "Requirement Status" custom field is a calculated field, usable in the context of requirement issues, that calculates the requirement coverage for a specific version. The version that it calculates the coverage for depends on the behavior for that field defined in a global configuration (see configuration details here).
...
Have in mind that a requirement is assigned to and implemented in some version. However the requirement will still live after that version, at least for some time. Therefore, when someone mentions a "status of a requirement", you have to ask "In which version?". The status of the requirement is thus dependant on the executions you make for the associated Tests in some version of the system, which may by different from the version in which the requirement was initialy implemented in.
This field is non-searchable.
...
searchable, so you can make statistics with it or use in gadgets. However, if you wish to search for requirements in some status we recommend using the requirements() JQL function instead (more info here).
TestRunStatus
Whenever we're speaking about status associated with a Test, we may in fact be talking about different things:
- workflow status associated to the Test issue (e.g. "New", "In Progress", "Closed")
- (coverage) status for some version, taking into account the runs made for that Test in some version of the system
- "TestRunStatus" custom field, the one that we will detail next
The "TestRunStatus" custom field is a calculated field, usable in the context of Test issues, that calculates the "status" (not the workflow status) of the Test for a specific version, having in mind executions (i.e. test runs) for that version. The version that it calculates the status for depends on the behavior for that field defined in a global configuration (see configuration details here).
The calculated value for the field also depends on Test Environments, if they're being used, as mentioned here. As an example, you may prefer to always show the latest test run result independently in which version it was executed... or you may prefer to show the status of the latest run executed on the earliest version yet to be released (i.e. the next version). In the later case, it takes into account the order of the versions within the project settings page. You can add this field to the Test
Although a Test in Xray is essentialy a test case template, thus not related with any execution whatsoever, you can add this field to the Test view screen as a way to have a glance of the current status of it for some version right from the screen of the "test template" (i.e. Test).
| Info | ||
|---|---|---|
| ||
The name of this custom field may be a bit misleading at first sight. Although it is named "TestRunStatus", don't confuse it with the status (i.e. the result) of some recorded Test Run. As mentioned above, the TestRunStatus custom field takes into account, eventualy, many Test Runs. |
This field is searchable, so you can make statistics with it or use in gadgets. If you wish to search based on, please see the proper syntax here.
Test Set Status
The "Test Set Status" custom field is a calculated field, usable in the context of Test Set issues, that calculates the "status" (not the workflow status) of all the Tests within the Test Set, for a specific version, having in mind executions (i.e. test runs) for that version. The version that it calculates the status for depends on the behavior for that field defined in a global configuration (see configuration details here).
Although a Test Set in Xray is basically a list of Tests,thus not related with any execution whatsoever, you can add this field to the Test Ser view screen as a way to have a glance of the current status of the Tests that are part of it, for some version right from the screen of the Test Set. This can be quite useful if you have some highly relevant Test Sets and you wish to quickly have an high-level idea of the status of the Tests that belong to it.
This field is non-searchable.
Test Execution Status
This custom field provides information about the progress (i.e. the "Overall Execution Status") of the Test Execution issue.
It can be used, for example, in gadgets, included in the cards of Agile boards, used as a column in JIRA issues listing.
This field is non-searchable.
Test Set Status
Test Plan Status
This custom field provides information about the progress (i.e. the "Overall Execution Status") of the Test Plan issue.
It can be used, for example, in gadgets, included in the cards of Agile boards, used as a column in JIRA issues listing.dd
This field is non-searchable.
Adding your own custom fields
...