Thunderbird:2.0.0.15:Test Plan: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
Line 9: Line 9:


== QA Details ==
== QA Details ==
* Smoketests: 6/17
* Code freeze: 6/6
* Bug Verification: 6/17-18
* Builds start: 6/19
* BFTs: 6/18-6/20
* QA starts: June 6/23
* l10n Testing: 6/23
* Release to beta channel: 6/27
* Betatest Channel Testing: 6/24-25
* Final Release: 7/3
* Beta Channel Testing: 6/24-25
 
* Smoketests: 6/23
* BFTs: 6/24-6/26
* l10n Testing: 6/26
* Betatest Channel Testing: 6/27
* Beta Channel Testing: 6/27


Release to Beta channel on Wednesday, 6/25 at 12:00 PM.
Release to Beta channel on Wednesday, 6/25 at 12:00 PM.


* Beta period - 6/25 to 7/1
* Beta period - 6/27 to 7/3
* Releasetest & Release Update Testing: 7/2
* Releasetest & Release Update Testing: 7/3
* Release to World: 7/2 - 3:00 PM
* Release to World: 7/3 - 3:00 PM


=== Details ===
=== Details ===

Latest revision as of 22:04, 19 June 2008

Test Plan for Thunderbird 2.0.0.15

Schedule

  • Code freeze: 6/6
  • Builds start: 6/19
  • QA starts: June 6/23
  • Release to beta channel: 6/27
  • Final Release: 7/3

QA Details

  • Code freeze: 6/6
  • Builds start: 6/19
  • QA starts: June 6/23
  • Release to beta channel: 6/27
  • Final Release: 7/3
  • Smoketests: 6/23
  • BFTs: 6/24-6/26
  • l10n Testing: 6/26
  • Betatest Channel Testing: 6/27
  • Beta Channel Testing: 6/27

Release to Beta channel on Wednesday, 6/25 at 12:00 PM.

  • Beta period - 6/27 to 7/3
  • Releasetest & Release Update Testing: 7/3
  • Release to World: 7/3 - 3:00 PM

Details

Testing

  • BFT on Windows, Mac, and Linux
  • Bug verifications (security and critical)

Testing Results

RC Status
Smoketests BFTs
Thunderbird 2.0.0.13rc1 Team RESULT Team RESULT

RC1 Smoketests

  • Windows XP (tester) - result
  • Windows Vista (tester) - result
  • Mac OS X 10.5 (tester) - result
  • Linux (abillings) - result

BFTs

  • Windows XP (team) - result
  • OS X (team) - result
  • Linux (team) - result

Testing Details

Bugs

Bug Verifications

When you verify the bug is fixed:

  • If you test on Trunk, resolve it as VERIFIED FIXED
  • If you test on 1.8.1.x branch, replace the fixed1.8.1.15 keyword with verified1.8.1.15

Branch Bugs

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.

Bugs Found during testing: