| Summary: | [RFE] Etimated hours field | ||
|---|---|---|---|
| Product: | [Other] TCMS | Reporter: | Tomas Pelka <tpelka> |
| Component: | Application | Assignee: | Yang Ren <ryang> |
| Status: | NEW --- | QA Contact: | Nobody <nobody> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.6 | CC: | junzhang, ryang, vchen |
| Target Milestone: | --- | ||
| Target Release: | 4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Tomas Pelka
2011-11-02 12:47:53 UTC
My idea is that everyone can see for the first view how much time will this test plan take for one person on one arch (basic and full testing). Just informative fields, perhaps sortable. We can sum each test case's estimated time for full test plan. We don't know what is "Basic"? Basic = P1's only (In reply to comment #3) > Basic = P1's only Sorry I meant P1+P2. It seems that different team has different standard on "Basic" definition. so we should have a full test estimation time in each plan. Consider if we need a feature to calculate the time based on the filtered test cases in TCMS 4.0. |