«  Firefox 38 Beta 1 | Firefox 38 Beta 2 | Firefox 38 Beta 3  »

Firefox 38 Beta 2 (build 1) Test Plan

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

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
  • YouTube switched back the default player served to Flash for Windows (still Flash on Mac and Linux)
  • Testing to ensure that YouTube Flash playback works without major issues on all Operating Systems
  • Will be covered by Sanity testing on the YouTube default player (Flash)
• 2. Reading List
  • A massive uplift was made in Firefox 38 Beta for the Reading List feature
  • Testing to ensure that the many fixes that landed did not break the feature's basic functionality
  • Will be covered by Sanity testing
• 3. WebGL
  • Part of the Beta Regression run
  • Testing to ensure that the additional Graphics fixes that landed in 38 did not cause regressions
  • Will be covered by Regression testing
• 4. PDF
  • New pdf.js versions landed in Firefox 38 (https://bugzil.la/1126941, https://bugzil.la/1135021)
  • Part of the Beta Regression run
  • Testing to ensure that PDFs work without any major issues
  • Will be covered by Regression testing

Features

See the Feature Release Tracking wiki for a general overview

Results

Bug Summary

• New bugs

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

• New bugs to this Beta

    NONE     

• Known Issues

11 Total; 2 Open (18.18%); 8 Resolved (72.73%); 1 Verified (9.09%);

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

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

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

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

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