Objectives for this functionality
- It should support hierarchical classification of Test Cases (as suggested).
- It should continue to support all existing functions like sorting.
- Page break in Table should not cause an issue with hierarchy.
- Users should be able to get decent performance with large number of Test Cases.
- Improved usability and user perception on what the Hierarchy represents.
Approach
- Provide a flat structure to define the Test Cases (as currently implemented).
- Provide a Custom Field of type Hierarchical View.
- The users will be able to associate Test Cases with a Label defined in the Hierarchy.
Examples of Different Hierarchical Views for TC's
Type of Test
- Sanity
- Requirements
- Traceability
- ...
- Performance
- Usability
By Functionality
- Requirements
- Creation
- Indentation
- Deletion
- ...
- Traceability
By Release
- RMsis 1.0.0
- RMsis 1.2.0
- RMsis 1.3.0
- RMsis 1.6
Implementation
Define a "View Name" of type Hierarchical View
- The custom column would be given a View Name, while creating
- This could be global or specific to a project.
- Labels can be created and organized in a Hierarchy under Views.
Associate TC's with Views
- User can associate the TC's with views using Multiselect Option
Create Label
Image Added
Edit / Delete Label
Image Added
Tabular Views - Flat
Test Types | TC | | |
---|
/Sanity | | | |
/Sanity/Requirement | TC1 | | |
/Sanity/Requirement | TC2 | | |
/Sanity/Requirement | TC3 | | |
Impacted functions
- TR's
- Panles
- Selection mechanisms in panels ... for example TC selection panel for "Create TR" may contain an option to select based on hierarchical classification.
- Custom Reports
{"serverDuration": 208, "requestCorrelationId": "b3cf5a6a83b842269e78812574c7a9dc"}