Releases/Firefox 46/Test Plan/Beta/4

From MozillaWiki
Jump to navigation Jump to search

«  Firefox 46 Beta 2 | Firefox 46 Beta 4 | Firefox 46 Beta 5  »

Firefox 46.0 Beta 4 Test Plan

QE recommendation regarding the quality of the build

  • Recommendation based on results from manual testing:
Build 1 GOOD FOR RELEASE


Manual Testing summary - Platform Coverage and Areas Tested

  • Testing performed around: video/audio compatibility and the crash reporter.
  • Test Cases executed and results: report

Build 3

Platform Build architecture Assignee Results: report
Windows Vista x86 (nVIDIA GeForce 620) 32-bit Cornel Ionce [DONE]
Windows 10 x64 (Intel HD Graphics 4600) 32-bit Iulia Cristescu [DONE]
Mac OS X 10.8 (ATI Radeon HD 2400 XT 128 MB) 64-bit Bogdan Maris [DONE]
Ubuntu 14.04 x64 (Intel HD 2500) 64-bit Mihai Boldan [DONE]
Tested Area Testing Type Results
Video compatibility Regression Testing PASS
Audio compatibility Regression Testing PASS
Crash reporter Regression Testing PASS

Features

See the Feature Release Tracking gdoc for a general overview


Feature Owner Status Details Test Plan
APZ Petruta Rasa [ON TRACK] Feature targeted for Firefox 46 - final QA sign-off at the end of Beta 46 Test Plan

Results

New bugs

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 403 [1] => Forbidden ) ) 1


Known Issues - also seen in previous builds

Major issues also seen in previous builds

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 403 [1] => Forbidden ) ) 1


Low impact issues also seen in previous builds

Bugzilla query error

Query options must be valid JSON.1


Branch Bug Fix Verifications

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 403 [1] => Forbidden ) ) 1

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