Open Bug 1836373 Opened 1 years ago Updated 1 year ago

Risk of messages in tree causing failures of random automated tests

Categories

(Firefox :: Messaging System, defect, P3)

defect

Tracking

()

People

(Reporter: aminomancer, Unassigned)

References

(Blocks 1 open bug)

Details

Messaging is generally enabled during tests since it's enabled by default. This doesn't usually cause too many problems since most of our messages trigger in very specific conditions so they don't come up during automated tests. But in some cases, messages that work fine in experiments will cause problems when landing in tree (see bug 1831144 for example - the message unexpectedly appears on startup when other tests, unrelated to FxMS, are running).

There might be an easy way to disable this specific message during automated tests by just changing its targeting. Then, our own tests can enable it so they can test on it, but the rest of Firefox's browser tests don't need to be edited to account for it. But since this isn't really a problem with this specific message, but a universal risk for all messages with lenient enough trigger/targeting, we should consider a more universal approach to fixing this. For example, disable ASRouter entirely when a pref is set, and set that pref in some file that runs as part of the test harness, or something.

Priority: -- → P3

The severity field is not set for this bug.
:lsmith, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(lsmith)
Severity: -- → N/A
Flags: needinfo?(lsmith)

The severity field is not set for this bug.
:lsmith, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(lsmith)
Severity: N/A → S4
Flags: needinfo?(lsmith)
You need to log in before you can comment on or make changes to this bug.