Closed Bug 2017449 Opened 5 months ago Closed 5 months ago

Improve about:translations test events

Categories

(Firefox :: Translations, task)

task

Tracking

()

RESOLVED FIXED
150 Branch
Tracking Status
firefox150 --- fixed

People

(Reporter: nordzilla, Assigned: nordzilla)

References

(Blocks 1 open bug)

Details

Attachments

(1 file, 1 obsolete file)

Description

The about:translations page fires some events that are intended to help tests precisely track the flow of execution through the UI.

We should ensure that these events no-op and are not fired when we are not running in automation, so as not to add unneeded event calls while the page is running in production.

This commit reworks the test-only events fired by the about:translations
page, which help us adhere to precise event-based timing throughout tests,
to truly be fired as test-only events, instead doing a no-op if we are
not in automation.

This commit reworks the test-only events fired by the about:translations
page, which help us adhere to precise event-based timing throughout tests,
to truly be fired as test-only events, instead doing a no-op if we are
not in automation.

Attachment #9545925 - Attachment is obsolete: true
Attachment #9546218 - Attachment description: Bug 2017449 - Rework about:translations test events r=#translations-reviewers! → Bug 2017449 - Rework about:translations test events r=sfoster!
Pushed by smolnar@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/acb6f5bce700 https://hg.mozilla.org/integration/autoland/rev/6dfad38f2a7f Revert "Bug 2017449 - Rework about:translations test events r=sfoster" for causing bc failures @ browser_MLSuggest_integration.js

This is part of a single backout that spanned multiple bugs.

In the patch stack, I increased the timeout when waiting for a mocked RemoteSettings model to download within our Translations tests, hoping that it might also help to reduce intermittent Translations test failures.

There are a few ml related tests that share our Remote Settings mocks. This test case happens to wait for the full duration of the timeout as part of the success path of the test case.

I've reverted the timeout change, and everything should hopefully be fine now.

I would one day like to either fully separate this code, or unify it in a way that ml doesn't rely on Translations under the hood, so that its more clear where the downstream consumers are.

Flags: needinfo?(enordin)
Status: NEW → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
Target Milestone: --- → 150 Branch
QA Whiteboard: [qa-triage-done-c151/b150]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: