Releases/Firefox 3.5.1/Test Plan: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(5 intermediate revisions by 2 users not shown)
Line 24: Line 24:
* Smoketests: 3 people (abillings, aakashd, hskupin)
* Smoketests: 3 people (abillings, aakashd, hskupin)
* BFTs: 3 people (abillings, tracy, tester3)
* BFTs: 3 people (abillings, tracy, tester3)
* l10n checks: 3 people (abillings, tchung, tester3)
* l10n checks: 3 people (abillings, tchung, tchung)
* Updates checks: 3 people (abillings, tchung, aakashd)
* Updates checks: 3 people (abillings, tester, aakashd)


== Builds ==
== Builds ==
Line 33: Line 33:


== Test Results ==
== Test Results ==
* Verifications: ''in progress''
* Verifications: '''nearly all completed'''
* [[Releases/Firefox 3.5.1/Test Plan:Smoketests | Smoketests and BFTs]]: '''result'''
* [[Releases/Firefox 3.5.1/Test Plan:Smoketests | Smoketests and BFTs]]: '''PASS'''
* [[Releases/Firefox 3.5.1/Test Plan:l10n | l10n Spot Checks]]: '''result'''
* [[Releases/Firefox 3.5.1/Test Plan:l10n | l10n Spot Checks]]: '''PASS'''
* [[Releases/Firefox 3.5.1/Test Plan:Software Update | Updates]]: '''result'''
* [[Releases/Firefox 3.5.1/Test Plan:Software Update | Updates]]: '''Pass(beta)'''


== Bugs to Verify ==
== Bugs to Verify ==
Line 43: Line 43:
* [http://bit.ly/19Mt1O '''Ride-along bugs''']
* [http://bit.ly/19Mt1O '''Ride-along bugs''']


'''Important:''' Please read Sam Sidler's post in the dev-planning newsgroup to see how we have changed the way use flags for branch management. To quote from it which is relevant to us:
'''Important:''' Once verified, edit the bug's keyword from ''fixed1.9.1.1'' to ''verified1.9.1.1''
 
''Verifications will be handled using the "verified1.9.1" keyword, in conjunction with the ".n-fixed" status.''

Latest revision as of 01:16, 17 July 2009

Firefox 3.5.1 Test Plan

Description of Release

This is a chemspill release which will address a critical bug found in Firefox 3.5. We are taking a few ride-along fixes as well.

Specific Plan for 3.5.1

We need to verify bug fixes, especially the fix for the bug that prompted this release bug 503286. In addition we will go through the usual checks for our maintenance releases: smoketests, basic functional tests, l10n spot checks, and updates checks.

Schedule

Given the chemspill nature of this release, we will have an accelerated schedule. As of Tue (7/14pm PDT) we have not declared code completeness, but we expect to have builds by tomorrow morning PDT. This is a tentative QA schedule:

  • Code Freeze: 7/14
  • QA Starts Verifications: 7/14
  • Builds Start: 7/14
  • QA Cycle: 7/14 - 7/18
    • Smoketests: 7/14-7/15 - 3 people
    • BFTs: 7/15 - 3 people
    • l10n: 7/15 - 3 people
    • Updates checks betatest: 7/16 - 3 people
    • Updates Beta(?): 7/16-7/17 - 3 people

Resources

  • Verifications: Everyone who can help (abillings, hskupin, aakashd, tchung)
  • Smoketests: 3 people (abillings, aakashd, hskupin)
  • BFTs: 3 people (abillings, tracy, tester3)
  • l10n checks: 3 people (abillings, tchung, tchung)
  • Updates checks: 3 people (abillings, tester, aakashd)

Builds

We'll have links to the build location as they become available.

ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/

Test Results

Bugs to Verify

Important: Once verified, edit the bug's keyword from fixed1.9.1.1 to verified1.9.1.1

Retrieved from "https://wiki.allizom.org/index.php?title=Releases/Firefox_3.5.1/Test_Plan&oldid=155861"