If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

unable to remove the last suite(s) from a run

RESOLVED WONTFIX

Status

Mozilla QA
MozTrap
RESOLVED WONTFIX
5 years ago
6 months ago

People

(Reporter: Leah Klearman, Unassigned)

Tracking

Details

(Reporter)

Description

5 years ago
seen on moztrap-dev 1/4/2013 evening:

edit a run that has multiple suites
remove one of the suites, press save
suite is removed from the run.

edit a run that has multiple suites
remove all of the suites. press save
none of the suites are removed.

this is not a problem for removing cases from suites or cases from tags.
wow, this is an interesting one. can't reproduce it locally yet, but I sure can on moztrap-dev.  nice find!  Thanks!
A Pivotal Tracker story has been created for this Bug: http://www.pivotaltracker.com/story/show/42066585
Cameron Dawson changed story state to started in Pivotal Tracker
Cameron Dawson changed story state to delivered in Pivotal Tracker
Cameron Dawson changed story state to accepted in Pivotal Tracker
Cameron Dawson changed story state to accepted in Pivotal Tracker
Cameron Dawson changed story state to started in Pivotal Tracker
Cameron Dawson changed story state to accepted in Pivotal Tracker
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: 6 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.