Closed
Bug 805574
Opened 12 years ago
Closed 7 years ago
please add API for add and delete product, version, environment, suite, and run
Categories
(Mozilla QA Graveyard :: MozTrap, defect)
Mozilla QA Graveyard
MozTrap
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: lklrmn, Unassigned)
Details
creating and removing fixtures for moztrap-tests via selenium takes longer than the test itself does. using API calls would speed that up significantly.
Updated•12 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Hardware: x86 → All
Updated•12 years ago
|
Severity: normal → major
Comment 1•12 years ago
|
||
Cameron already started the planing on this: http://www.pivotaltracker.com/story/show/38741433
Comment 2•12 years ago
|
||
A Pivotal Tracker story has been created for this Bug: http://www.pivotaltracker.com/story/show/41554749
Comment 3•12 years ago
|
||
Leah Klearman changed story state to started in Pivotal Tracker
Comment 4•11 years ago
|
||
Leah Klearman added a comment in Pivotal Tracker: case attachment notes: https://gist.github.com/klrmn/4734532 https://github.com/Pylons/webtest/issues/24
Comment 5•11 years ago
|
||
Leah Klearman changed story state to delivered in Pivotal Tracker
Comment 6•11 years ago
|
||
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
Closed: 7 years ago
Resolution: --- → WONTFIX
Updated•6 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
•