Closed Bug 1511312 Opened 6 years ago Closed 5 years ago

Fix update tests to set "app.update.disabledForTesting" to False

Categories

(Testing :: Firefox UI Tests, enhancement, P2)

enhancement

Tracking

(firefox65 fixed, firefox66 fixed)

RESOLVED FIXED
mozilla66
Tracking Status
firefox65 --- fixed
firefox66 --- fixed

People

(Reporter: whimboo, Assigned: whimboo)

References

Details

Attachments

(1 file)

With bug 1508726 application updates are disabled with "app.update.disabledForTesting" set to True. To allow update tests to continue to work this preference has to be set to False.

Note that this also needs bug 1511311 to be fixed first.
Assignee: nobody → hskupin
Status: NEW → ASSIGNED
Priority: -- → P2
Pushed by hskupin@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/dafa583b9dfb
[fxui] Re-enable update permissions for update tests. r=ato
https://hg.mozilla.org/mozilla-central/rev/dafa583b9dfb
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla66
Please uplift this test-only patch to beta.
Whiteboard: [checkin-needed-beta]
Whiteboard: [checkin-needed-beta]

FYI: we're planning on removing the old UI during the next cycle.

Flags: needinfo?(hskupin)

Thanks for the heads-up. I will keep an eye on bug 1515484. Basically the tests should continue to work, unless some new ui is added. And the only necessary work for us would be to remove the old code afterward. But that is very low priority those days.

Flags: needinfo?(hskupin)

You should be able to check by removing the app.update.doorhanger pref or setting it to true since setting that to false is what turns on the old UI.
https://searchfox.org/mozilla-central/source/testing/firefox-ui/harness/firefox_ui_harness/runners/update.py#18

We never implemented the doorhanger. All update tests are actually running against the about window. I assume with bug 1515484 you only remove the old software update window, but not the update functionality from the about window?

Flags: needinfo?(robert.strong.bugs)

That is correct and I'll also be removing the app.update.doorhanger pref which you added so the tests can run against the old update UI. Since you aren't using the old Update UI you should remove that pref to make certain your tests aren't relying on it in some way.

Flags: needinfo?(robert.strong.bugs)

Lets move further discussion (if necessary) over to bug 1552771. Thanks.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: