Most of the Xray terminology is common within the Test Management world. Summarized in the table below are some of the key terms you will find throughout the documentation and the UI. Please review and follow the links for more detail on specific topics.
This short video explains the core concepts and the issue types used by Xray.
|Concept/Term||Issue Type||Description||Also known in the testing community as...|
|Test||Test||A test case. It may either be manual or automated, 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 execution of the Test's 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 campaign|
|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*, test campaign|
|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 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, a test run is created internally within the Test Execution context. A test may have multiple test runs.|
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 its 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 them, 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.|
If you know ISTQB, you may want to give a look at ISTQB glossary vs Xray terminology.
Entity Relationship Diagram
Although not common, you may link a Test Execution with multiple Test Plans making its results impact on the consolidated overview shown/managed on each linked Test Plan.