QA/Mobile/TelemetryTestPlan: Difference between revisions

QA/Mobile/TelemetryTestPlan (view source)

410 bytes added , 8 May 2019

m

pings

Confirmed users

487

edits

@@ Line 64: / Line 64: @@
 == Ping Activities ==
 === Summary ===
-To test ping integrity from end-to-end, we'll be doing 3 things:
+To test ping integrity from end-to-end, we need to do the following:
-# Trigger Data Collection
+# Data Collection
-#* Ping data is generated on the client when certain actions are performed.  Our test coverage will ensure we generate data for each of the ping scenarios.
+#* Ping data is collected on the client (and stored locally) when certain specific actions are performed.  Our test coverage will 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
-# Trigger Data Submission
+# Data Submission
-#* Using Glean CLI tool, we will force data to be sent immediately, rather than waiting for a scheduled trigger event(s) or for thresholds to be met
+#* Using Glean CLI tool, we will 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.
 # Verify Submitted Data
+#* Using the [https://debug-ping-preview.firebaseapp.com/ Glean Debug Dashboard], we'll verify that the ping data we've tagged (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.
 == Ping Scenarios ==