702853 - Case Conductor doesn't enable you to set order or testcases within test runs

Status: RESOLVED WONTFIX

(Mozilla QA Graveyard :: MozTrap, defect)

Description

[John Hammink]

This bug actually embodies two needed features:

In Battery API certain cases must precede or follow certain other cases (like testing .dischargingTime should be last because battery on device has to be in nearly discharged state - same with .charging Time). 

1. It must be possible to sort the testcases within the test runs.

However it seems that Case Conductor arbitrarily lumps testcases into a somewhat random order (not even the order they are by default after having been entered, activated, etc.

2.  CC should, by default, render testcases within test runs in the order of their creation - after search view (see url).

Comment 1

[Cameron Dawson [:camd]]

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

Comment 2

[Cameron Dawson [:camd]]

Cameron Dawson added a comment in Pivotal Tracker:   
   
I'm not sure we preserve much of a set order for cases in suites.

I think if we were able to sort by tags and/or suites that might solve this.  If you had tags on cases that must be done at the end, then you could sort so those were at the end.  

I wonder if it would be possible to sort the list by suite, and have the run list preserve the order they are set in the suite (presuming we keep ordered lists of tests in suites)

Comment 3

[Cameron Dawson [:camd]]

Cameron Dawson added a comment in Pivotal Tracker:   
   
default ordering should be what was set by the test suite creator.  then the user can reorder while testing, if they choose to.

Comment 4

[Cameron Dawson [:camd]]

Carl Meyer changed story state to started in Pivotal Tracker

Comment 5

[Cameron Dawson [:camd]]

Carl Meyer changed story state to unstarted in Pivotal Tracker

Comment 6

[Cameron Dawson [:camd]]

Cameron Dawson added a comment in Pivotal Tracker:   
   
carl: I believe you support the order in the schema, right?  Is it just up to eric now to implement support for that in the runtests page?

Comment 7

[Cameron Dawson [:camd]]

Cameron Dawson added a comment in Pivotal Tracker:   
   
the multi-select widget needs to provide order values.  so we would need Jonny on that.  And when re-activating runs, might get tricky resetting the ordering.  This would be for the cases of suites as well as the suites of runs.

Comment 8

[Cameron Dawson [:camd]]

Cameron Dawson added a comment in Pivotal Tracker:   
   
should support order of cases in a suite, then order of suites in a run.

Comment 9

[Cameron Dawson [:camd]]

Cameron Dawson changed story state to started in Pivotal Tracker

Comment 10

[Cameron Dawson [:camd]]

Cameron Dawson changed story state to finished in Pivotal Tracker

Comment 11

[Cameron Dawson [:camd]]

Cameron Dawson changed story state to delivered in Pivotal Tracker

Comment 12

[Cameron Dawson [:camd]]

Cameron Dawson changed story state to accepted in Pivotal Tracker

Comment 13

[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!