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

Firefox 38 Beta 8 (build 1) Test Plan

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

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. Reading List disabling
  • Testing to check that the Reading List feature is disabled as part of the Firefox Spring Campaign plans (bug 1155191)
  • Will be covered by Exploratory testing
• 2. Reader View disabling
  • Testing to check that the Reader View feature is disabled as part of the Firefox Spring Campaign plans (bug 1155191)
  • Will be covered by Exploratory testing
• 3. Suggested Tiles disabling
  • Testing to check that the Suggested Tiles feature is disabled as part of the Firefox Spring Campaign plans (bug 1156921)
  • Will be covered by Exploratory testing
• 4. Plug-ins
  • Part of the Beta Regression run
  • Testing to ensure that the most popular plug-ins work without major issues
  • Will be covered by Regression testing
• 5. Secure Browsing
  • Part of the Beta Regression run
  • Testing to ensure that browsing of secure sites works without major regressions
  • Will be covered by Regression testing
• 6. OS X 32-bit mode
  • Part of the Beta Regression run
  • Testing to ensure that Firefox works without issues when run in 32-bit mode on Mac OS X
  • Will be covered by Regression testing
• 7. Basic Web Compatibility
  • Testing to check that build 2 works without any major breakage
  • Will be covered by Sanity testing

Features

See the Feature Release Tracking gdoc for a general overview

Results

New bugs

    NONE     

New bugs to this Beta

    NONE     

Known Issues

• Major issues

    NONE

• Low impact issues

8 Total; 1 Open (12.5%); 7 Resolved (87.5%); 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

• Remaining (for next beta builds)
  • [PASS/FAIL] Mac OSX Signing Verification
  • [PASS/FAIL] Hello Smoke test
  • [PASS/FAIL] Install, disable, enable, remove themes and personas

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