QA/Mobile/TelemetryTestPlan: Difference between revisions

QA/Mobile/TelemetryTestPlan (view source)

1,300 bytes added , 9 May 2019

glean cli

Confirmed users

487

edits

@@ Line 154: / Line 154: @@
 = Glean CLI =
+Below is a brief summary of the Glean CLI features documented here:  [https://github.com/mozilla-mobile/android-components/tree/master/components/service/glean#debugging-products-using-glean Debugging products using Glean]
 ''logPings''
@@ Line 170: / Line 172: @@
 == 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 baseline --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 baseline --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 baseline --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:
 =NOTES=