[remote-dbg-next] migrate aboutdebugging test: browser_addons_debug_webextension.js
Categories
(DevTools :: about:debugging, enhancement, P1)
Tracking
(firefox67 fixed)
Tracking | Status | |
---|---|---|
firefox67 | --- | fixed |
People
(Reporter: jdescottes, Assigned: jdescottes)
References
(Blocks 2 open bugs)
Details
(Whiteboard: old-remote-debugging-ng-m3)
Attachments
(6 files)
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review |
Assignee | ||
Comment 1•6 years ago
|
||
Assignee | ||
Comment 2•6 years ago
|
||
Assignee | ||
Comment 3•6 years ago
|
||
Assignee | ||
Comment 4•6 years ago
|
||
You can have a look at the following documentation for some tips on how to migrate tests: https://gist.github.com/juliandescottes/fecc426ac84600357259bf513cea744c
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 5•6 years ago
|
||
Small refactor that will be useful for the upcoming patches were we install
temporary extensions from existing XPI files
Assignee | ||
Comment 6•6 years ago
|
||
Depends on D17053 . Just renaming and moving the helper for consistency
Assignee | ||
Comment 7•6 years ago
|
||
Depends on D17054
The previous version only relied on a manifest, but it's not really flexible.
The XPI approach allows to define background scripts, which can be useful for
more tests.
Note: the old about:debugging supports both the manifest and the XPI approaches
but we should try to keep only one here to make it less complicated to write new
tests.
Assignee | ||
Comment 8•6 years ago
|
||
Depends on D17055
Added console to the name, otherwise a straightforward migration normally.
Assignee | ||
Comment 9•6 years ago
|
||
Depends on D17056
We started migrating the about:debugging tests to the new about:debugging folder.
I guess we should still apply the webextensions tag to them?
Assignee | ||
Comment 10•6 years ago
|
||
Assignee | ||
Comment 11•6 years ago
|
||
Depends on D17055
Sadly on Windows loading a temporary addon as an XPI will lock the file.
This means we cannot update the addon during the test and we cannot test
the reload feature on windows.
The only other solution I can see is to add again the alternate API using
the TemporaryExtension helper to install an "exploded" temporary extension.
I would really like to avoid that, I feel like it's already complicated to
know which method to use in order to install extensions, between temporary
extensions, regular extensions, file based extensions... I would like to
avoid adding yet another method just for one test.
Let me know what you think.
Comment 12•6 years ago
|
||
Comment 13•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/ce48248ceaf8
https://hg.mozilla.org/mozilla-central/rev/17f82957f62c
https://hg.mozilla.org/mozilla-central/rev/1b45bc69411d
https://hg.mozilla.org/mozilla-central/rev/2b7b8078a63a
https://hg.mozilla.org/mozilla-central/rev/c1bcc87a8c68
https://hg.mozilla.org/mozilla-central/rev/4935a429a2b7
Description
•