Closed Bug 740972 Opened 12 years ago Closed 7 years ago

a user should be able to filter run tests by result status

Categories

(Mozilla QA Graveyard :: MozTrap, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: camd, Unassigned)

Details

this would be especially helpful to see only a list of items that are pending,
A Pivotal Tracker story has been created for this Bug: http://www.pivotaltracker.com/story/show/27323215
Carl Meyer changed story state to started in Pivotal Tracker
Carl Meyer added a comment in Pivotal Tracker:   
   
This is quite difficult for the same reasons as sorting by result status. I'm sure both are possible, but they will probably require a quite in-depth re-working of how the runtests page works, unfortunately.
Carl Meyer changed story state to unstarted in Pivotal Tracker
Carl Meyer added a comment in Pivotal Tracker:   
   
This story is also a duplicate of https://bugzilla.mozilla.org//show_bug.cgi?id=658670
Cameron Dawson added a comment in Pivotal Tracker:   
   
it's actually a little different.  The other story is about filtering by results in the View Results screens.  This one is about filtering in the runtests screens
Carl Meyer added a comment in Pivotal Tracker:   
   
whoops, indeed - late-night reading comprehension fail :-)
Mass-closing remaining MozTrap bugs as WONTFIX, due to 1) the Mozilla-hosted instance being decommissioned (see https://wiki.mozilla.org/TestEngineering/Testrail), and, for now, 2) the still-up code archived at its GitHub page: https://github.com/mozilla/moztrap (we'll decide what's next for that, in the near future).

See also the history and more-detailed discussion which led us here, at https://groups.google.com/forum/#!topic/mozilla.dev.quality/Sa75hV8Ywvk

(If you'd like, you should be able to filter these notification emails using at least the unique string of "Sa75hV8Ywvk" in the message body.

Thanks!
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.