Closed Bug 1163684 Opened 6 years ago Closed 6 years ago

Disable all functional and remote tests except security tests

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect)

defect
Not set
normal

Tracking

(firefox38 disabled, firefox39 disabled, firefox40 disabled, firefox-esr31 disabled, firefox-esr38 disabled)

RESOLVED FIXED
Tracking Status
firefox38 --- disabled
firefox39 --- disabled
firefox40 --- disabled
firefox-esr31 --- disabled
firefox-esr38 --- disabled

People

(Reporter: whimboo, Assigned: whimboo)

Details

(Whiteboard: [mozmill-test-failure])

Attachments

(2 files)

We recently have massive amounts of test failures for our mozmill tests and I absolutely don't have the time to partially skip them once failures are starting to occur. So I discussed a complete disabling of the test with Robert and Otilia via IRC and we all agree to that. It's even something we wanted to do already end of last quarter but I was in the hope partially disabling tests will still give us a better test coverage. But the maintenance burden is simply too high.

So we will disable all functional tests, and all remote tests except the security ones. The latter will be replaced soon by the Marionette tests. The same applies to update tests, which I will also replace soon. Both for Nightly first and then riding the train, or if all works well, even with backports so we can reach 38ESR.
Given that the security tests will be the first ones to transition over to Marionette, i will also leave the functional ones enabled. Those are not failing, and we can better keep up with regressions which would also affect the Marionette tests.
Summary: Disable all functional and remote tests except remote security tests → Disable all functional and remote tests except security tests
Attached patch skipSplinter Review
Assignee: nobody → hskupin
Status: NEW → ASSIGNED
Attachment #8604213 - Flags: checkin+
Somehow on esr31 all functional tests got skipped. Sorry for that. This patch will re-enable the security tests which we should still run.
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.