Fix update tests to set "app.update.disabledForTesting" to False
Categories
(Testing :: Firefox UI Tests, enhancement, P2)
Tracking
(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 | ||
Comment 1•5 years ago
|
||
Assignee | ||
Updated•5 years ago
|
Pushed by hskupin@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/dafa583b9dfb [fxui] Re-enable update permissions for update tests. r=ato
Comment 3•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/dafa583b9dfb
Assignee | ||
Comment 4•5 years ago
|
||
Please uplift this test-only patch to beta.
Comment 5•5 years ago
|
||
bugherder uplift |
https://hg.mozilla.org/releases/mozilla-beta/rev/4449dde0dd98
Updated•5 years ago
|
Comment 6•5 years ago
|
||
FYI: we're planning on removing the old UI during the next cycle.
Assignee | ||
Comment 7•5 years ago
|
||
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.
Comment 8•5 years ago
|
||
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
Assignee | ||
Comment 9•5 years ago
|
||
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?
Comment 10•5 years ago
|
||
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.
Assignee | ||
Comment 11•5 years ago
|
||
Lets move further discussion (if necessary) over to bug 1552771. Thanks.
Description
•