QA/Mobile/TelemetryTestPlan: Difference between revisions

QA/Mobile/TelemetryTestPlan (view source)

Revision as of 23:35, 8 May 2019

533 bytes added , 8 May 2019

test exec

Rpappalardo

Confirmed users

487

edits

@@ Line 125: / Line 125: @@
 ** Enabling debug mode either returns a unique identifier, or the ID you want to use (see tagPings parameter below), enabling immediate query of test pings
-===TEST EXECUTION===
+=== TEST EXECUTION ===
 ==== Setup ====
@@ Line 161: / Line 161: @@
 # Move app to the background (this should immediately trigger send)
-==== Verify Ping Success ====
+==== Data Integrity ====
+Now let's verify that data has arrived to telemetry service intact.
+see: [# Verify JSON data per [https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/docs/pings/pings.md pings doc]
+===== Open Ping =====
 # Open Glean Debug Dashboard: [https://debug-ping-preview.firebaseapp.com]
 # Verify real-time receipt of tagged ping in dashboard
@@ Line 168: / Line 173: @@
 # Verify that "Recent pings..." entry contains correct ping types
 # Drill down to JSON data
-# Verify JSON data per [https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/docs/pings/pings.md glean pings doc]
+===== Verify Common Info =====
+* Verify data in all fields per [https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/docs/pings/pings.md#ping-sections common fields doc]
+* NOTE: if common info is good on baseline ping, SHOULD BE good on others! (All use same path of execution)
+===== Verify Baseline Info =====
+===== Verify Events Info =====
+===== Verify Metrics Info =====
+===== Verify Custom Info =====
 ===EXAMPLES===