Closed Bug 1511071 Opened Last year Closed 9 months ago
QA test plan for Return to AMO
67.2 - Feb 11 - 24
This bug is to discuss how we plan on end-to-end test the new Return to AMO feature. Right now we can test the UI portion of Return to AMO by "faking" some attribution in Activity Stream dev tools. The instructions on how to test that are found here: https://github.com/mozilla/activity-stream/pull/4578#issue-233701010. This sets the attribution and allows us to see the UI. We need a plan for testing the entire flow, start to finish: 1. Without Firefox installed, 2. Navigate to https://addons.mozilla.org via another browser (Chrome for example) 3. Find an add-on and click the "Only with Firefox - Get Firefox Now" button 4. Install Firefox and start it up 5. Observe that we see the Return to AMO flow with the correct add-on that we were trying to install in the other browser Shane mentioned there are some scripts that we can drop to add attribution to a Nightly build, and then we can start that Nightly and observe that the attribution got picked up from the build, and therefore we see the Return to AMO UI. There are also ways to test that the attribution gets set from AMO into a build. Testing these two pieces separately may be enough to get GREEN sign-off from QA if we don't have a way to end-to-end test the entire flow. Shane and David, feel free to add any other context you have to this bug.
NI to pmac, whom we spoke to about how attribution works. (Paul, this supersedes my email.) If there's already a way to test attribution end-to-end (from initiating installation from a mozilla property to verifying the attribution is there in Nightly), we could use that here. If there isn't already a way to do that, then recommendations are welcome. We're looking to land this in 65 and QA is blocked on this.
If all that is required on the www.m.o side is for query params to exist on the download page, then you should just manually be able to add them to the download URL. e.g. https://www.mozilla.org/en-US/firefox/download/thanks/?utm_source=return-to-amo I know that doesn't test the whole flow, but that should test that the data from the URL makes it into the installed Firefox. If the AMO button links directly to that URL then no further website changes are necessary. If you'll be linking to /firefox/new/ instead (which I do recommend btw. I feel it's a jarring UX to land on a new website and immediately start downloading) then a full test will need to wait until we pass the parameters over to the /thanks/ page. If you just need to test windows however, it should work now. It's the Mac attribution that doesn't fully work yet.
scratchpad script to output attribution codes to console, both windows and osx.
osx command line script to dump the attributes for any given downloaded app
Outlines how to test a new download for attribution data, requires other scripts attached.
Instructions to test nightly on osx and see the attribution UI in about:welcome.
adds windows test
Attachment #9028750 - Attachment is obsolete: true
Assignee: nobody → andrei.br92
Iteration: 66.2 - Dec 24 - Jan 6 → 66.3 - Jan 7 - 20
Priority: P2 → P1
Iteration: 66.3 - Jan 7 - 20 → 66.4 - Jan 21 - 27
Assignee: andrei.br92 → tspurway
Iteration: 66.4 - Jan 21 - 27 → 67.1 - Jan 28 - Feb 10
Iteration: 67.1 - Jan 28 - Feb 10 → 67.2 - Feb 11 - 24
Status: NEW → RESOLVED
Closed: 9 months ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 9 months ago → 9 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.