QA/Mobile/TelemetryTestPlan: Difference between revisions

m
add links
m (summary)
m (add links)
Line 50: Line 50:
=== Description ===
=== Description ===
Testing ping integrity from end-to-end can be broken down into three high-level steps:
Testing ping integrity from end-to-end can be broken down into three high-level steps:
# Data Collection
# [[#Data Collection|Data Collection]]
#* Ping data is collected on the client (and stored locally on disk) when certain specific actions are performed.   
#* Ping data is collected on the client (and stored locally on disk) when certain specific actions are performed.   
#* 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 trigger data collection for each of the ping scenarios by ''performing those actions in the proper sequence.''
#* Generated data will first be verified locally via logcat
#* Generated data will first be verified locally via logcat
# Data Submission
# [[#Data Submission|Data Submission]]
#* 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|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 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.''
Confirmed users
487

edits