[remote-dbg-next] migrate aboutdebugging test: browser_service_workers_status.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
(3 files)
Assignee | ||
Comment 1•7 years ago
|
||
Assignee | ||
Comment 2•7 years ago
|
||
Assignee | ||
Comment 3•7 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
|
||
In its current shape the existing test in about:debugging is not testing anything interesting comparing to our existing tests. It simply waits for a serviceworker to reach the stopped state, but we already do that as a prerequisite to most of our service worker tests.
To design a stable test here we would need to be able to drive the "registering", "starting" and "stopped" phases of the service worker from the test page. I will try to do this, but if it seems too complicated let's move this to P3 or outside of m2 directly since it's not a gap.
Assignee | ||
Comment 6•6 years ago
|
||
Depends on D17555
Not necessary, but one less react warning in the logs :)
Assignee | ||
Comment 7•6 years ago
|
||
Depends on D17629
Small leftover from previous bugs
Assignee | ||
Comment 8•6 years ago
|
||
Depends on D17630
I am not mentioning the original test in the test file because they are not similar.
Original test was not actually testing anything interesting for us.
Comment 10•6 years ago
|
||
Comment 11•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/3b9416e476b7
https://hg.mozilla.org/mozilla-central/rev/8c7f41867ac7
https://hg.mozilla.org/mozilla-central/rev/d2e4d4ff466b
Description
•