implement generate test report for Reporting API
Categories
(Remote Protocol :: Marionette, task, P3)
Tracking
(firefox148 fixed)
| Tracking | Status | |
|---|---|---|
| firefox148 | --- | fixed |
People
(Reporter: sefeng211, Assigned: sfarre)
References
Details
(Whiteboard: [webdriver:m18][webdriver:external], [wptsync upstream][webdriver:relnote])
Attachments
(1 file)
This is missing from our work for bringing our implementation up to date
https://www.w3.org/TR/reporting-1/#generate-test-report-command
| Reporter | ||
Comment 1•8 months ago
|
||
I looked into current failing tests, I expect these ones should start to pass (or come up with a new failure) one this is implemented.
bufferSize.html.ini
Disconnect.html.ini
generateTestReport-honors-endpoint.https.sub.html.ini
generateTestReport.html.ini
nestedReport.html.ini
Order.html.ini
Reporting-api-honors-limits.https.sub.html.ini
| Reporter | ||
Updated•8 months ago
|
| Assignee | ||
Comment 3•3 months ago
|
||
This is an implementation of a Marionette version of the WebDriver extension command outlined in Part 7.1 of the Reporting API spec: https://w3c.github.io/reporting/#generate-test-report-command
This command simulates the generation of a report for the purpose of testing, which is observed by any registered Reporting Observers and sent off to a specified endpoint.
The platform logic for this command lives in D250373.
Updated•3 months ago
|
| Assignee | ||
Updated•3 months ago
|
Updated•2 months ago
|
Comment 6•2 months ago
|
||
Backed out for causing non-unified build bustages on TestReportGenerator
| Assignee | ||
Comment 7•2 months ago
|
||
I'm on it. Building locally without unity build. Thread Ripper thankfully goes brrr.
Comment 9•2 months ago
|
||
| bugherder | ||
Updated•2 months ago
|
Updated•18 days ago
|
Description
•