Update migration automated tests to test the extensions resource with the InternalTestingProfileMigrator
Categories
(Firefox :: Migration, task, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox116 | --- | fixed |
People
(Reporter: mconley, Assigned: mconley)
References
(Blocks 1 open bug, Regressed 1 open bug)
Details
Attachments
(2 files)
The browser_do_migration.js test intentionally skips testing the extensions resource for now because the testing infrastructure needs to be taught how to test the ending result of importing extensions. This task is to get those tests written.
|
||
Updated•3 months ago
|
|
Assignee | |
Updated•3 months ago
|
|
|
Assignee | |
Comment 1•3 months ago
|
||
|
|
Assignee | |
Comment 2•3 months ago
|
||
Depends on D182116
Pushed by mconley@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/397a3150e68c Update browser_do_migration test to test extensions resource migration. r=niklas https://hg.mozilla.org/integration/autoland/rev/da38525a017e Add more extension migration tests. r=niklas
|
||
Comment 4•3 months ago
|
||
Backed out for causing mochitest-chrome failures on test_history.html.
Pushed by imoraru@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/482b2f054ce2 Update browser_do_migration test to test extensions resource migration. r=niklas https://hg.mozilla.org/integration/autoland/rev/80adb872a3d1 Add more extension migration tests. r=niklas a=reland CLOSED TREE
|
|
||
Comment 6•3 months ago
•
|
||
Hi Mike! I have re-landed this. The reason for the backout were some backfills that pointed at your push as the culprit, but that was actually wrong, because there was a strange interaction when backfills combined with retriggers would pull dependencies from the wrong push.
Sorry for any inconvenience caused by this.
Thank you!
|
||
Comment 8•3 months ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/482b2f054ce2
https://hg.mozilla.org/mozilla-central/rev/80adb872a3d1
Description
•