Releases/Firefox 3.0.6/Test Plan: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 23: Line 23:
* Builds start: January 19
* Builds start: January 19
* QA (part 2) starts: 1/20
* QA (part 2) starts: 1/20
** Smoketests: 1/20 - 1/21 - 2 people
** Smoketests: 1/20 - 1/21 - 3 people
** BFTs: 1/22 - 1/23 - 2 people
** BFTs: 1/22 - 1/23 - 3 people
** l10n Testing: November 1/26 - 2 people
** l10n Testing: November 1/26 - 3 people
** Betatest & Beta Channel Testing: 1/27 - 2 people
** Betatest & Beta Channel Testing: 1/27 - 3 people
* Release to beta channel: 1/27
* Release to beta channel: 1/27
** Releasetest & Release Channel Testing: 2/3 - 3 people
** Releasetest & Release Channel Testing: 2/3 - 3 people

Revision as of 17:11, 6 January 2009

General Firefox 3.0.6 Test Plan

This is the basic set of tests we run for every security & maintenance release.

Description of Release

3.0.6 is a normal security release for Firefox.

Specific Test Plan for this Release

Nothing specific for this release.

Assumptions

Current Tasks

  • Ongoing: Waiting for Builds

Schedule

This is an estimated schedule as a normal security release.

  • Tree opens: 12/5
  • Code freeze: 1/6 11:59pm
  • QA (part 1) starts: January 7
  • Builds start: January 19
  • QA (part 2) starts: 1/20
    • Smoketests: 1/20 - 1/21 - 3 people
    • BFTs: 1/22 - 1/23 - 3 people
    • l10n Testing: November 1/26 - 3 people
    • Betatest & Beta Channel Testing: 1/27 - 3 people
  • Release to beta channel: 1/27
    • Releasetest & Release Channel Testing: 2/3 - 3 people
  • Final Release: 2/3

Test Assignments:

  • Smoketests, BFT
    • juanb
    • abillings
  • l10n Testing
    • juanb
    • abillings
  • Betatest/Beta updates
    • juanb
    • abillings
  • Releasetest/Release updates
    • juanb
    • abillings

Builds

Test Results

Builds
Firefox 3.0.6 Build 1
Smoketests Team RESULT
BFTs Team RESULT
l10n Team RESULT


Bug Verifications

When you verify the bug is fixed:

Tips:

  • If you don't see an easy way to verify or need further clarification add a comment to the bug or add "[needs testcase]" (without quotes) to the bug's Status Whiteboard.

Target Bugs to Verify

None

Dependent Bugs to Verify

None