Closed Bug 650943 Opened 15 years ago Closed 14 years ago

Results: Implement list of TestCycles

Categories

(Mozilla QA Graveyard :: MozTrap, enhancement, P1)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: camd, Unassigned)

References

Details

This list should be filterable with unified filtering interface Paginated Each line should show some summary data without expanding, such as: - % complete - Summary results values for that cycle (pass / fail / invalid / pending) - Start date or deadline? - others, TBD
Target Milestone: --- → 0.3
Summary: Results: Implement unexpanded list of TestCycles → Results: Implement list of TestCycles
Expansion of a Test Cycle: When a testcycle is expanded, it should show: - link to all the contained testcases - link to all the contained testruns - team members - perhaps put start date / deadline here instead?
This list should default to show test cycles filtered to in-progress only, sorted by product. If the user wants to see all test cycles for one product, they can just change their filtering.
Severity: normal → enhancement
"% complete" keeps coming up as an idea, but I still don't know what it actually means. I know I asked all this on an earlier bug, but I'm not sure which now. Is it % of test-cases in the cycle that have been run by at least one tester in at least one environment? Percent of possible results (cases x environments) that have been reported? In any case it'll need to be added as a new platform feature, so I suggest when there's a clear answer to what the % should represent, just file that description as a TCM-Platform bug for Vadim, and when he adds it we can come back and file bugs to add it to the relevant screens.
Just skyped with Carl. I understand the problem better now and will write a new bug for Vadim on the platform and reference it here. Please see that bug for details.
Depends on: 651174
Details mentioned above, and required new API on platform are described and requested in: Bug 651174
Priority: -- → P1
A Pivotal Tracker story has been created for this Bug: http://www.pivotaltracker.com/story/show/12751037
Cameron Dawson changed story state to unstarted in Pivotal Tracker
Eric Meyer added a comment in Pivotal Tracker: https://www.pivotaltracker.com/story/show/12717235
Eric Meyer changed story state to started in Pivotal Tracker
Carl Meyer changed story state to finished in Pivotal Tracker
Carl Meyer changed story state to started in Pivotal Tracker
Eric Meyer changed story state to finished in Pivotal Tracker
Carl Meyer changed story state to delivered in Pivotal Tracker
Carl Meyer added a comment in Pivotal Tracker: Just realized that test cycles in "draft" state will never have any results. Should they be excluded from this list by default, or should we just leave that up to the user to filter?
Cameron Dawson added a comment in Pivotal Tracker: carl: yes, exclude draft cycles from the results area. I think that's best.
Cameron Dawson changed story state to started in Pivotal Tracker
Carl Meyer changed story state to finished in Pivotal Tracker
Carl Meyer changed story state to delivered in Pivotal Tracker
Cameron Dawson changed story state to accepted in Pivotal Tracker
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.