Releases/Firefox 66/Test Plan/Beta/13: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "= Firefox 66 Beta 13 Test Plan = == Build information == * Release week: March 5th, 2019. Plan is to ship this build on Tue, Mar 5th, 2019 — [https://www.google.com/calendar...")
 
No edit summary
Line 66: Line 66:


= Detailed test results =
= Detailed test results =
{{note| New and known bugs are listed in https://testrail.stage.mozaws.net/index.php?/plans/defects/15810}}
{{note| New and known bugs are listed in defects_list}}


== New bugs ==  
== New bugs ==  

Revision as of 13:38, 5 March 2019

Firefox 66 Beta 13 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)
66.0b13-build1 IN PROGRESS 71% -
  • No new issues were found apart from a few already known issues.

Manual testing summary

PLATFORM ASSIGNEE BUILD GPU STATUS PER TEST SUITE
Search Default & custom theme support
Windows 7 x64 Maria Berlinger 64-bit Intel(R) HD Graphics 5500 GREEN GREEN
Windows 10 x64 Anca Soncutean 64-bit ATI Radeon 3000 GREEN GREEN
macOS 10.14 Mihai Boldan 64-bit Intel Iris Pro 1536 GREEN GREEN
Ubuntu 18.04 x64 Daniel Cicas 64-bit NVA8 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 defects_list

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

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

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


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