Firefox:3.0.2:Test Plan: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 42: Line 42:
|-
|-
| style="background:#ffdead;" | '''Smoketests'''
| style="background:#ffdead;" | '''Smoketests'''
| tester '''result'''
| Tomcat '''result'''
| tester '''result'''
| Tomcat '''result'''
| tester '''result'''
| tester '''result'''
|-
|-
| style="background:#ffdead;" | '''BFTs'''
| style="background:#ffdead;" | '''BFTs'''
| tester '''result'''
| tester '''result'''
| tester '''result'''
| Tomcat '''result'''
| tester '''result'''
| tester '''result'''
|-
|-
| style="background:#ffdead;" | '''L10n'''
| style="background:#ffdead;" | '''L10n'''
| tester '''result'''
| Tomcat '''result'''
| tester '''result'''
| tester '''result'''
| tester '''result'''
| tester '''result'''

Revision as of 11:20, 15 August 2008

General Firefox 3.0.2 Test Plan

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

Description of Release

3.0.2 is a normal security release for Firefox.

Specific Test Plan for this Release

  • Verify the fixed bugs that are going into this release
  • Run smoketest, BFTs, updates, and l10n tests

Assumptions

Current Tasks

  • Ongoing: Bug Reproduction

Schedule

This is an estimated schedule as a normal security release.

  • Code freeze: Aug 15
  • Builds start: Aug 18
  • QA starts: Aug 19 (4 testers)
    • Smoketests: 1 1/2 day
    • BFTs and Bug Verification: 3 days
    • l10n Testing: 1/2 day
    • Betatest & Beta Channel Testing: 1 day
  • Release to beta channel: Aug 27
    • Releasetest & Release Channel Testing: Sept 2
  • Final Release: Sept 3

Builds

Test Results

Builds
Windows Mac Linux
Smoketests Tomcat result Tomcat result tester result
BFTs tester result Tomcat result tester result
L10n Tomcat result tester result tester result
Updates tester
Betatest - result
Beta - result
Releasetest - result
Release - tbd
tester
Betatest - result
Beta - result
Releasetest - result
Release - tbd
tester
Betatest - result
Beta - result
Releasetest - result
Release - result

Detailed Test Results

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.