Firefox:2.0.0.10:Test Plan: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 16: Line 16:
== Schedule ==
== Schedule ==
* Code Freeze: 11/14
* Code Freeze: 11/14
* Bug Verifications: 11/15 - 2 people
* Bug Verifications: 11/15 - 4 people
* Smoketests: 11/15 - 10:00 AM (4 hours) - 4 people
* Smoketests: 11/15 - 4 people
* Windows BFTs: 11/15 to 11/16 - 2:00 PM (6 hours) - 3 people
* Windows BFTs: 11/16 - 3 people
* l10n Testing: 11/16 - 12:00 PM (4 hours) - 3 people
* l10n Testing: 11/19 - 3 people
* Betatest Channel Testing: 11/19 - 10:00 AM (2 hours) - 3 people
* Betatest Channel Testing: 11/20 - 3 people
* Beta Channel Testing: 11/19 - 1:00 PM (2 hours) - 3 people
* Beta Channel Testing: 11/20 - 3 people


Release to Beta channel on Monday, 11/19 at 3:00 PM.
Release to Beta channel on Tuesday, 11/20 at 3:00 PM.


* Releasetest & Release Update Testing: 11/21 - 10:00 AM (6 hours) - 2 people
* Releasetest & Release Update Testing: 11/27 - 3 people
* Release to World: 11/21 - 4:00 PM
* Release to World: 11/27 - 4:00 PM


== Builds ==  
== Builds ==  

Revision as of 19:39, 15 November 2007

General Firefox 2.0.0.10 Test Plan

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

Description of Release

This is a firedrill release to fix security and stability issues that became clear after Firefox 2.0.0.9 shipped.

Specific Test Plan for this Release

Assumptions

Current Tasks

Schedule

  • Code Freeze: 11/14
  • Bug Verifications: 11/15 - 4 people
  • Smoketests: 11/15 - 4 people
  • Windows BFTs: 11/16 - 3 people
  • l10n Testing: 11/19 - 3 people
  • Betatest Channel Testing: 11/20 - 3 people
  • Beta Channel Testing: 11/20 - 3 people

Release to Beta channel on Tuesday, 11/20 at 3:00 PM.

  • Releasetest & Release Update Testing: 11/27 - 3 people
  • Release to World: 11/27 - 4:00 PM

Builds

Test Results

Daily Builds
Smoketests
Firefox 2.0.0.10 Team RESULT


RC Status
Smoketests BFTs
Firefox 2.0.0.10rc1 Team RESULT 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

Dependent Bugs to Verify

Bug List Here