browser-chrome test name not logged
Categories
(Remote Protocol :: Agent, defect, P1)
Tracking
(firefox73 fixed)
| Tracking | Status | |
|---|---|---|
| firefox73 | --- | fixed |
People
(Reporter: ato, Assigned: ato)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [puppeteer-beta-mvp])
Attachments
(2 files)
Because we override add_task() in bc tests, the test name (function name) of the underlying test is lost:
INFO - Entering test bound
INFO - TEST-PASS | remote/test/browser/browser_agent.js | remote-listening observer not notified -
INFO - TEST-PASS | remote/test/browser/browser_agent.js | expected default port 49405, but got 49405 -
INFO - Leaving test bound
This is logged in browser-test.js:1060:
this.SimpleTest.info("Entering test " + task.name);
| Assignee | ||
Updated•6 years ago
|
Comment 1•6 years ago
|
||
Nothing on bug 1589625 actually changed that behavior. It only refactored the code. The custom add_task implementation was already present before. So why do you think it has been caused by bug 1589625? Did you test that? I feel this problem exists since bug 1537768.
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Comment 2•6 years ago
|
||
The documentation for the overridden add_task() is quite poor.
Document it as to not confuse new developers why it is behaving
differently to the default bc add_task().
DONTBUILD
Updated•6 years ago
|
| Assignee | ||
Comment 3•6 years ago
|
||
The browser-chrome test name is derived from the function name.
The function name of the original task is lost when wrapped inside
the add_task() override in remote/test/browser/head.js.
This fixes the problem by rewriting the taskFn name on the new wrapper.
Updated•6 years ago
|
Updated•6 years ago
|
Comment 5•6 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/7b207b360a5d
https://hg.mozilla.org/mozilla-central/rev/f61815665e1f
Updated•3 years ago
|
Description
•