Stephend

Dependencies (tools/systems):

• Bouncer
• Mozilla.org (Bedrock)
• Telemetry

Questions:

1. All (supported) Windows platforms, or?
2. Which Firefox editions?
   1. Developer Edition?
   2. Firefox Extended Support Release Edition?
3. How to test (all five?) codes/fields?
   1. Source
   2. Medium
   3. Campaign
   4. Content
   5. "Referrer" alone?
4. Do Not Track support
   1. How/does JavaScript-disabled interplay with DNT?
      1. Which specific browsers (vendors + versions) properly support it/if have it enabled, we'll honor the setting?
5. Which locale(s)?
6. Entry-points on Mozilla.com. Which page(s)? Or all download pages?
   1. https://www.mozilla.org/en-US/firefox/all/
   2. https://www.mozilla.org/en-US/firefox/new/?scene=2 (and do the ?scene=[] parameters matter?)
7. JavaScript enabled *and* disabled cases?
   1. Should the attribution code(s) be present on Download buttons when JavaScript is disabled?
8. How/who checks the Telemetry ping from the client? Via Dashboard?
9. Do we need to cover the upgrade-path scenario? i.e.:
   1. user downloads and installs using the special stub installer w/tracking code
   2. we verify correct pings, etc.
   3. user upgrades later to a newer version of Firefox (pave-over install)
      1. do we still check for this ping?
10. How about the successfully installed, then uninstalled case: check to see that client no longer sends ping?

Manual Tests:

1. Positive (happy-path) Tests:
   1. Do Not Track disabled
      • Click an ad banner or link which has an attribution (source? medium? campaign? content? referrer?) code
      • Verify that the URL which takes you to a Mozilla.org download page contains a stub_attcode with a valid param
      • Verify that the same valid stub_attcode param/value gets passed to the Mozilla.org Download Firefox button
      • Download and install the stub installer
      • Verify (how?) that upon successful installation, the stub installer sends a "success!" ping with the same stub_attcode param/value
      • Verify (need specific Windows registry key, here) that the stub_attcode gets written to the registry/on-disk (need to double-check this) with appropriate value(s)
        • ...which are?

Negative Tests:

1. Ensure other installers/binaries don't have/pass on the URL param/stub code
   1. e.g. Mac, Linux, full Firefox for Windows installers
2. Much, much more to flesh out, here

Test Automation Coverage:

• What will the Bedrock unit tests cover?
  • Where/how frequently will they run? With each pull request/commit/release?
• What will the Bouncer tests cover?
  • Where/how frequently will they run? With each pull request/commit/release? On a cron?

References

• Stub Attribution wiki
• Stub Attribution project's checkin notes (Google Doc)