Add generic marionette test that checks startup with a clean profile and verifies no error console messages are created
Categories
(Firefox :: General, task, P3)
Tracking
()
People
(Reporter: Gijs, Assigned: Gijs)
References
Details
Attachments
(1 file)
We keep having issues where people accidentally add console spam. This is annoying when debugging issues with users (and trying to find the salient bits), and often reflects errors in implementation/testing if they were not otherwise caught before landing in nightly.
To remedy this, I think it'd help if we added a marionette test that starts the browser with a clean new profile, and with an existing profile, and waits for startup to be complete (including all the idle tasks etc.) and then checks that there are no (pending) console messages.
We'll initially need an allowlist of things that already exist, but hopefully this would clamp down on patches that introduce new errors/message spam.
| Assignee | ||
Comment 1•3 years ago
|
||
Recent examples: bug 1813320, bug 1814688, bug 1743495, etc.
Comment 2•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'DevTools::Console' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Comment 3•3 years ago
|
||
| Assignee | ||
Updated•3 years ago
|
Updated•3 years ago
|
Comment 5•3 years ago
|
||
| bugherder | ||
Comment 6•3 years ago
|
||
Since nightly and release are affected, beta will likely be affected too.
For more information, please visit auto_nag documentation.
| Assignee | ||
Updated•3 years ago
|
Description
•