«  Firefox 38 Beta 8 | Firefox 38 Beta 9 | Firefox 38 RC  »

Firefox 38 Beta 9 (build 1) Test Plan

• Release Week: April 27th, 2015. The plan is to be shipped on Thursday April 30th 2015 (Release Calendar)
• QA Contact: Robert Kaiser; Florin Mezei
• IRC: irc://irc.mozilla.org#qa ping kairo; FlorinMezei
• Build 1: Firefox 38 Beta 9 | changeset | (ID: 20150429135941)

QE recommendation regarding the quality of the build

Risks with this Beta and ways to mitigate them through testing

Please list any risks related to the quality of this release.

• 1. YouTube (default player)
  • Main focus area especially for Windows and Mac OS, where the intent is to use the HTML5 player (with MSE by default)
  • Testing to make sure that the YouTube default player works without any major issues
  • Will be covered by Sanity testing
• 2. Flash
  • High risk area causing frequent stability problems in recent weeks
  • Testing to make sure that Flash content plays correctly, and without causing major stability problems
  • Will be covered by Sanity testing
• 3. OSX Signing
  • Part of the Beta Regression run
  • Testing to ensure that the build is properly signed on OS X and starts without issues
  • Will be covered by Regression testing
• 4. Hello
  • Part of the Beta Regression run
  • Testing to ensure that the various fixes that entered in Firefox 38 did not break the Hello app
  • Will be covered by Regression testing
• 5. Themes
  • Part of the Beta Regression run
  • Testing to ensure that themes can be installed and apply without issues
  • Will be covered by Regression testing

Features

See the Feature Release Tracking gdoc for a general overview

Results

New bugs

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

New bugs to this Beta

    NONE     

Known Issues

• Major issues

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

• Low impact issues

11 Total; 1 Open (9.09%); 10 Resolved (90.91%); 0 Verified (0%);

Regression Tests

• Tests are run from a Full Regression set, created before Beta 2, to cover areas most affected by fixes in current Beta (Firefox 38)
• Regression tests are run over the interval Beta 2 -> Release
• Tests to run for each Beta are picked to cover areas most affected by fixes since previous Beta (if there are no such areas, tests are picked randomly from the Full Beta Regression set).
• Tests are available in Mozilla Moztrap.
• In case of failure in any regression tests, bugs need to be raised ASAP before proceeding to the exploratory testing.

Regression testing areas (final list to be finalized before Beta 2):

• Executed (in previous beta builds)
  • [FAIL] Play WebGL games
  • [FAIL] Play WebGL animations
  • [FAIL] Show PDF
  • [FAIL] Play different video formats
  • [FAIL] Play various audio formats
  • [FAIL] Desktop Firefox Web Compatibility
  • [FAIL] Breakpad End-to-End Functionality
  • [FAIL] Customize toolbars
  • [FAIL] Desktop Firefox Add-on Compatibility
  • [PASS] Verify update applies with root owned files
  • [FAIL] Search
  • [FAIL] Desktop Firefox Plugin Compatibility
  • [PASS] Mac OSX 32-bit Mode
  • [PASS] Browsing secure sites
  • [PASS] Mac OSX Signing Verification
  • [FAIL] Hello Smoke test
  • [PASS] Install, disable, enable, remove themes and personas

• Remaining (for next beta builds)

    NONE

Exploratory Testing

• 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)

Branch Bug Fix Verifications

• Firefox (38) Bugs

• Verified bugs

6 Total; 0 Open (0%); 1 Resolved (16.67%); 5 Verified (83.33%);

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