QA/Mobile/TelemetryTestPlan: Difference between revisions

m
summary
(data collection)
m (summary)
Line 52: Line 52:
# [[#Data Collection|Data Collection]]
# [[#Data Collection|Data Collection]]
#* Ping data is collected on the client (and stored locally on disk).  Some data is recorded automatically (i.e. [https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/docs/pings/baseline.md baseline] and [https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/docs/pings/metrics.md metrics] pings). Other data is collected when certain specific actions are performed by the user.  These are referred to as "events" (i.e. [https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/docs/pings/events.md events] pings).
#* Ping data is collected on the client (and stored locally on disk).  Some data is recorded automatically (i.e. [https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/docs/pings/baseline.md baseline] and [https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/docs/pings/metrics.md metrics] pings). Other data is collected when certain specific actions are performed by the user.  These are referred to as "events" (i.e. [https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/docs/pings/events.md events] pings).
#* Our test coverage must ensure we trigger data collection for each of the ping scenarios by ''performing those actions in the proper sequence.''
#* Our test coverage must ensure we verify that [[#Data Collection|data collection]] and [[#Data Submission|submission]] has taken place locally for each of the ping scenarios. We can monitor this activity with logcat.
#* Generated data will first be verified locally via logcat
# [[#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 ''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 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 [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).
#* 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.''


Confirmed users
487

edits