Xray terminology is mostly common to what may be found in the Test Management world.
Throughout the documentation and the UI you may find some key terms that are summarized in the following table. Please take a look below and follow the links for more detail on specific topics.
Learn more
You may want to give a look at this short video which explains the core concepts and the issue types used by Xray.
Terminology
| Concept/Term | Issue Type | Description | Also known by the testing community as... |
|---|---|---|---|
| Test | Test | A test case. It may be either a manual or automated test, composed of multiple steps, actions and expected results. | test case, test scenario, test template |
| Pre-Condition | Pre-Condition | Initial conditions that must be assured before the Test own steps. A Pre-Condition may be used by multiple Tests. | |
| Test Set | Test Set | A group of tests, organized in some logical way. A test may belong to multiple Test Sets. | test group, test suite |
| Test Plan | Test Plan | A "formal" plan of the tests intended to be executed for a given version. | |
| Test Execution | Test Execution | An assignable, "schedulable" task to execute one or more tests for a given version/revision along with its results. | test cycle |
| Sub-Test Execution | Sub-Test Execution | A Sub Test Execution has the same functionalities as the Test Execution issue type. The difference between them is that the Sub Test Execution is a sub-Task and can be created in a requirement's context. Creating a Test Execution as a sub-task from within the requirement issue screen, will provide the user the ability to track executions in the Agile's board. | |
| test run | - | A specific run of a test. An instance of the test, containing the execution status and a snapshot of the test specification. Whenever a user adds a Test to a Test Execution, internally a test run is created within the Test Execution context. A test may have multiple test runs. | |
| test status | - | The "status" of a Test. Mostly, a shorthand for "test run status". Xray provides a calculated custom field TestRunStatus which may be used in queries, gadgets, etc, based on some rules. | .. |
| requirement | Story, Requirement, .... | Something that you expect from the system. A feature. A good requirement explains how the system should behave and it's purpose. | |
| test repository | - | The full list of tests within a project. In Xray the test repository is simply composed of all Test issues. | |
| test strategy | - | Which requirements you want to validate, how to validate, use of either manual or automated tests, the resource allocation, etc. | |
| testing lifecycle | - | After requirement specification and revision, the testing lifecyce involves test planning , test designing, test execution and test reporting. |
Entities Relationship Diagram
