Releases/Firefox 67/Test Plan/Beta/18
From MozillaWiki
< Releases | Firefox 67 | Test Plan
« Firefox 67 Beta 17 | Firefox 67 Beta 18 | Firefox 67 Release Candidate »
Firefox 67 Beta 18 Test Plan
Build information
- Release week: May 5th, 2019. Plan is to ship this build on Tue, May 7th, 2019 — Release Calendar.
- Build: 67.0b18-build1 | fe6ddfaa325f | 20190506235559 | 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) |
---|---|---|---|
67.0b18-build1 | COMPLETED (100%) | SHIP IT |
|
Manual testing summary
Note: Test Plan available at https://testrail.stage.mozaws.net/index.php?/plans/view/17342
PLATFORM | ASSIGNEE | BUILD | GPU | STATUS PER TEST SUITE | |||
---|---|---|---|---|---|---|---|
Web compatibility | |||||||
Windows 7 x64 | Alexandru Trif | 32-bit | AMD 760G | PASS | |||
Windows 10 x64 | Timea Zsoldos | 64-bit | Intel HD Graphics | PASS | |||
macOS 10.14 | Maria Berlinger | 64-bit | Intel Iris Plus Graphics 650 | PASS | |||
Ubuntu 18.04 x64 | Catalin Sasca | 64-bit | Ati HD 3000 | PASS |
Features in Firefox 67
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/17342
New bugs
Bugzilla query error
error, http-bad-status, Array
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
17 Total; 9 Open (52.94%); 7 Resolved (41.18%); 1 Verified (5.88%);
Bug fix verification
All verified Firefox 67 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