Closed Bug 1333410 Opened 8 years ago Closed 8 years ago

Test animated /firstrun for new on-boarding experience

Categories

(www.mozilla.org :: Pages & Content, defect)

Production
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: agibson, Unassigned)

References

(Blocks 1 open bug)

Details

Blocks: 1322718
Erica's branch is now up on a demo for review / testing: https://bedrock-demo-ericawright.us-west.moz.works/en-US/firefox/51.0/firstrun/?f=99
I had to move this to demo1 for FxA iframe testing: https://www-demo1.allizom.org/en-US/firefox/51.0/firstrun/?f=99 Please ignore the URL in Comment 1
Just to be clear on variations: FC98 = control: existing installer, download page and first run FC99 = variation 1: updated download page, streamlined installer, auto-migration enabled, wow moment first run FC100 = variation 2: updated download page, streamlined installer, auto-migration DISABLED, wow moment first run This means the updated /firstrun page should only be displayed when f=99 or f=100 is in the URL. agibson: the updated first run template above should be loaded for \?f=(99|100)$
Flags: needinfo?(agibson)
(In reply to Chris More [:cmore] from comment #3) > Just to be clear on variations: > > FC98 = control: existing installer, download page and first run > FC99 = variation 1: updated download page, streamlined installer, > auto-migration enabled, wow moment first run > FC100 = variation 2: updated download page, streamlined installer, > auto-migration DISABLED, wow moment first run > > This means the updated /firstrun page should only be displayed when f=99 or > f=100 is in the URL. > > agibson: the updated first run template above should be loaded for > \?f=(99|100)$ For things relating to /firstrun please add them to Bug 1333410 (Erica is doing the dev work on this. I'll let her know, but let's try and avoid chinese whispers)
Flags: needinfo?(agibson)
Oops sorry, I cross posted into the wrong bug by mistake - you totally got this right the first time, my bad! :) Erica, can you please update as per Comment 3? Thanks
Flags: needinfo?(ewright)
Yes, it has been done - the url f=100 and f=99 both work. (sorry for the late reply, I don't often work with Bugzilla)
Flags: needinfo?(ewright)
Grover will be testing the end to end experience from /new to first run, lease confirm when it's ready for him to review.
Flags: needinfo?(agibson)
(In reply to Romain Testard [:RT] from comment #7) > Grover will be testing the end to end experience from /new to first run, > lease confirm when it's ready for him to review. A custom build of Firefox will be needed to open /firstrun on the demo server. Is that something someone is putting together? If not, he can test the individual parts on the demo servers linked in the respective bugs (or wait until all the parts are in production).
Flags: needinfo?(agibson)
(In reply to Alex Gibson [:agibson] from comment #8) > (In reply to Romain Testard [:RT] from comment #7) > > Grover will be testing the end to end experience from /new to first run, > > lease confirm when it's ready for him to review. > > A custom build of Firefox will be needed to open /firstrun on the demo > server. Is that something someone is putting together? If not, he can test > the individual parts on the demo servers linked in the respective bugs (or > wait until all the parts are in production). Alternatively he could also set the /firstrun URL via a preference in a custom profile (without requiring a different build).
Pref would be e.g: startup.homepage_welcome_url = 'https://www-demo1.allizom.org/%LOCALE%/firefox/%VERSION%/firstrun/?f=99'
> A custom build of Firefox will be needed to open /firstrun on the demo > server. Is that something someone is putting together? If not, he can test > the individual parts on the demo servers linked in the respective bugs (or > wait until all the parts are in production). This is done on bug 1326252. Grover, are you OK testing the different pieces separately or do you recommend waiting until everything is put together?
Flags: needinfo?(gwimberly)
Catching up on info for this bug, I have a few comments/questions: We test Funnelcake using the URL provided in Comment 2 and change our profiles with the preferences set in Comment 10? If so, then we will begin testing as soon as our test cases are looked over.
Flags: needinfo?(rtestard)
Flags: needinfo?(gwimberly)
Flags: needinfo?(agibson)
(In reply to Grover Wimberly IV [:Grover-QA] from comment #12) > Catching up on info for this bug, I have a few comments/questions: > > We test Funnelcake using the URL provided in Comment 2 and change our > profiles with the preferences set in Comment 10? > > If so, then we will begin testing as soon as our test cases are looked over. Yes, that should work in terms of showing the right page. To fully test the FxA signup flow, you may also need to create a custom profile using the instructions here: http://bedrock.readthedocs.io/en/latest/firefox-accounts.html#demo-server-testing This may or may not meet your requirements for a good end-to-end test. If it does not, you may want to wait until this page has finished in review and been pushed to production.
Flags: needinfo?(agibson)
Most of the test cases I've written cover end-to-end testing, so it might be best to wait until it's out of review. Please NeedInfo me when that is available.
Flags: needinfo?(agibson)
Flags: needinfo?(rtestard)
Commit pushed to master at https://github.com/mozilla/bedrock https://github.com/mozilla/bedrock/commit/645b187f8c50de9efd54ea3e43d278d6f179b41c [fix bug 1333410] - /firstrun for Firefox onboarding v2.0 experience
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
(In reply to Grover Wimberly IV [:Grover-QA] from comment #14) > Most of the test cases I've written cover end-to-end testing, so it might be > best to wait until it's out of review. Please NeedInfo me when that is > available. This is now in production: https://www.mozilla.org/en-US/firefox/51.0.1/firstrun/?f=99 https://www.mozilla.org/en-US/firefox/51.0.1/firstrun/?f=100
Flags: needinfo?(agibson)
Excellent! I had a meeting with several team members yesterday and we will be running through our tests today and Monday (if applicable)
You need to log in before you can comment on or make changes to this bug.