Closed
Bug 1559474
Opened 5 years ago
Closed 5 years ago
Describe manual test scenario for pre-release telemetry for late beta builds
Categories
(Toolkit :: Telemetry, task, P1)
Toolkit
Telemetry
Tracking
()
RESOLVED
FIXED
People
(Reporter: raphael, Assigned: raphael)
References
(Blocks 1 open bug)
Details
Describe the steps for manual QA for verifying that a late beta/release candidate build of Firefox sends pre-release telemetry.
A late beta/release candidate build has the build-time update channel set to "release" and the run-time update channel to "beta".
Assignee | ||
Comment 1•5 years ago
|
||
Prerequisites:
- Firefox Desktop RC build
- Firefox RC profile
Test scenario:
- Start Firefox RC build withe the RC profile
- Navigate to
about:telemetry
- The page is expected to contain the following text
Telemetry is collecting pre-release data and upload is enabled.
Assignee | ||
Comment 2•5 years ago
|
||
Hi Krupa, can you please ask the QA team to add the above test to their RC test plan?
Flags: needinfo?(kraj)
Comment 3•5 years ago
|
||
Added test case in new suite.
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Flags: needinfo?(kraj) → in-testsuite+
Resolution: --- → FIXED
Comment 4•5 years ago
|
||
After a discussion with Raphael on Slack, we've updated the TC scenario:
- Start Firefox RC build withe the RC profile;
- Swap the app.update.channel to "beta" after starting the RC build and performing a browser restart so the string gets updated;
- Perform a browser update;
- Navigate to about:telemetry;
- The page is expected to contain the following text: "Telemetry is collecting pre-release data and upload is enabled."
*For good measure we're checking the string is updated even after the browser update.
You need to log in
before you can comment on or make changes to this bug.
Description
•