Firefox:1.5.0.8:Test Plan

General Firefox 1.5.0.x Test Plan

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

Assumptions

• This release will be piggy-backing on 1.8.1
• Builds should have gone through the l10n meta-diff checker and the update checker before they are released to QA

Current Tasks

• Bug triage
• Test plan completion
• Minor/Major Software Updates discussions and testing
• Bug verification
• Tuesday, October 24 - Smoketests - tracy - PASS

Schedule

Tuesday, October 17

• Start bug verifications for bugs marked fixed1.8.0.8
• Post to QA blog for Community Testing ?

Friday, October 20

• Continue bug verifications
• Start testing minor/major softare updates with mock-ups provided by Seth

Tuesday, October 24

• FF 1.5.0.8rc1 builds ready
• Firefox Smoketets on all platforms - tracy - PASS
• BFT's started BFT Results
  • Basic Functional Tests (BFTs)
• TB 1.5.0.8rc1 builds to be started by the end of the day

Wednesday, October 25

• Firefox release candidate builds should be available for Win/Linux/PPC
• Smoketests (rc1) on Windows, Linux, Mac en-us
  • If smoketests go well, start BFTs

Thursday, October 26

• Firefox BFTs
• Build should begin l10n packaging after BFTs signoff

Friday, October 27

• Testing of QA identified hot spots
• Targeted exploratory testing over Developer identified hot spots (minor/major software updates, for example)

Monday, October 30, 31

• L10n + Updates testing

Wednesday, November 1st

• Firefox 1.5.0.8 is released, probably 4pm
• Spot check live updates

Thusday, November 2, 3, 6

• Start special distro spotchecks, and continue until Monday, Nov 6

Tuesday, November 7, 8

• Test updates for special distributions

Thursday, November 9

• Special distributions are released.
• Live updates for special distros.

Test Results

Any 1.5.0.8 testing results that will help us track progress, identify regressions, and verify fixes should go here.

• Basic Functional Tests (BFTs)
• l10n related testing
• Software Update Testing

The above list is just a sample of what we will be testing and links to blank pages we should us to track our test results. Please add any other test results here. Thanks!

Bug Verifications

When you verify the bug is fixed, resolve it as VERIFIED FIXED and replace the fixed1.8.0.8 keyword with verified1.8.0.8

Tips:

• Bugs verified on 1.8.1 still need to be verified in 1.8.0.8
• 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.

Fixed

• fixed 1.5.0.8 bugs

Verified

• verified 1.5.0.8 bugs

Priority Verifications

• 6 mail bugs ("fixed1.8.0.8" bugs, component is "mailnews" or product is "thunderbird")
  • mail bugs

• 16 critical bugs ("fixed1.8.0.8" bugs, no "needs testcase" in status whiteboard, and severity is "critical")
  • critical bugs

• 5 security bugs ("fixed1.8.0.8" bugs, no "needs testcase" in status whiteboard, and is marked "security-sensitive"):
  • security bugs

Note: If you run into a difficult bug, just add the "[need testcase]" in the status whiteboard and move on.