Stephend

Stub Attribution Notes/Test Plan (scratchpad)

Questions:

1. All (supported) Windows platforms, or?
2. Which locale(s)?
3. Entry-points on Mozilla.org/.com. Which page(s)? Or all download pages?
4. JavaScript enabled *and* disabled cases?
5. How/who checks the Telemetry ping from the client?
6. 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?

1. Manual Tests:
   1. Positive (happy-path) Tests:

1. 1. Negative Tests:
   2. Ensure other installers/binaries don't have/pass on the URL param/stub code
      1. e.g. Mac, Linux, full Firefox for Windows installers

1. Test Automation: