Firefox:2.0.0.6:Test Plan
Contents
General Firefox 2.0.0.6 Test Plan
This is the basic set of tests we run for every security & maintenance release.
Description of Release
Specific Test Plan for this Release
We need to test the interaction between Firefox and 3rd party applications. Thunderbird is affected as well.
See Protocol Handler Testing for ongoing information and a link to a Google Spreadsheet with protocol handlers to test.
RStrong sent the following to the team:
Bug 389469 has been filed to track the fallout (if any) from the landing of Bug 389106 (e.g. escaping of back-ticks, double-quotes, and spaces when calling external protocol handlers).
The next steps are to get the community involved (e.g. via the QA Blog, forum posts, mailing list, etc.) in verifying that this change hasn't broken any third party applications so we can make an informed decision regarding the risk of this change.
Attached to Bug 389469 is a compiled list of protocol handlers from numerous Windows systems that can be used as a starting point for identifying the protocols / apps to test. The list has an "IsSafe?" column that may contain an X for protocols I am quite sure should work fine with the additional escaping. Lists compiled from Mac OS X and Linux systems will hopefully be forthcoming.
When testing these protocols an application that handles the protocol must be installed on your system and registered to handle the protocol. I highly recommend that the callout to the community be very clear on this in order to lessen invalid reports.
Assumptions
Current Tasks
- Ongoing: Bug Verifications
Schedule
- First Candidates Available: 7/28
- Final release scheduled: Week of 7/30-8/3
Test Results
Smoketests | |
---|---|
Firefox 2.0.0.6 | Tomcat PASS |
Smoketests | BFTs | |
---|---|---|
Firefox 2.0.0.6 | Tomcat PASS | Tomcat PASS |
Smoketests | BFTs | |
---|---|---|
Firefox 2.0.0.6 | Tomcat PASS | Tomcat PASS |
- Smoketests and BFTs
- l10n related testing
- Updates Testing
- Protocol Handler Testing
- Protocol Handler Testing Part 2
- Addon Test Results
- Vista Focused Testing (deprecated)
- Vista Updates Testing (deprecated - included in software updates)
- Distro Test Results
- Security Regression tests
- Javascript tests
- Top Sites (See FFT)
- Key extensions
- Performance
- Gross memory usage
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.5 keyword with verified1.8.1.5
- Verified Bugs for 2.0.0.6 - waiting for first builds.
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.