Engagement/Mozilla.org Durable Team/Testing Playbook: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 2: Line 2:
## Why test?
## Why test?
### Testing gives us data to optimize user experience, leading to increased conversion (downloads, Accounts sign ups, newsletter sign ups, etc) supporting key performance indicators.
### Testing gives us data to optimize user experience, leading to increased conversion (downloads, Accounts sign ups, newsletter sign ups, etc) supporting key performance indicators.
## Test tracker
## [https://docs.google.com/spreadsheets/d/1BSAR6EJj_lToGNNNp3k9RjRTlGcVrpRfZvEw9OwH_88/edit#gid=0 Test tracker]
# Planning.  Define the following in bugzilla/google docs linked from wiki page:
# Planning.  Define the following in bugzilla/google docs linked from wiki page:
## Hypothesis
## Hypothesis
Line 27: Line 27:
##### Basic user-agent  
##### Basic user-agent  
## Review  
## Review  
### Checklist for reviewing Optimizely set up
### [https://gist.github.com/jpetto/30396fbfdd62794d8e02 Checklist] for reviewing Optimizely set up
#### Does test look and work as expected on demo server?
#### Does test look and work as expected on demo server?
#### Are correct measurements being reported in GA?
#### Are correct measurements being reported in GA?
Line 35: Line 35:
# Next steps
# Next steps
## Review results
## Review results
### Data studio links on wiki page
### [https://datastudio.google.com/#/reporting/0B6voOaUZL-jwcGg1ZVZvSUJ4dUU Newsletter conversion]
### Deploy winning tests globally with L10N team
### [https://docs.google.com/presentation/d/15izvYKdGkCdczRu1jjjsid2KbNqAiezknH7AnQeDwto/edit?ts=56e33125#slide=id.p Participation tasks]
### Define additional hypotheses and tests based on test data
## Deploy winning tests globally with L10N team
## Define additional hypotheses and tests based on test data
Confirmed users
55

edits