QA/Mobile/TelemetryTestPlan: Difference between revisions

QA/Mobile/TelemetryTestPlan (view source)

616 bytes removed , 10 May 2019

remove

Confirmed users

487

edits

@@ Line 143: / Line 143: @@
 * Pick 4-5 event types and perform those user actions in sequence (NOTE: we will later want to verify that they are recorded on the telemetry server in the correct sequence).
 * Reason (per the [https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/docs/pings/events.md events ping docs]): "The events ping's purpose is to transport all of the event metric information"
-== Data Submission ==
-Once we have performed the above steps to locally collect data for the desired scenario, we will need to force it to be submitted immediately.  By default, data is only submitted at scheduled times or when certain data thresholds are reached.  We don't want to wait!
-Repeat the following steps on every test to force immediate data submission for ALL scenarios:
-# Close and uninstall any previous instances of app-under-test
-# Re-install a fresh instance of app on device
-# Launch app with Glean CLI command (not manually)
-# Move app to the background (this should immediately trigger send)
 == Data Integrity ==