Basically, because our test suites cover components of our Product, we would benefit from being able to categorize those test suites/components, for example “Frontend” vs “Backend”. I would be able to create Test Plans/Runs based on these properties.
Another scenario is prioritization. We’d like to have 2 different priority scopes. The priority of a test case is limited to the scope of it’s test suite, not the overall Product. The priority of a test suite, however, is at the Product level.
Say you have this structure:
TC A.1 (priority: high)
TC A.2 (priority: medium)
TC B.1 (priority high)
TC B.2 (priority low)
I’d like to be able to prioritize TS B so that BOTH TC B.1 and TC B.2 get executed before TC A. So if I assign the following priorities to the test suites:
TS A (low)
TS B (high)
This will be the order of test cases:
Now, this can be accomplished artificially by the administrator (when creating runs) as long as the info is in the test suite to begin with, I guess that’s more realistic than the auto-recalculation of priorities.
Hope this clarifies things more. “Type” and “Priority” are the two main properties we could use now, but I could definitely see the need for custom field support.