User:Stephend: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 6: Line 6:
Questions:
Questions:
# All (supported) Windows platforms, or?
# All (supported) Windows platforms, or?
# Do Not Track support
## Which specific browsers (vendors + versions) properly support it/if have it enabled, we'll honor the setting?
# Which locale(s)?
# Which locale(s)?
# Entry-points on Mozilla.org/.com.  Which page(s)?  Or all download pages?
# Entry-points on Mozilla.org/.com.  Which page(s)?  Or all download pages?
## https://www.mozilla.org/en-US/firefox/all/
## https://www.mozilla.org/en-US/firefox/new/?scene=2 (and do the ?scene=[] parameters matter?)
# JavaScript enabled *and* disabled cases?
# JavaScript enabled *and* disabled cases?
# How/who checks the Telemetry ping from the client?
# How/who checks the Telemetry ping from the client?
Line 18: Line 22:
# Manual Tests:
# Manual Tests:
## Positive (happy-path) Tests:
## Positive (happy-path) Tests:
### Do Not Track disabled


## Negative Tests:
## Negative Tests:

Revision as of 21:08, 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?
  1. Manual Tests:
    1. Positive (happy-path) Tests:
      1. Do Not Track disabled
    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: