env specific tests not getting filtered out on test run

RESOLVED WONTFIX

Status

RESOLVED WONTFIX
7 years ago
8 days ago

People

(Reporter: camd, Unassigned)

Tracking

Details

(Reporter)

Description

7 years ago
Create a test run for a product with OS environments of windows and Linux
Create test case "TC1" with no environment narrowing
Create another test case "TC2" with environments narrowed down to windows only.
Execute the test run specifying the environment of Linux

Expect: to only see "TC1"
Actual: You see both test cases.  The narrowing is not being honored.
(Reporter)

Comment 1

7 years ago
A Pivotal Tracker story has been created for this Bug: http://www.pivotaltracker.com/story/show/28710251
(Reporter)

Comment 2

7 years ago
Cameron Dawson added a comment in Pivotal Tracker:   
   
Carl: this bug was pointed out to me, and I confirmed it's happening on 1.0.X and master.

I checked in a branch with a proposed fix.  However, the fix breaks a ton of other tests in that package.  So it may not be the right fix.  I added another test that fails without my fix and passes with it applied.

Please take a look when you can and advise.  Perhaps it's the right fix and I just need to fix all the other tests?  :)
(Reporter)

Comment 3

7 years ago
Cameron Dawson added a comment in Pivotal Tracker:   
   
actually, I fixed the tests.  I just had to add environments=self.envs to the defaults in the create_rcv method.  So all the test pass now with the fix applied.
(Reporter)

Comment 4

7 years ago
Cameron Dawson changed story state to started in Pivotal Tracker
(Reporter)

Comment 5

7 years ago
Carl Meyer changed story state to delivered in Pivotal Tracker
(Reporter)

Comment 6

7 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
Last Resolved: 2 years ago
Resolution: --- → WONTFIX

Updated

8 days ago
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.