QA/Mobile/TelemetryTestPlan: Difference between revisions

Jump to navigation Jump to search
m
examples
(test tools)
m (examples)
Line 170: Line 170:
#* Open Android Studio to monitor all client-side activity
#* Open Android Studio to monitor all client-side activity


= Glean CLI =
== 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]
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]
Line 179: Line 179:


''sendPing''
''sendPing''
# To force sending a ping right away use:
# To force sending a ping immediately use:
#* <code>adb shell -n ...GleanDebugActivity --es sendPing metrics </code>
#* <code>adb shell -n ...GleanDebugActivity --es sendPing metrics </code>
#* (or instead of metrics other ping names)
#* (or instead of metrics other ping names)
Line 185: Line 185:


''tagPings''
''tagPings''
# To tag a ping with a user label for easy query in Glean dashboard
# To tag a ping with a user label for easy query in [https://debug-ping-preview.firebaseapp.com/ Glean Debug dashboard]
#* <code>adb shell -n ...GleanDebugActivity --es tagPings rpapa-test1</code>, then spot <code>rpapa-test1</code> in the frontend to identify your pings.
#* <code>adb shell -n ...GleanDebugActivity --es tagPings rpapa-test1</code>, then spot <code>rpapa-test1</code> in the frontend to identify your pings.


Confirmed users
487

edits

Navigation menu