Confirmed users
487
edits
QA/Mobile/TelemetryTestPlan: Difference between revisions
m
type
Rpappalardo (talk | contribs) m (desc) |
Rpappalardo (talk | contribs) m (type) |
||
| Line 55: | Line 55: | ||
# [[#Data Submission|Data Submission]] | # [[#Data Submission|Data Submission]] | ||
#* Using the [https://github.com/mozilla-mobile/android-components/tree/master/components/service/glean#debugging-products-using-glean Glean CLI tool], we'll tag and 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 [https://github.com/mozilla-mobile/android-components/tree/master/components/service/glean#debugging-products-using-glean Glean CLI tool], we'll tag and 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 | # [[#Data Integrity|Data Integrity Verification]] | ||
#* Using the [https://debug-ping-preview.firebaseapp.com/ Glean Debug Dashboard], we must verify that our ping data arrives at the telemetry server without undue latency (within approx. 10-20 seconds). | #* Using the [https://debug-ping-preview.firebaseapp.com/ Glean Debug Dashboard], we must verify that our ping data arrives at the telemetry server 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.'' | ||