Firefox:3.0.2:Test Plan: Difference between revisions
Jump to navigation
Jump to search
m (→Test Results) |
(→Builds) |
||
| Line 30: | Line 30: | ||
== Builds == | == Builds == | ||
*ftp://ftp.mozilla.org/pub/firefox/nightly/3.0.2-candidates/build2/ | |||
*Linux | |||
**Build ID: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.2) Gecko/2008082713 Firefox/3.0.2 | |||
== Test Results == | == Test Results == | ||
Revision as of 00:01, 28 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
- Linux
- Build ID: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.2) Gecko/2008082713 Firefox/3.0.2
Test Results
| Windows | Mac | Linux | |
|---|---|---|---|
| Smoketests | Tracy result | Tomcat result | Marcia result |
| BFTs | Tracy result | Tomcat result | Marcia result |
| L10n | Tracy result | Tomcat result | Marcia result |
| Updates | Tracy Betatest - result Beta - result Releasetest - result Release - tbd |
Tomcat Betatest - result Beta - result Releasetest - result Release - tbd |
Marcia Betatest - result Beta - result Releasetest - result Release - result |
Detailed Test Results
Bug Verifications
When you verify the bug is fixed:
- Mark the whiteboard from fixed1.9.0.2 to verified1.9.0.2
- Fixed 3.0.2 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.