Releases/Firefox 3.5.2/Test Plan: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 21: Line 21:


'''Resources'''
'''Resources'''
* Verifications: Everyone who can help (tester1, tester2, ...)
* Verifications: Everyone who can help (ashughes, tester2, ...)
* Smoketests: 3 people (tester1, tester2, ...)
* Smoketests: 3 people (ashughes, tester2, ...)
* BFTs: 3 people (tester1, tester2, ...)
* BFTs: 3 people (ashughes, tester2, ...)
* l10n checks: 3 people (tester1, tester2, ...)
* l10n checks: 3 people (tester1, tester2, ...)
* Updates checks: 3 people (tester1, tester2, ...)
* Updates checks: 3 people (ashughes, tester2, ...)


== Builds ==
== Builds ==

Revision as of 22:33, 29 July 2009

Firefox 3.5.2 Test Plan

Description of Release

This will likely be a chem-spill release which will address critical bugs in Firefox, to be disclosed at Black Hat.

Specific Plan for 3.5.2

We need to verify bug fixes. 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. TBD

  • Code Freeze: Week of 7/27
  • QA Starts Verifications: Week of 7/27
  • Builds Start: Week of 7/27
  • QA Cycle: Week of 7/27
    • Smoketests: Half day - 3 people
    • BFTs: One full day - 3 people
    • l10n: Half day - 3 people
    • Updates checks betatest: Half day - 3 people
    • Updates Beta(?): Week of 7/27, half day - 3 people

Resources

  • Verifications: Everyone who can help (ashughes, tester2, ...)
  • Smoketests: 3 people (ashughes, tester2, ...)
  • BFTs: 3 people (ashughes, tester2, ...)
  • l10n checks: 3 people (tester1, tester2, ...)
  • Updates checks: 3 people (ashughes, tester2, ...)

Builds

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

ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/3.5.2-candidates/build1/

Test Results

Bugs to Verify (To be added)

Important: Please read Sam's post on dev-planning regarding the new verification editing procedures.