Confirm
586
edits
Changes
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
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 ==
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 ==
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>.
== Extension Signing Staging == Telemetry Experiments need to be signed to run in FF 42+, just like all other add-ons.
== Final Deployment ==
