Confirmed users
487
edits
QA/Mobile/TelemetryTestPlan: Difference between revisions
m
test strategy
Rpappalardo (talk | contribs) m (test demo) |
Rpappalardo (talk | contribs) m (test strategy) |
||
| Line 24: | Line 24: | ||
= Test Strategy = | = Test Strategy = | ||
== | == Summary == | ||
The Mobile QA team will perform two test types of telemetry verification for all our mobile projects: | The Mobile QA team will perform two test types of telemetry verification for all our mobile projects: | ||
# End-to-end (client-to-server) manual tests | # End-to-end (client-to-server) manual tests | ||
| Line 31: | Line 31: | ||
This wiki outlines a test plan for manual testing. | This wiki outlines a test plan for manual testing. | ||
''Frequency:'' | ''Frequency:'' | ||
* upon request from devs, management | * upon request from devs, management | ||
''Who:'' | ''Who:'' | ||
* SoftVision engineers | * SoftVision engineers | ||
== Ping Scenarios == | == Ping Scenarios == | ||
=== | === Description === | ||
A "ping" refers to a JSON data blob sent from the client to the telemetry service. There are three basic types (scenarios): | A "ping" refers to a JSON data blob sent from the client to the telemetry service. There are three basic types (scenarios): | ||
# [https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/docs/pings/baseline.md baseline ping] | # [https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/docs/pings/baseline.md baseline ping] | ||
| Line 59: | Line 48: | ||
== Ping Activities == | == Ping Activities == | ||
=== | === Description === | ||
Testing ping integrity from end-to-end can be broken down into three high-level steps: | Testing ping integrity from end-to-end can be broken down into three high-level steps: | ||
# Data Collection | # Data Collection | ||