Releases/Firefox 67/Test Plan/Beta/17

From MozillaWiki
< Releases‎ | Firefox 67‎ | Test Plan
Revision as of 14:24, 6 May 2019 by Bogdan.maris (talk | contribs) (Created page with "<small> « Firefox 67 Beta 16 | Firefox 67 Beta 17 | Releases/Firefox 67/Test Plan/Be...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

«  Firefox 67 Beta 16 | Firefox 67 Beta 17 | Firefox 67 Beta 18  »

Firefox 67 Beta 17 Test Plan

Build information

Manual QA's recommendation for this build

Note: Recommendation based on results from manual testing.
BUILD TESTING STATUS RECOMMENDATION REASON(S)
67.0b17-build2 COMPLETED (100%) SHIP IT
  • No new issues uncovered.
  • Known issues are low-impact.


Manual testing summary

PLATFORM ASSIGNEE BUILD GPU STATUS PER TEST SUITE
WebExtensions compatibility & support Web compatibility
Windows 7 x64 Catalin Sasca 64-bit AMD Radeon HD 3000 PASS PASS
Windows 10 x64 Cristian Baica 64-bit Intel HD Graphics 530 PASS PASS
macOS 10.13 Oana Botisan 64-bit Intel Iris Plus Graphics 650 PASS PASS
Ubuntu 18.04 x64 Anca Soncutean 64-bit AMD Radeon RS780 PASS PASS

Features in Firefox 67

See the following gdoc for a general overview.

Detailed test results

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