Firefox:1.5.0.7:Test Plan: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 99: Line 99:
'''Verified'''
'''Verified'''
*[https://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=verified1.8.0.7&order=Bug+Number verified 1.5.0.7 bugs]
*[https://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=verified1.8.0.7&order=Bug+Number verified 1.5.0.7 bugs]
=== Priority Verifications ===
* 7 mail bugs ("fixed1.8.0.7" bugs, component is "mailnews" or product is "thunderbird")
**[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&keywords_type=allwords&keywords=fixed1.8.0.7&chfieldto=Now&field0-0-0=component&type0-0-0=substring&value0-0-0=mailnews&field0-0-1=product&type0-0-1=substring&value0-0-1=thunderbird mail bugs]
* 20 critical bugs ("fixed1.8.0.7" bugs, no "needs testcase" in status whiteboard, and severity is "critical")
**[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&keywords_type=allwords&keywords=fixed1.8.0.7&chfieldto=Now&field0-0-0=status_whiteboard&type0-0-0=notsubstring&value0-0-0=need+testcase&field0-1-0=bug_severity&type0-1-0=equals&value0-1-0=critical critical bugs]
* 11 security bugs ("fixed1.8.0.7" bugs, no "needs testcase" in status whiteboard, and is marked "security-sensitive"):
**[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&keywords_type=allwords&keywords=fixed1.8.0.7&chfieldto=Now&field0-0-0=bug_group&type0-0-0=substring&value0-0-0=security&field0-1-0=status_whiteboard&type0-1-0=notsubstring&value0-1-0=need+testcase security bugs]
Note: If you run into a difficult bug, just add the "[need testcase]" in the status whiteboard and move on.





Revision as of 00:02, 7 September 2006

General Firefox 1.5.0.x Test Plan

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


Assumptions

  • 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

Schedule

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

  • Firefox RC4 will be released this afternoon
  • Smoketest Firefox RC4
  • Thunderbird bug verifications

Thursday, September 7th

Friday, September 8th

Monday, September 11th

Tuesday, September 12th

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

Wednesday, September 13th

Thursday, September 14th

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

Tips:

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

Verified

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