Releases/Firefox 66/Test Plan/Beta/12
From MozillaWiki
< Releases | Firefox 66 | Test Plan
« Firefox 66 Beta 11 | Firefox 66 Beta 12 | Firefox 66 Beta 13 »
Firefox 66 Beta 12 Test Plan
Build information
- Release week: Feb 28th, 2019. Plan is to ship this build on Fri, Mar 1st, 2019 — Release Calendar.
- Build: 66.0b12-build1 | 67710331eb1f | 20190228180200 | 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) |
---|---|---|---|
66.0b12-build1 | COMPLETED 100% | SHIP IT |
|
Manual testing summary
Note: Test Plan available at https://testrail.stage.mozaws.net/index.php?/plans/view/15647
PLATFORM | ASSIGNEE | BUILD | GPU | STATUS PER TEST SUITE | |||
---|---|---|---|---|---|---|---|
Graphics compatibility & support | WebExtensions compatibility & support | Anti-Tracking | |||||
Windows 8.1 x64 | Catalin Sasca | 64-bit | Intel HD 4000 | GREEN | GREEN | GREEN | |
Windows 10 x86 | Gabi Cheta | 86-bit | Intel(R) HD Graphics | GREEN | GREEN | GREEN | |
macOS 10.10 | Vlad Lucaci | 64-bit | Intel Iris Pro 1536 | GREEN | GREEN | GREEN | |
Ubuntu 16.04 x86 | Cornel Ionce | 86-bit | Intel® HD Graphics 5500 | GREEN | GREEN | GREEN |
Features in Firefox 66
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/15810
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
7 Total; 3 Open (42.86%); 3 Resolved (42.86%); 1 Verified (14.29%);
Bug fix verification
All verified Firefox 66 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