Open
Bug 1229156
Opened 9 years ago
Updated 2 years ago
Test ServiceWorkerEvents error reporting (ex: respondWith, waitUntil)
Categories
(Core :: DOM: Service Workers, defect, P3)
Core
DOM: Service Workers
Tracking
()
NEW
People
(Reporter: bkelly, Unassigned)
References
(Blocks 2 open bugs)
Details
(Whiteboard: DWS_NEXT)
We have a devtools test that covers console.log() from a service worker. We should add something similar that checks for console error reporting when respondWith() fails, an exception is thrown, etc.
Reporter | ||
Updated•9 years ago
|
Blocks: dt-service-worker
Reporter | ||
Comment 1•9 years ago
|
||
I'm not currently working on this.
Assignee: bkelly → nobody
Status: ASSIGNED → NEW
Updated•8 years ago
|
Assignee: nobody → bugmail
Status: NEW → ASSIGNED
Comment 2•8 years ago
|
||
Were you thinking that these tests would be separate or should they piggy-back on the existing test coverage that triggers the error?
For example, https://dxr.mozilla.org/mozilla-central/source/dom/workers/test/serviceworkers/test_install_event.html covers the "throw in install" and "throw in activate" cases bug 1222720 wants better errors for. The test seems complicated enough already that adding the console error checking might make the test harder to understand.
OTOH, https://dxr.mozilla.org/mozilla-central/source/dom/workers/test/serviceworkers/test_unresolved_fetch_interception.html which covers one of the respondWith() failing cases is reasonably straightforward and probably could handle some extra logic.
I don't think I've worked with the dom/ codebase long enough to have an opinion or totally grok what constitute best practices or what the desired convention is. The trend I perceive is: new bugs get new tests, copying and pasting happens, not a lot of shared test support infrastructure beyond what SimpleTest.js and SpecialPowers offer.
Flags: needinfo?(bkelly)
Reporter | ||
Comment 3•8 years ago
|
||
I was thinking new tests so that it would be easier to copy the devtools logging stuff:
https://dxr.mozilla.org/mozilla-central/source/devtools/shared/webconsole/test/test_console_serviceworker.html
But I don't have a strong opinion here.
Flags: needinfo?(bkelly)
Reporter | ||
Updated•8 years ago
|
Updated•7 years ago
|
Priority: -- → P3
Comment 4•6 years ago
|
||
For context, we have existing tests at https://searchfox.org/mozilla-central/source/dom/serviceworkers/test/test_error_reporting.html which use the helpers at https://searchfox.org/mozilla-central/source/dom/serviceworkers/test/error_reporting_helpers.js. There is also a test at https://searchfox.org/mozilla-central/source/dom/serviceworkers/test/test_unresolved_fetch_interception.html#66 that uses the helpers.
For this bug, this basically means that we want to make sure that all of the errors reported via AsyncLog and ReportToAllClients in https://searchfox.org/mozilla-central/source/dom/serviceworkers/ServiceWorkerEvents.cpp are covered. This covers respondWith and waitUntil failures, in particular.
status-firefox45:
affected → ---
Whiteboard: DWS_NEXT
Updated•6 years ago
|
Assignee: bugmail → nobody
Status: ASSIGNED → NEW
Summary: test various types of service worker error reporting → Test ServiceWorkerEvents error reporting (ex: respondWith, waitUntil)
Updated•6 years ago
|
Assignee: nobody → ytausky
Status: NEW → ASSIGNED
Priority: P3 → P2
Updated•5 years ago
|
Assignee: ytausky → nobody
Status: ASSIGNED → NEW
Priority: P2 → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•