Fix bogus test_reload in test_delay_update_webextension.js
Categories
(Toolkit :: Add-ons Manager, task, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox71 | --- | fixed |
People
(Reporter: zombie, Assigned: zombie)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
I found this while working on https://phabricator.services.mozilla.com/D44368#inline-270225
The test finishes before the runtime.reload()
call takes effect, effectively testing nothing.
The await extension.awaitStartup()
line is returning immediately because it's awaiting the already resolved promise from the first extension startup from the top of the test.
Adding a wait of 1 second leaves time for extension to restart and to send the "ready" message again.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
Pushed by tjovanovic@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/62de619a3d75 Fix test_delay_update_webextension to actually wait for extension startup after restart r=robwu
Comment 3•5 years ago
|
||
bugherder |
Comment 4•5 years ago
•
|
||
Hello,
Will this fix require manual validation or is it covered by automated tests? If yes, please provide some steps to reproduce in order to correctly test it and also, please set the "qe-verify+" flag.
Otherwise, could the "qe-verify-" flag be added? Thank you.
Updated•5 years ago
|
Assignee | ||
Comment 5•5 years ago
|
||
Not needed, thanks.
For future reference, test-only changes can't have a visible effect in product, so manual verification is not possible, and so obviously never needed.
Comment 6•5 years ago
|
||
It did seem rather obvious but we needed the confirmation and for the issue to have that flag, otherwise it would continue to show up in our queries containing work to be done.
Thank you for the details.
Description
•