QA/Mobile/TelemetryTestPlan: Difference between revisions

QA/Mobile/TelemetryTestPlan (view source)

Revision as of 17:30, 22 May 2019

1,144 bytes removed , 22 May 2019

reference testrail

Rpappalardo

Confirmed users

487

edits

@@ Line 150: / Line 150: @@
 '''Launch Glean'''
+See test steps in [https://testrail.stage.mozaws.net/index.php?/suites/view/4669&group_by=cases:section_id&group_order=asc TestRail - Fenix - telemetry]
-*<code>adb shell am start -n org.mozilla.fenix/mozilla.components.service.glean.debug.GleanDebugActivity --ez logPings true --es sendPing baseline --es tagPings rpapa-test-00</code>
-'''Start data collection'''
-* ''No specific user actions are required.''
-* Reason (per the [https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/docs/pings/baseline.md baseling ping docs]): "This ping is intended to provide metrics that are managed by the library itself, and not explicitly set by the application"
-'''Submit data'''
-* Move app to the background (this should immediately trigger send)
 ===  Metrics Ping ===
-'''Launch Glean'''
+See test steps in [https://testrail.stage.mozaws.net/index.php?/suites/view/4669&group_by=cases:section_id&group_order=asc TestRail - Fenix - telemetry]
-*<code>adb shell am start -n org.mozilla.fenix/mozilla.components.service.glean.debug.GleanDebugActivity --ez logPings true --es sendPing metrics --es tagPings rpapa-test-01</code>
-'''Start data collection'''
-* ''No specific user actions are required.''
-* 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)"
-'''Submit data'''
-* Move app to the background (this should immediately trigger send)
 '''NOTE'''
@@ Line 181: / Line 160: @@
 === 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/events.yaml events.yaml]  (Look for "type: event").
+See test steps in [https://testrail.stage.mozaws.net/index.php?/suites/view/4669&group_by=cases:section_id&group_order=asc TestRail - Fenix - telemetry]
-'''Launch Glean'''
+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/events.yaml events.yaml]  (Look for "type: event").
-*<code>adb shell am start -n org.mozilla.fenix/mozilla.components.service.glean.debug.GleanDebugActivity --ez logPings true --es sendPing events --es tagPings rpapa-test-02</code>
+''' data collection'''
-'''Start data collection'''
 * 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"
-'''Submit data'''
-* Move app to the background (this should immediately trigger send)
 == Data Integrity ==