Releases/Firefox 40/Test Plan/Beta/4

«  Firefox 40 Beta 3 | Firefox 40 Beta 4 | Firefox 40 Beta 5  »

Firefox 40 Beta 4 (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 most affected by fixes since the previous Beta (in cases when there are no Regression tests to cover these areas, or those tests have already been run as part of the Full Beta Regression set)
  • Test Cases executed and results: report

PLATFORM MATRIX

Platform Assignee Results: report
Windows 7 x86 (Intel HD Graphics 2500) Camelia Badau [DONE]
Windows 10 x64 (nVIDIA GeForce 620) Cornel Ionce [DONE]
Mac OS X 10.9.5 (Intel Iris Pro 1024 MB) Petruta Rasa [DONE]
Ubuntu 14.04 x64 (AMD Radeon HD 5450) Catalin Varga [DONE]

AREAS TESTED

Tested Area Testing Type Results
MIGRATORS Regression Testing PASS

Features

See the Feature Release Tracking gdoc for a general overview


Feature Owner Status Details Test Plan
Async plugin init Catalin Varga [ON TRACK] Feature is in Beta 40, but still disabled by default - potential final QA sign-off at the end of Beta 40 -
First Run for 40 release Catalin Varga [NOT STARTED] New feature targeted for Firefox 40 (not yet implemented) - final QA sign-off at the end of Beta 40 -
Suggested tiles: Sponsored Cornel Ionce [ON TRACK] Feature dropped from Firefox 39 - final QA sign-off at the end of Beta 40 Test Plan
New Add-on Signing Vasilica Mihasca DROPPED FROM 40 Feature dropped from Firefox 39 & 40 (not enough add-ons signed) -
Unified telemetry/FHR Stuart Philp [DONE] Testing performed is tracked in bug 1169037 -
OMTC by default on Linux Alexandra Lucinet [ON TRACK] New feature targeted for Firefox 40 - final QA sign-off at the end of Beta 40 -
Hello - Context Bogdan Maris [AT RISK] New feature targeted for Firefox 40 - final QA sign-off at the end of Beta 40 -

Results

New bugs

    NONE     

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

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 403 [1] => Forbidden ) ) 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