Change the about:profiling test assertion so it doesn't fail frequently when a new feature is added
Categories
(DevTools :: Performance Tools (Profiler/Timeline), task, P3)
Tracking
(firefox127 fixed)
Tracking | Status | |
---|---|---|
firefox127 | --- | fixed |
People
(Reporter: canova, Assigned: canova)
Details
Attachments
(1 file)
We have this assertion in the browser_interaction-between-interfaces.js test that fails every time we add a new feature that's enabled by default.
But if you look at the comment above, it doesn't really test the features, it only tests the threads filter. And specifically it's testing a special path that is executed where the changed thread list has same amount of threads. So it's really not necessary to check all the features. It's better to remove these checks and simplify it since it has caused multiple backouts in the past.
Assignee | ||
Comment 1•10 months ago
|
||
Previously this assertion was checking the whole preset values, including
interval, threads list and the enabled features. But if you look at the info
message above, it actually only intends to test a specific edge case of a
threads filter. So it's not really necessary to check the interval and the
features since that's not really important for this assertion.
I initially wanted to change this assertion because it caused multiple backouts
in the past when we changed the default values of some features. I think it's
better to not check the features here at all to make sure that we won't have
any more backouts in the future.
Updated•10 months ago
|
Assignee | ||
Updated•9 months ago
|
Updated•9 months ago
|
Comment 3•9 months ago
|
||
bugherder |
Description
•