Open
Bug 1741430
Opened 4 years ago
Add ability to run dom/l10n integration tests as if they were run in production.
Categories
(Core :: Internationalization: Localization, enhancement)
Core
Internationalization: Localization
Tracking
()
NEW
People
(Reporter: zbraniecki, Unassigned)
Details
The way MaybeReportErrorsToGecko works [0] is that it handles all possible errors very lightly in release and runtime (since users can't react), and strictly in automation (throw).
This allows us to catch errors early, but avoid having end users pay the cost in cases where we don't catch it.
The downside of this model is that we can't write tests for behavior that we'd like to see in production, since all tests run in by definition in automation.
It would be useful to add some flag to allow Localization class to act as if it operates in production.
For example:
Localization::SetRelaxedErrorHandling(true);
You need to log in
before you can comment on or make changes to this bug.
Description
•