Ticket #1367 (new enhancement)
Test suite concept for Testing Tools
| Reported by: | Jani Laakso | Owned by: | Jani Laakso |
|---|---|---|---|
| Priority: | undefined | Milestone: | Testing Tools Backlog |
| Component: | Testing Tools | Version: | |
| Keywords: | Cc: | ||
| Known Issue description: | |||
| Hours estimate: | 14 | Deadline (dd.mm.yyyy): | |
| Known Issue version (since): | Known Issue title: | ||
| Hours done: | Depends to: | ||
| Affects documentation: | no | ||
| Known Issue workaround: | |||
| Affects release notes: | yes | Contract: | |
Description
Typically testing softwares involve test suite usable to divide massive amounts of test cases into logical groups. E.g. Test Suites could be organized based on product modules or even functional vs. performance vs. security testing etc, it's up to customer how they want to organize their testing.
It's troublesome to move in / out mass amount of test cases when creating tasks, adding / moving test suites is a lot cleaner solution.
Just add Test suite concept to Testing tools. Test suite has 1 .. N relation to test cases.
Doing database is simple, usable UI creation and testing takes some time..
Change History
Note: See
TracTickets for help on using
tickets.
