Releases/Firefox 67/Test Plan/Beta/6
< Releases | Firefox 67 | Test Plan
Jump to navigation
Jump to search
« Firefox 67 Beta 5 | Firefox 67 Beta 6 | Firefox 67 Beta 7 »
Firefox 67 Beta 6 Test Plan
Build information
- Release week: Mar 25th, 2019. Plan is to ship this build on Fri 29th, 2019 — Release Calendar.
- Build: 67.0b6-build1 | 0b745b93a430983cdcd6c748e6e2098d012e1969 | 20190328152334 | 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.0b5-build1 | NOT STARTED (0%) | TBD | TBD |
Manual testing summary
Note: Test Plan available at https://testrail.stage.mozaws.net/index.php?/plans/view/16493
| PLATFORM | ASSIGNEE | BUILD | GPU | STATUS PER TEST SUITE | |||
|---|---|---|---|---|---|---|---|
| Area 1 | Area 2 | ||||||
| Windows 7 x64 | Cornel Ionce | 64-bit | GPU | TBD | TBD | ||
| Windows 10 x64 | Vlad Lucaci | 64-bit | GPU | TBD | TBD | ||
| Mac 10.11 | Gabi Cheta (Asofie) | 64-bit | GPU | TBD | TBD | ||
| Ubuntu x64 | Mihai Boldan | 64-bit | GPU | TBD | TBD | ||
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/16395
New bugs
Bugzilla query error
Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 400 [1] => Bad Request ) ) 1
Known bugs
High-impact bugs also encountered in previous builds
Bugzilla query error
Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 400 [1] => Bad Request ) ) 1
Low-impact bugs also encountered in previous builds
Bugzilla query error
Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 400 [1] => Bad Request ) ) 1
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