User:Stephend: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
''' Stub Attribution Notes/Test Plan (scratchpad) '''
= Stub Attribution Notes/Test Plan (scratchpad) =


= Dependencies (tools/systems): =
= Dependencies (tools/systems): =
* [https://github.com/mozilla-services/go-bouncer Bouncer]
* [https://github.com/mozilla-services/go-bouncer Bouncer]


= Questions: =
== Questions: ==
# All (supported) Windows platforms, or?
# All (supported) Windows platforms, or?
# Do Not Track support
# Do Not Track support
Line 20: Line 20:
### do we still check for this ping?
### do we still check for this ping?


= Manual Tests: =
== Manual Tests: ==
# Positive (happy-path) Tests:
# Positive (happy-path) Tests:
## Do Not Track disabled
## Do Not Track disabled


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


= Test Automation: =
== Test Automation: ==




{{VerifiedUser}}
{{VerifiedUser}}

Revision as of 21:12, 24 August 2016

Stub Attribution Notes/Test Plan (scratchpad)

Dependencies (tools/systems):

Questions:

  1. All (supported) Windows platforms, or?
  2. Do Not Track support
    1. Which specific browsers (vendors + versions) properly support it/if have it enabled, we'll honor the setting?
  3. Which locale(s)?
  4. Entry-points on Mozilla.org/.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?)
  5. JavaScript enabled *and* disabled cases?
  6. How/who checks the Telemetry ping from the client?
  7. 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?

Manual Tests:

  1. Positive (happy-path) Tests:
    1. Do Not Track disabled

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

Test Automation: