Confirmed users
487
edits
QA/Mobile/TelemetryTestPlan: Difference between revisions
m
add link
Rpappalardo (talk | contribs) m (word smithing) |
Rpappalardo (talk | contribs) m (add link) |
||
| Line 57: | Line 57: | ||
#* Using the Glean CLI tool, we'll ''force data to be submitted to the telemetry server immediately,'' rather than waiting for a scheduled trigger event(s) or for thresholds to be met, etc. | #* Using the Glean CLI tool, we'll ''force data to be submitted to the telemetry server immediately,'' rather than waiting for a scheduled trigger event(s) or for thresholds to be met, etc. | ||
# [[#Data Integrity|Data Integrity Verication]] | # [[#Data Integrity|Data Integrity Verication]] | ||
#* Using the [https://debug-ping-preview.firebaseapp.com/ Glean Debug Dashboard], we must verify that the ping data we've tagged and forced to be submitted (using the Glean CLI tool), arrives without undue latency (within approx. 10-20 seconds). | #* Using the [https://debug-ping-preview.firebaseapp.com/ Glean Debug Dashboard], we must verify that the ping data we've tagged and forced to be submitted (using the [https://github.com/mozilla-mobile/android-components/tree/master/components/service/glean#debugging-products-using-glean Glean CLI tool]), arrives without undue latency (within approx. 10-20 seconds). | ||
#* Drill down on the JSON data and ''verify the correct data has been submitted.'' | #* Drill down on the JSON data and ''verify the correct data has been submitted.'' | ||