QA/Telemetry/Developing a Telemetry Experiment: Difference between revisions

Jump to navigation Jump to search
more info
(more build info)
(more info)
Line 37: Line 37:
** <code>python -m SimpleHTTPServer 8080</code>
** <code>python -m SimpleHTTPServer 8080</code>
* Now it's a good opportunity to check if everything worked. Visit http://localhost:8080 if your normal web browser to see if a page shows up and it has the correct information, similar to [http://telemetry-experiment.cdn.mozilla.net/ the production page].
* Now it's a good opportunity to check if everything worked. Visit http://localhost:8080 if your normal web browser to see if a page shows up and it has the correct information, similar to [http://telemetry-experiment.cdn.mozilla.net/ the production page].
* Verify that the information about your experiment is correct
* Verify that the information about your experiment is correct.
* Also verify that the generated firefox-manifest.json is there at http://localhost:8080/firefox-manifest.json
 
== Testing everything ==
 
* '''Very important''': before testing, you need to make sure that telemetry is enabled (which it isn't for a local build). On a local build, you can use <code>export MOZ_TELEMETRY_REPORTING=1</code> in your mozconfig, or set '''toolkit.telemetry.enabled''' to true.
* '''Also important''', if you built locally, your update channel will be ''default'', which probably won't match what you specified in your manifest. Add ''default'' to your experiment manifest or test with a correct nightly/aurora/beta build.
 
To test things, you need to set up a number of prefs:
 
** '''devtools.chrome.enabled = true''', in order for the Browser Console to show up
** '''toolkit.telemetry.enabled = true''', telemetry must be enabled
** '''experiments.manifest.uri = http://localhost:8080/firefox-manifest.json''', full path to your generated firefox-manifest.json
** '''experiments.logging.enabled = true''', for logging
** '''experiments.logging.level = 0''', more logging
** '''extensions.logging.enabled = true''', even more logging from the Add-ons Manager
 
== Testing on Beta ==
 
If you're testing on beta or release, you'll '''need''' to have the XPI signed, or rebuild beta to remove the requirement that experiments be signed, by [http://mxr.mozilla.org/mozilla-central/source/toolkit/mozapps/extensions/internal/XPIProvider.jsm?rev=002d7897c93c#240 removing this line].
Confirmed users
371

edits

Navigation menu