Releases/Firefox 43/Test Plan/Beta/RC

From MozillaWiki
Jump to navigation Jump to search

«  Firefox 43 Beta 9 | Firefox 43 RC (build 1) |  »

Firefox 43.0 RC (build 1) Test Plan


QE recommendation regarding the quality of the build

Recommendation based on results from manual testing GOOD FOR RELEASE

Manual Testing summary - Platform Coverage and Areas Tested

  • Testing is performed around areas affected by fixes: Web Compatibility, Search Suggestions, Tab Sound Visual Indicator.
  • Test Cases executed and results: report
Platform Build Architecture Assignee Results: report
Windows 7 x64 (AMD Radeon HD 6450) 32-bit Bogdan Maris [DONE]
Windows 10 x86 (Intel HD Graphics 2500) 32-bit Mihai Boldan [DONE]
Mac OS X 10.9.5 (Intel Iris Pro 1024 MB) 64-bit Camelia Badau [DONE]
Ubuntu 13.04 x86 (AMD Radeon R7 200) 32-bit Paul Silaghi [DONE]
Tested Area Testing Type Results
WEB COMPATIBILITY Regression Testing PASS
SEARCH SUGGESTIONS Regression Testing PASS
TAB SOUND VISUAL INDICATOR Regression Testing PASS

Features

See the Feature Release Tracking gdoc for a general overview


Feature Owner Status Details Test Plan
New Add-on Signing Vasilica Mihasca [DONE] Signed off Test Plan
Unified Autocomplete Petruta Rasa [DONE] Signed off Test Plan
Search Suggestions Petruta Rasa [DONE] Signed off ---
Windows on-screen Keyboard Vasilica Mihasca [DONE] Signed off Test Plan

Results

New bugs

Bugzilla query error

There was a problem during the HTTP request: 429 Unknown Error


Known Issues - also seen in previous builds

Major issues also seen in previous builds

NONE

Low impact issues also seen in previous builds

Bugzilla query error

There was a problem during the HTTP request: 429 Unknown Error


Branch Bug Fix Verifications

Bugzilla query error

There was a problem during the HTTP request: 429 Unknown Error

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