Confirmed users
487
edits
QA/Mobile/TelemetryTestPlan: Difference between revisions
clarify submit data
Rpappalardo (talk | contribs) (remove) |
Rpappalardo (talk | contribs) (clarify submit data) |
||
| Line 100: | Line 100: | ||
<code> $ ping https://debug-ping-preview.firebaseapp.com</code> | <code> $ ping https://debug-ping-preview.firebaseapp.com</code> | ||
== Data Collection == | == Data Collection & Submission == | ||
=== Summary === | === Summary === | ||
Next, we will need to do | Next, we will need to do 3 things: | ||
# Tag our telemetry pings with a custom identifier | # Tag our telemetry pings with a custom identifier | ||
# Trigger ping collection (generation) on the client. Since this is done differently for each of the ping scenarios, we'll list the steps separately below | # Trigger ping collection (generation) on the client. Since this is done differently for each of the ping scenarios, we'll list the steps separately below | ||
# Submit data to telemetry server | |||
#* 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! | |||
=== Baseline Ping === | === Baseline Ping === | ||
| Line 117: | Line 120: | ||
* ''No specific user actions are required.'' | * ''No specific user actions are required.'' | ||
* Reason (per the [https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/docs/pings/baseline.md baseling ping docs]): "This ping is intended to provide metrics that are managed by the library itself, and not explicitly set by the application" | * Reason (per the [https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/docs/pings/baseline.md baseling ping docs]): "This ping is intended to provide metrics that are managed by the library itself, and not explicitly set by the application" | ||
'''Submit data''' | |||
* Move app to the background (this should immediately trigger send) | |||
=== Metrics Ping === | === Metrics Ping === | ||
| Line 127: | Line 134: | ||
* ''No specific user actions are required.'' | * ''No specific user actions are required.'' | ||
* Reason (per the [https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/docs/pings/metrics.md metrics ping docs]): "The metrics ping is intended for all of the metrics that are explicitly set by the application or are included in the application's metrics.yaml file (except events)" | * Reason (per the [https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/docs/pings/metrics.md metrics ping docs]): "The metrics ping is intended for all of the metrics that are explicitly set by the application or are included in the application's metrics.yaml file (except events)" | ||
'''Submit data''' | |||
* Move app to the background (this should immediately trigger send) | |||
'''NOTE''' | '''NOTE''' | ||
| Line 143: | Line 155: | ||
* 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). | * 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" | * 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" | ||
'''Submit data''' | |||
* Move app to the background (this should immediately trigger send) | |||
== Data Integrity == | == Data Integrity == | ||