Content Comparison

Objectives for this

...

functionality

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.

...

Approach

• Provide a flat structure to define the entities (Like we have TC's nowTest Cases (as currently implemented).
• Provide a Custom Field of type Hierarchical View.
• A user should be able to define multiple Hierarchical Views
• The user The users will be able to associate artifacts with any of the defined views.The views can be switched to show different organizationsTest Cases with a Label defined in the Hierarchy.

Examples of Different Hierarchical Views for TC's

...

Define a "View Name" of type Hierarchical View

• Each The custom column would be given a View Name, while creating
• This would could be global or specific to a project.
• For first release, this may be limited to just 1 view
• 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

Tabular View - Hierarchical

Note : The highlighted part should be considered as Merged.

Create Label

Image Removed

Edit / Delete Label

...

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