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

Firefox 38 Beta 3 (build 1) Test Plan

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

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 (HTML5 player)
  • YouTube switched back to the HTML5 player by default for Windows
  • There were a series of Video/Audio fixes landing in this build that may impact YouTube HTML5 playback
  • Testing to ensure that YouTube HTML5 playback works without major issues on all Operating Systems
  • Will be covered by Sanity testing
• 2. WebGL
  • Several Graphics fixes landed in this build
  • Testing to ensure that these fixes did not cause regressions
  • Will be covered by Sanity testing (WebGL games, animations, maps)
• 3. Hello
  • Several fixes landed in this build for WebRTC and Loop
  • Testing to ensure that basic functionality for Hello was not broken
  • Will be covered by Basic Sanity testing (checking ability to make a call)
• 4. Audio playback
  • Part of the Beta Regression run
  • Testing to ensure that the multiple Video/Audio fixes did not cause regressions
  • Will be covered by Regression testing
• 5. Video playback
  • Part of the Beta Regression run
  • Testing to ensure that the multiple Video/Audio fixes did not cause regressions
  • Will be covered by Regression testing

Features

See the Feature Release Tracking wiki for a general overview

Results

Bug Summary

• New bugs

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

• New bugs to this Beta

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

• Known Issues

9 Total; 0 Open (0%); 8 Resolved (88.89%); 1 Verified (11.11%);

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
  • [FAIL] Play different video formats
  • [FAIL] Play various audio formats

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

4 Total; 0 Open (0%); 0 Resolved (0%); 4 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