a tester should have an easy way to see the pending tests they are assigned to run

RESOLVED WONTFIX

Status

RESOLVED WONTFIX
8 years ago
6 days ago

People

(Reporter: camd, Unassigned)

Tracking

Details

(Reporter)

Description

8 years ago
perhaps a link on their login screen?  or once they have picked a product, then show a link to the tests for them to execute for that product.  Could these tests belong to several test runs?
(Reporter)

Comment 1

8 years ago
A Pivotal Tracker story has been created for this Bug: http://www.pivotaltracker.com/story/show/13298779
(Reporter)

Comment 2

8 years ago
Carl Meyer added a comment in Pivotal Tracker:   
   
This could just be an option/checkbox in the hierarchical chooser to "only show me test runs that I've already been assigned, not ones that I could choose to self-assign."
(Reporter)

Comment 3

7 years ago
Cameron Dawson added a comment in Pivotal Tracker:   
   
Carl: does this story really need an api change?  I can't find a bug for it.  I may have given it that tag erroneously.
(Reporter)

Comment 4

7 years ago
Carl Meyer added a comment in Pivotal Tracker:   
   
It depends on this one: https://bugzilla.mozilla.org/show_bug.cgi?id=659073 which is fixed, though I haven't gotten to it to verify yet.
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
Last Resolved: 2 years ago
Resolution: --- → WONTFIX

Updated

6 days ago
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.