Closed
Bug 1287591
Opened 9 years ago
Closed 9 years ago
The application should not be started and left open if evaluation of manifest files do not find any test
Categories
(Remote Protocol :: Marionette, defect)
Remote Protocol
Marionette
Tracking
(firefox51 fixed)
RESOLVED
FIXED
mozilla51
Tracking | Status | |
---|---|---|
firefox51 | --- | fixed |
People
(Reporter: whimboo, Assigned: whimboo)
References
Details
Attachments
(1 file, 1 obsolete file)
If you run one of the marionette test commands via mach, and no tests can be found AFTER evaluating the manifest files for eg. tags, we spawn the application but do not close it anymore. Here an example:
mach firefox-ui-update --binary /mozilla/bin/nightly/firefox testing/firefox-ui/tests/functional/keyboard_shortcuts/manifest.ini
For the update tests we are looking for a specific tag in the manifest which is not present for functional tests. As result Firefox gets opened and stays open forever. We should really stop the instance if we launched it ourselves.
Assignee | ||
Comment 1•9 years ago
|
||
Review commit: https://reviewboard.mozilla.org/r/67458/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/67458/
Assignee | ||
Updated•9 years ago
|
Attachment #8775269 -
Flags: review?(dburns)
Assignee | ||
Comment 2•9 years ago
|
||
Anjana, we decided to land this without a harness unit test. If you think that one should be added, would you mind doing it? The pre-condition is an empty manifest file you specify for the tests. Thanks.
Assignee: nobody → hskupin
Status: NEW → ASSIGNED
Flags: needinfo?(anjanavakil)
Comment 3•9 years ago
|
||
Comment on attachment 8775269 [details]
Bug 1287591 - The application should not be started and left open if filtering of a single manifest file does not find any test
https://reviewboard.mozilla.org/r/67458/#review65184
Attachment #8775269 -
Flags: review?(dburns) → review+
Comment 4•9 years ago
|
||
(In reply to Henrik Skupin (:whimboo) from comment #2)
> Anjana, we decided to land this without a harness unit test. If you think
> that one should be added, would you mind doing it? The pre-condition is an
> empty manifest file you specify for the tests. Thanks.
Sure - I'm adding a test to make sure that `self.marionette` and `self.httpd` get reset to `None` after trying to call `run_tests` with a manifest with no active tests. For me, the test fails before applying the patch you submitted for this bug, and passes after applying it. Let me know what you think!
Flags: needinfo?(anjanavakil)
Comment 5•9 years ago
|
||
Add a test to make sure that if an empty manifest, or one with no active tests,
is provided, Marionette/Firefox are shut down as expected (previous behavior
was that the Marionette cleanup was never reached in this scenario).
Review commit: https://reviewboard.mozilla.org/r/68308/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/68308/
Attachment #8776594 -
Flags: review?(hskupin)
Updated•9 years ago
|
Attachment #8776594 -
Attachment is obsolete: true
Attachment #8776594 -
Flags: review?(hskupin)
Pushed by hskupin@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c77f60f1fef9
The application should not be started and left open if filtering of a single manifest file does not find any test r=automatedtester
Comment 7•9 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
status-firefox51:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla51
Updated•2 years ago
|
Product: Testing → Remote Protocol
You need to log in
before you can comment on or make changes to this bug.
Description
•