Content Comparison

Objectives for this implementation

1. It should support hierarchical classification of Test Cases (as suggested).
2. It should continue to support all existing functions like sorting.
3. Page break in Table should not cause an issue with hierarchy.
4. Users should be able to get decent performance with large number of Test Cases.
5. Improved usability and user perception on what the Hierarchy represents.

An Alternative Approach

• Provide a flat structure to define the entities (Like we have TC's now).
• Provide a Custom Field of type Hierarchical View.
• A user should be able to define multiple Hierarchical Views
• The user will be able to associate artifacts with any of the defined views.
• The views can be switched to show different organizations.

Examples of Different Hierarchical Views for TC's

Type of Test

• Sanity
  
  • Requirements
  • Traceability
  • ...
• Performance
  
  • UI
  • DB
  • Application
• 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
  • RMsis 1.6.1
  • RMsis 1.6.2

Implementation

Define a "View Name" of type Hierarchical View

• Each custom column would be given a View Name, while creating
• This would be specific to a project.
• For first release, this may be limited to just 1 view
• Labels can be created under Views.

Associate TC's with Views

• User can associate the TC's with views using Multiselect Option

Tabular Views - Flat

Tabular View - Hierarchical

Note : The highlighted part should be considered as Merged.

Create Label

Image Added

Edit / Delete Label

Image Added

Impacted functions

1. TR's
2. Panles
3. Selection mechanisms in panels ... for example TC selection panel for "Create TR" may contain an option to select based on hierarchical classification.
4. Custom Reports