QA/Mobile/TelemetryTestPlan: Difference between revisions

QA/Mobile/TelemetryTestPlan (view source)

1,083 bytes removed , 9 May 2019

m

remove

Confirmed users

487

edits

@@ Line 152: / Line 152: @@
 === Verify Metrics Info ===
 === Verify Custom Info ===
-= Examples =
-For running the commands with any Firefox Android app, adjust the application ID part in the command:
-== Fenix ==
-* <code>adb shell -n org.mozilla.fenix/mozilla.components.service.glean.debug.GleanDebugActivity --ez logPings true --es sendPing metrics --es tagPings rpapa-test1</code>
-==Android Components (sample apps)==
-* <code>adb shell -n org.mozilla.samples.glean/mozilla.components.service.glean.debug.GleanDebugActivity --ez logPings true --es sendPing metrics --es tagPings rpapa-test1</code>
-==Reference Browser==
-* <code>adb shell -n org.mozilla.reference.browser.debug/mozilla.components.service.glean.debug.GleanDebugActivity --ez logPings true --es sendPing metrics --es tagPings rpapa-test1</code>
-* NOTE
-** even with telemetry enabled, reference-browser doesn't define any metric outside of the ones we provide out of the box, which are sent in the ''baseline'' ping.
-** suggestion: run commands against a version of reference-browser that has telemetry enabled (e.g. the one from the play store), and send a ping for which we're sure to have data:
 = Glean CLI =