Remove `browser.nova.enabled=false` coverage from profiles tests
Categories
(Toolkit :: Startup and Profile System, task)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox161 | --- | fixed |
People
(Reporter: sclements, Assigned: akulyk)
References
(Blocks 1 open bug)
Details
(Whiteboard: [recomp])
Attachments
(1 external file)
Bug 2082898 locks browser.nova.enabled to true. Before that can happen, tests that set the pref to false or branch on that value need to be removed so only the Nova behavior is tested. Do not remove any code behind browser.nova.enabled=false outside of test directories or configuration; that cleanup needs to happen after the pref is locked.
Tests to clean up:
browser/components/profiles/tests/browser/browser_create_profile_page_test.js
browser/components/profiles/tests/browser/browser-legacy.toml runs the profiles tests with browser.nova.enabled=false and should be removed.
Updated•1 month ago
|
Updated•1 month ago
|
Comment 1•28 days ago
|
||
A couple more notes here:
- There are some conditional Nova pref checks that should be cleaned up in
/browser/components/profiles/tests/browser/browser_create_profile_page_test.js, for example this one - We can remove
browser/components/profiles/tests/browser/browser_create_profile_page_test.jsandbrowser_test_current_theme_from_amo.jssince they both only run as part of the legacy manifest (the latter is for functionality we no longer support in the new theme picker)
Updated•26 days ago
|
Updated•26 days ago
|
browser.nova.enabled is about to be locked to true, so the legacy manifest
and the tests for the legacy theme picker are removed.
browser_edit_profile_test.js only ran in the legacy manifest, so its tasks
that don't involve the theme picker move to browser.toml.
Theme selection telemetry is now checked through theme_picker.change,
which the shared picker records.
Comment 4•18 days ago
|
||
| bugherder | ||
Updated•6 days ago
|
Description
•