Confirmed users
487
edits
QA/Mobile/TelemetryTestPlan: Difference between revisions
Jump to navigation
Jump to search
data collection
Rpappalardo (talk | contribs) m (add link) |
Rpappalardo (talk | contribs) (data collection) |
||
| Line 51: | Line 51: | ||
For each ping scenario, testing ping integrity from end-to-end can be broken down into three high-level steps: | For each ping scenario, testing ping integrity from end-to-end can be broken down into three high-level steps: | ||
# [[#Data Collection|Data Collection]] | # [[#Data Collection|Data Collection]] | ||
#* Ping data is collected on the client (and stored locally on disk) when certain specific actions are performed. | #* Ping data is collected on the client (and stored locally on disk). Some data is recorded automatically (i.e. [https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/docs/pings/baseline.md baseline] and [https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/docs/pings/metrics.md metrics] pings). Other data is collected when certain specific actions are performed by the user. These are referred to as "events" (i.e. [https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/docs/pings/events.md events] pings). | ||
#* Our test coverage must ensure we trigger data collection for each of the ping scenarios by ''performing those actions in the proper sequence.'' | #* Our test coverage must 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 | #* Generated data will first be verified locally via logcat | ||