Releases/Firefox 60/Test Plan/Beta/4
From MozillaWiki
« Firefox 60 Beta 4 | Firefox 60 Beta 5 »
Firefox 60 Beta 4 Test Plan
Build information
- Release week: Mar 15th, 2018. Plan is to ship this build on Fri, Mar 16th, 2018 — Release Calendar.
- Build: 60.0b4-build1 | 1dfbedb54c39 | 20180315232954 | bugs since previous changeset | 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) |
---|---|---|---|
60.0b4-build1 | COMPLETED (100%) | SHIP IT |
|
Manual testing summary
Note: Test Plan available at https://testrail.stage.mozaws.net/index.php?/plans/view/8798
PLATFORM | ASSIGNEE | BUILD | GPU | STATUS PER TEST SUITE | |||
---|---|---|---|---|---|---|---|
Graphics | |||||||
Windows 7 x32 | David Olah | 32-bit | AMD Radeon HD 5450 | RED | |||
Windows 8.1 x64 | Daniel Aschilean | 64-bit | AMD Radeon 3000 | GREEN | |||
macOS 10.12 | Hani Yacoub | 64-bit | Intel Iris Pro 1536 MB | GREEN | |||
Ubuntu 16.04 x64 | Carmen Fat | 64-bit | Intel® HD Graphics 530 (Skylake GT2) | GREEN |
Features in Firefox 60
Note: See https://docs.google.com/document/u/1/d/1jLrir7BEF7nerypyqbbtdu_uL2IDRLjZqigSOeUMFho/edit for a general overview.
Detailed test results
Note: New and known bugs are listed in https://testrail.stage.mozaws.net/index.php?/plans/defects/8868
New bugs
4 Total; 3 Open (75%); 1 Resolved (25%); 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
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
Bug fix verification
Note: {{{1}}}
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
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