Firefox: Plan

From MozillaWiki
Jump to: navigation, search

General Firefox 1.5.0.x Test Plan

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


  • Goal of this release is security fixes and important regressions, other fixes will not be included
  • Builds should have gone through the l10n meta-diff checker and the update checker before they are released to QA
  • Thunderbird will be released a few days after Firefox
  • Monday, September 4th is a holiday

Current Tasks

  • Bug triage
  • Test plan completion
  • Bug verification


Monday, August 28th

  • RC1 delayed till Monday night/Tuesday morning. Shifting Monday's planned activities to Tuesday

Tuesday, August 29th

Wednesday, August 30th

  • Firefox BFTs - PASS
  • Build should begin l10n packaging after BFTs signoff (Rhelmer/TR)
  • Get post up on the QA blog with link to candidate builds
  • Testing of QA identified hot spots
  • Targeted exploratory testing over Developer identified hot spots

Thursday, August 31st

  • Continued testing of developer identified hot spots and bug verifications

Friday, September 1st

Tuesday, September 5th

  • Further bug verifications and testing of hot spots
  • Thunderbird Smoketests
  • Start Thunderbird BFTs

Wednesday, September 6th

Thursday, September 7th

Friday, September 8th

Monday, September 11th

Tuesday, September 12th

Wednesday, September 13th

Thursday, September 14th

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

Bug Verifications

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


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



Priority Verifications

  • 7 mail bugs ("fixed1.8.0.7" bugs, component is "mailnews" or product is "thunderbird")
  • 20 critical bugs ("fixed1.8.0.7" bugs, no "needs testcase" in status whiteboard, and severity is "critical")
  • 11 security bugs ("fixed1.8.0.7" bugs, no "needs testcase" in status whiteboard, and is marked "security-sensitive"):

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

Need Verification

bc's JS bugs:

Cannot Verify