Releases/Firefox 3.6.4/Test Plan

From MozillaWiki
Jump to: navigation, search

Firefox 3.6.4 Test Plan

Description of Release

This is a security and stability release of Firefox that also contains the Out of Process Plugins (OOPP) work.

Specific Plan for 3.6.4

We will verify security and critical bugs for this release. We will also verify the bugs for OOPP and the recently-added plugin tests for OOPP in Litmus. OOPP will only support Flash, Silverlight, and Quicktime. Smoketests and BFTs will also be run. Because of the OOPP work affecting multiple platforms, we will be runnning BFTs on more than one platform to include the ones where OOPP is available.

Schedule

  • Tree opens: 4/1
  • Code freeze: 4/12, 11:59pm
  • Official builds start: 4/13
  • QA with build 1 starts: 4/14
    • Smoketests - 4 people - 4/14
    • Focusing OOPP testing - 4/14 - 4/15
    • BFTs - 4 people - 4/14 - 4/16
    • Betatest & Beta Channel Testing for MU - 4 people - 4/16
  • Beta offered as advertised major update in beta channel - 4/16
  • l10n testing: 4 people - 4/17
  • Build 3 builds start: 5/3
  • QA with build 3 starts: 5/3
    • Smoketests - 3 people - 5/3
    • Betatest & Beta Channel Testing for MU - 4 people - 5/4
  • Beta offered to build 1 users in beta channel - 5/4
    • Focusing OOPP testing - 2 people - 4/30 - 5/4
    • BFTs - 2 people - 5/4
  • QA with build 4 starts: 5/12
    • Smoketests - 2 people - 5/12
    • Focusing OOPP testing - 2 people - 5/12 - 5/13
    • Betatest & Beta Channel Testing - 1 person - 5/12
  • Beta offered to build 3 users in beta channel - 5/14
  • Firefox 3.6.4 build 4 offered as normal beta - 5/18
  • Firefox 3.6.4 build 5 created - 5/24
    • Smoketests - 1 person - 5/24 - 5/25
    • Betatest & Beta Channel Testing - 1 person - 5/26
  • Firefox 3.6.4 build 5 offered as normal beta - 5/26
  • Firefox 3.6.4 build 6 created - 5/27
    • Smoketests - 1 person - 5/27
    • Betatest & Beta Channel Testing - 1 person - 5/28
  • Firefox 3.6.4 build 5 offered as normal beta - 5/28
  • Firefox 3.6.4 build 7 created - 6/13
    • Smoketests - 1 person - 6/14
    • Betatest & Beta Channel Testing - 1 person - 6/14
  • Firefox 3.6.4 build 7 offered as normal beta - 6/14
    • Releasetest & Release Channel Testing - 1 person - 6/17
  • Firefox 3.6.4 shipped - 6/17

Resources

  • Smoketests: 4 people
    • abillings
    • juanb
    • marcia
    • aravind
  • BFTs: 4 people
    • abillings
    • juanb
    • marcia
    • aravind
  • Updates checks: 4 people
    • abillings
    • juanb
    • marcia
    • aravind

Builds

Test Results

Bugs to Verify

Important:

  1. Focus on critical and security bugs first.
  2. Mark bug as verified adding the keyword verified1.9.2

Beta 1 (Build 1) feedback from Hendrix, etc

Hendrix

  • Overall, not much feedback in the pre-release Hendrix group. Found some feedback in the main Firefox group as well
  • One Windows user reported that a pave over install failed for him (paved over 3.6.3)
  • Report that Firefox 3.6.4 Silverlight plugins is very slow.
    • Some sites such as the Silverlight Showcase exhibit this issue but that particular site is a known issue according to bsmedberg. Reporter identified http://www.onsen.ag/ as the site. More investigation needed.
  • Report that Acrobat Plugin Output disappears on 3.6.4 Beta using Win XP
    • One Reporter using the latest Adobe release which just came out. Investigating but have not yet been able to reproduce.
    • Another reporter reports the same issue but has many extensions installed in his profile so this issue could be extension related.
    • https://bugzilla.mozilla.org/show_bug.cgi?id=559494 is one file and seems similar
  • Report of Plugin container does not respond error message
    • JAVA 6.0.160.1 was not removed / replaced upon installation of JAVA

6.0.200.2 and later popped-up a window advising it was being disabled due to instability.... and keeps popping-up repeatedly even though it is already disabled.... There is no right-click option to Remove or Delete it either.

Twitter

  • Feedback was primarily related to the announcment of the feature. I did not see much feedback regarding comments, etc