[about:welcome] Support running new migration wizard Fx113 experiment
Categories
(Firefox :: Messaging System, enhancement, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox113 | --- | verified |
People
(Reporter: pdahiya, Assigned: Mardak)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
To support running Fx113 migration wizard experiment on about:welcome
a) we should update explicit wait on AWMigrateClose , this explicit await won't work with new migration wizard and user will stay on import or easy setup screen from where SHOW_MIGRATION_WIZARD action is initiated
STR:
a) With patch https://phabricator.services.mozilla.com/D174326 on local build, open about:welcome
b) Set pref browser.migrate.content-modal.enabled
and browser.migrate.content-modal.auto-close-from-welcome
to true
c) Refresh about:welcome , navigate to import screen, click import
d) Completing import from about:preferences should autoclose about:preferences and return to about:welcome
[ Expected] User should auto navigate to next screen as import is completed
[Actual] User stays on import screen because of AWMigrateClose
await
b) Decide on which feature experiment should run . Experimenter link below uses 'migrationWizard' feature exposing migration wizard prefs that can be set via Nimbus
https://experimenter.services.mozilla.com/nimbus/new-import-interface-firefox-113/summary
Running experiment with 'migrationWizard' feature will load default about:welcome experience and the interaction telemetry received from about:welcome screens will use default message ids which probably should be ok if goal of the experiment is to measure import , retention and days of use
Other option is to run the experiment as aboutwelcome
feature adding the prefs needed under aboutwelcome
Assignee | ||
Comment 1•2 years ago
|
||
Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Comment 3•2 years ago
|
||
bugherder |
Comment 4•2 years ago
|
||
I’m marking this as Verified on 113 since this task was part of the work done on QA-1831, for which we sent a sign-off.
Description
•