Confirmed users
487
edits
QA/Mobile/TelemetryTestPlan: Difference between revisions
testing frequence
Rpappalardo (talk | contribs) (fix error) |
Rpappalardo (talk | contribs) (testing frequence) |
||
| Line 19: | Line 19: | ||
* TBD - pending Glean implementation | * TBD - pending Glean implementation | ||
== Testing Frequency == | |||
==== Ad-Hoc Testing ==== | |||
'''First Pass''' | |||
As telemetry is now being tested for the first time on mobile, we'll do a more thorough "first pass" to verify all data points one time for each ping scenario. | |||
This will be a one-time full verification (which will only be repeated on request) | |||
Currently: baseline, metrics, events | |||
TBD: activation, later, sync | |||
'''New Ping Types''' | |||
End-to-end verification of all data points will only be performed for new ping data in new scenarios. | |||
'''Per Management / dev request''' | |||
Upon request from management, fenix or telemetry dev engineers. | |||
==== Scheduled Testing ==== | |||
'''Sprint''' | |||
Spot checking = verify each ping scenario is transmitting data | |||
NOTE: not verifying every single data point, just eye-balling that data is being transmitted and arrives at telemetry service. | |||
''' Releases ''' | |||
Spot checking = verify each ping scenario is transmitting data | |||
NOTE: not verifying every single point, just eye-balling that data is being transmitted and arrives at telemetry service. | |||
= Test Strategy = | = Test Strategy = | ||