Confirmed users
586
edits
Telemetry/Experiments: Difference between revisions
Jump to navigation
Jump to search
Split QA testing into a separate section so I can link to it better, and squash the signing section since it's mostly covered in the "developing a telemetry experiment" page
(→Engineering: Remove stuff moved to the https://wiki.mozilla.org/QA/Telemetry/Developing_a_Telemetry_Experiment page) |
(Split QA testing into a separate section so I can link to it better, and squash the signing section since it's mostly covered in the "developing a telemetry experiment" page) |
||
| Line 4: | Line 4: | ||
Experiments can be targeted at various populations by specifying conditions in an experiment manifest. http://gecko.readthedocs.org/en/latest/browser/experiments/experiments/manifest.html has details on the possible conditions, and there it is also possible to write complex conditions in JavaScript which can filter on any data in the telemetry or Firefox Health Report payloads. | Experiments can be targeted at various populations by specifying conditions in an experiment manifest. http://gecko.readthedocs.org/en/latest/browser/experiments/experiments/manifest.html has details on the possible conditions, and there it is also possible to write complex conditions in JavaScript which can filter on any data in the telemetry or Firefox Health Report payloads. | ||
This page provides a high-level overview of the process to build and deploy an experiment. | |||
== Product Approval == | == Product Approval == | ||
| Line 16: | Line 18: | ||
Experiments are a special type of [https://developer.mozilla.org/en-US/Add-ons/Bootstrapped_extensions restartless extension]. They can do anything a regular restartless extension can do. Detailed instructions on the mechanics of developing and testing the experiment can be found at [[QA/Telemetry/Developing_a_Telemetry_Experiment|Developing a Telemetry Experiment]]. | Experiments are a special type of [https://developer.mozilla.org/en-US/Add-ons/Bootstrapped_extensions restartless extension]. They can do anything a regular restartless extension can do. Detailed instructions on the mechanics of developing and testing the experiment can be found at [[QA/Telemetry/Developing_a_Telemetry_Experiment|Developing a Telemetry Experiment]]. | ||
Note that Telemetry Experiments need to be signed to run in FF 42+, just like all other add-ons. There are more details on the signing process on the page linked above. | |||
== Extension Lifecycle == | == Extension Lifecycle == | ||
| Line 23: | Line 27: | ||
A few experiments are intended to collect data once and then uninstall themself. These experiments should uninstall themselves when done by calling <code>Experiments.disableExperiment("FROM_API")</code>. | A few experiments are intended to collect data once and then uninstall themself. These experiments should uninstall themselves when done by calling <code>Experiments.disableExperiment("FROM_API")</code>. | ||
== | == Staging == | ||
To deploy an experiment, write a patch to http://hg.mozilla.org/webtools/telemetry-experiment-server/ for experiment deployment, as described at [[QA/Telemetry/Developing_a_Telemetry_Experiment|Developing a Telemetry Experiment]], and bsmedberg or a peer can review. Pushes there auto-deploy to the staging server at https://telemetry-experiment-dev.allizom.org/. | |||
== QA Testing == | |||
== | |||
For experiments that involve a nontrivial amount of new code or changes, the QA team is available to verify the experience on the staging server, including data collection. To request QA sign-off, refer to the [[QA/Telemetry|QA Guide For Telemetry Experiments]] - [https://mozillians.org/en-US/u/RyanVM/ Ryan VanderMeulen] is the QA lead for experiments. | |||
== Final Deployment == | == Final Deployment == | ||