Releases/Firefox 65/Test Plan/Beta/65.0RC2
From MozillaWiki
< Releases | Firefox 65 | Test Plan
« Firefox 65.0 | Firefox 65.0RC2 »
Firefox 65.0 Test Plan
Build information
- Release week: Jan 28th, 2019. Plan is to ship this build on Tue, Jan 29th, 2019 — Release Calendar.
- Build: 65.0-build2 | 896611703c2b | 20190124174741 | bug list.
- QA contacts: Andrei Vaida (:avaida), Cornel Ionce (:cornel_ionce), Bogdan Maris (:bogdan_maris), — online on #qa and #release-drivers, ⌚️UTC+02:00.
Manual QA's recommendation for this build
Note: Recommendation based on results from manual testing.
| BUILD | TESTING STATUS | RECOMMENDATION | REASON(S) |
|---|---|---|---|
| 65.0-build2 | COMPLETED (100%) | SHIP IT |
|
Manual testing summary
Note: Test Plan available at https://testrail.stage.mozaws.net/index.php?/plans/view/14923
| PLATFORM | ASSIGNEE | BUILD | GPU | STATUS PER TEST SUITE | |||
|---|---|---|---|---|---|---|---|
| Web compatibility | |||||||
| Windows 7 x64 | Maria Berlinger | 32-bit | Intel(R) HD Graphics 5500 | GREEN | |||
| Windows 10 x64 | Daniel Cicas | 64-bit | Intel HD graphics | GREEN | |||
| macOS 10.12 | Catalin Sasca | 64-bit | Intel Iris Pro | GREEN | |||
| Ubuntu 16.04 x86 | Cristian Comorasu | 32-bit | HD Graphics 5500 | GREEN | |||
Features in Firefox 65
See the following gdoc for a general overview.
Detailed test results
Note: New and known bugs are listed in https://testrail.stage.mozaws.net/index.php?/plans/defects/14923
New bugs
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
Known bugs
High-impact bugs also encountered in previous builds
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
Low-impact bugs also encountered in previous builds
| ID | Summary | Status | Resolution |
|---|---|---|---|
| 558178 | Only show password capture dialog if we're reasonably sure the password was correct and the login was successful | RESOLVED | WONTFIX |
1 Total; 0 Open (0%); 1 Resolved (100%); 0 Verified (0%);
Bug fix verification
All verified Firefox 65 bug fixes are listed in the following gdoc
Status tags
- [NOT STARTED] - {{mnotstarted}} - little or no work has started on this task
- [ON TRACK] - {{mok}} - task is actively being worked on and those assigned feel comfortable and confident in the quality of the build.
- [DONE] - {{mdone}} - task is completed and those assigned feel comfortable and confident in the quality of the build.
- [AT RISK] - {{mrisk}}- blocking bug / high number of bugs / other confidence-shakers makes us feel not comfortable with the quality of the build.
- [IN PROGRESS] - {{mprog}} - actively being tested on
- [INVESTIGATION NEEDED] - {{minvest}} - more investigation needed
