QA/Mobile/TelemetryTestPlan: Difference between revisions

Jump to navigation Jump to search
m
summary
m (test execution)
m (summary)
Line 63: Line 63:
== Summary ==
== Summary ==


This section describes how to perform an end-to-end (client-to-server) test using the production telemetry service across the real network.   
This section describes how to perform an end-to-end (client-to-server) test using the production telemetry service across the real network.  Please note, for these tests we will not be a using the telemetry staging server nor a mock server on localhost to receive telemetry pings.  Test execution will require installation of an application APK on a physical mobile device and use of a built-in CLI tool called Glean.


NOTE: for these tests, we will not be a using the telemetry staging server nor a mock server on localhost to receive telemetry pings.


Test execution will require installation of an application APK and the use of a built-in CLI tool called Glean.
First, we will trigger telemetry data collection locally by emulating a specific set of user actions in the application. Next, we will force immediate data submission to the telemetry server.  Lastly, we will use the [https://debug-ping-preview.firebaseapp.com/ Glean Debug Dashboard] to verify data integrity.


First, we will locally trigger telemetry data collection by emulating a specific set of user activities in the application.


Next, we will force immediate data submission to the telemetry server.
To summarize, we will be doing the following:
 
Lastly, we will use the [https://debug-ping-preview.firebaseapp.com/ Glean Debug Dashboard] to verify data integrity.


To summarize, we will be doing the following:
# [[#Test Setup|Test Setup]]
# [[#Test Setup|Test Setup]]
# [[#Data Collection|Data Collection]]
# [[#Data Collection|Data Collection]]
# [[#Data Submission|Data Submission]]
# [[#Data Submission|Data Submission]]
## [[#Data Integrity|Data Integrity]] (verification)
# [[#Data Integrity|Data Integrity Verification]]  
 


'''NOTES on [https://debug-ping-preview.firebaseapp.com Dashboard Glean Dashboard]'''
'''NOTES on [https://debug-ping-preview.firebaseapp.com Dashboard Glean Dashboard]'''
* Authentication requires SSO login
* Authentication requires SSO login
* see: [https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/README.md#debugging-products-using-glean Debugging products using Glean]
* see: [https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/README.md#debugging-products-using-glean Debugging products using Glean]
* Features
** Glean Debug Dashboard makes data received by the pipeline from some devices visible in real-time
** Enabling debug mode either returns a unique identifier, or the ID you want to use (see tagPings parameter below), enabling immediate query of test pings


== Test Setup ==
== Test Setup ==
Confirmed users
487

edits

Navigation menu