Closed
Bug 851723
Opened 13 years ago
Closed 9 years ago
possible to get duplicate environments that look identical, leading to confusion
Categories
(Mozilla QA Graveyard :: MozTrap, defect)
Mozilla QA Graveyard
MozTrap
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: camd, Unassigned)
Details
some parts of the product allow you to create environments from env elements "on the fly" and it creates a new environment for that. the problem is that you can create one env with element A, and another new env with element A as well. They look the same, but are not. This leads to confusion with cases, suites, runs, etc.
we need to
1. make sure when a new env is created, we check for an existing identical one and use that instead.
2. make a script to "fix" all duplicate envs with identical elements
3. fix all the places where dup envs are referenced
| Reporter | ||
Comment 1•13 years ago
|
||
A Pivotal Tracker story has been created for this Bug: http://www.pivotaltracker.com/story/show/46314293
| Reporter | ||
Comment 2•13 years ago
|
||
Cameron Dawson changed story state to started in Pivotal Tracker
| Reporter | ||
Comment 3•13 years ago
|
||
Cameron Dawson changed story state to unstarted in Pivotal Tracker
| Reporter | ||
Updated•11 years ago
|
Assignee: cdawson → nobody
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: 9 years ago
Resolution: --- → WONTFIX
Updated•7 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•