Confirmed users
487
edits
QA/Mobile/TelemetryTestPlan: Difference between revisions
Jump to navigation
Jump to search
m
events ping
Rpappalardo (talk | contribs) (metrics ping) |
Rpappalardo (talk | contribs) m (events ping) |
||
| Line 121: | Line 121: | ||
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)" | ||
=== | === Events Ping === | ||
As of the writing of this test plan, there are currently 37 events defined in the fenix [https://github.com/mozilla-mobile/fenix/blob/master/app/metrics.yaml metrics.yaml] (Look for "type: event"). | As of the writing of this test plan, there are currently 37 events defined in the fenix [https://github.com/mozilla-mobile/fenix/blob/master/app/metrics.yaml metrics.yaml] (Look for "type: event"). | ||
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" | |||
== Data Submission == | == Data Submission == | ||