Xray v3.0 introduces the Test Repository concept which allows hierarchical Tests organization at project level, by allowing users to organise Tests in folders.
This is a different approach from the traditional way of organising Tests in flat lists by using Test Sets.
Similar to traditional operating systems (e.g. Windows, OSX, Linux), Tests may only be part of one folder.
- All: all Test issues within the current project
- Orphans: all non-organised Test issues (i.e. Tests that are not part of the Test Repository), in the context of the current project
- Test Repository: the actual Test Repository, composed of multiple folders and sub-folders along with Tests, in the context of the current project
Sections
Folders
Expand All
Tests
Folder Actions
Create
Remove
Rename
Expand/Collapse
Expand/Collapse All
Add to Test Set
Create Test Set
Add to Test Executon
Create Test Execution
Add to Test Plan
Create Test Plan
Tests Actions
Add to Test Set
Create Test Set
Add to Test Executon
Create Test Execution
Add to Test Plan
Create Test Plan
Move to Orphans
Recommendations
- Avoid putting semantic related with the execution phase in the Test Repository or else your Test Repository will end messed up
Test Repository vs Test Sets
Test Sets are simple, flat lists of Tests that you can use as basis for creating Test Executions or Test Plans. Tests can be part of different lists (i.e. Test Sets), each one grouping Tests in some logical way, such as grouping all Tests related with regression testing, or with a component, or with security, or with performance or with some high-level feature/business case. Test Sets can also be used as a dynamic way to cover requirements.
The Test Repository concept is a bit different; you have to think a bit similarly to what..
Pros and Cons
| Pros | Cons | |
|---|---|---|
|
|