666770 - should be able to set a pre-condition to testing in a suite

Status: RESOLVED WONTFIX

(Mozilla QA Graveyard :: MozTrap, enhancement)

Description

[Cameron Dawson [:camd]]

For example: logged in as admin.
This is something that should be true for all cases in the suite.
This would show for each test case that came from that suite during execution.

Not clear how this would display/work if a test case belongs to more than one suite, and both those suites are added, but have different preconditions...

From QA Survey feedback.

Comment 1

[Cameron Dawson [:camd]]

A Pivotal Tracker story has been created for this Bug: http://www.pivotaltracker.com/story/show/15005711

Comment 2

[Cameron Dawson [:camd]]

Cameron Dawson changed story state to unstarted in Pivotal Tracker

Comment 3

[Cameron Dawson [:camd]]

Cameron Dawson added a comment in Pivotal Tracker:   
   
Had an idea about this today:  What if we had a test case that WAS a precondition to other cases.  A "setup" case and a "teardown" case, perhaps.  It has steps, a description, attachments and all the stuff that's needed to build a good set of "setup" or "teardown" steps for a case (or set of cases in a suite).

SCREENCAST: In the short-term, I'll create a screencast "recipe" where the user creates the case and applies a tag of "pre-condition" to it.  Then reference that  (by URL in the description of other cases) as a set of steps that must be completed before the test case.

The thing is, it isn't really a test that passes or fails (though there could be failures in the preconditions, I suppose).  

Anyway, we should think about this and discuss it, perhaps.

Comment 4

[Stephen Donner [:stephend] Not actively reading bugmail]

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!