Firefox:1.5.0.8:Test Plan: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
''' | = General Firefox 1.5.0.x Test Plan = | ||
'''NOTES: This will be updated shortly, for 1.5.0.8''' | |||
== Bug Verifications == | |||
'''Identify bugs to be verified''' | |||
* Triage fixed bugs and categorize | |||
** Focus on security and critical bugs first | |||
** Add "testcase" keyword for those bugs that have reproducible steps and/or attached testcase(s) | |||
** Identify difficult to reproduce bugs that do not have a testcase | |||
*** add [need testcase] in status whiteboard. | |||
*** request more info from reporter, developer, or anyone interested in the bug | |||
** Spot check "no verification necessary" bugs | |||
*** Usually internal architecture changes with no externally visible effects | |||
*** Quick code inspection and checkin verification with bonsai | |||
'''Confidence metrics and sign-off requirements''' | |||
* Security bug verifications: 100% | |||
* Critical bug verifications: 100% | |||
* Non-critical bug verifications will be done on a case by case basis, depending on developer feedback and community testing. | |||
'''QA resources''' | |||
* MoCo QA is responsible for: | |||
** Security and critical bug verifications | |||
** Some non-critical bugs and special test cases | |||
** Providing bug lists to the community and pointing people to the wiki page | |||
* Mozilla Community tasks: | |||
** Test and help verify fixes for non-security bugs | |||
* Target markets and Mozilla partners: | |||
** IBM for enterprise deployment functionality | |||
** Mozilla Japan for jp-critical issues | |||
== Regression Testing == | |||
* Smoke Tests | |||
* BFT on all three platforms | |||
* Java Script | |||
* Top Sites (See FFT) | |||
* Key extensions | |||
* Performance | |||
** Gross memory usage | |||
* Security Test Library tests | |||
== Install Testing == | |||
* Test en-US after initial packaging. | |||
* Test locales after locale packaing. | |||
== L10n Testing == | |||
* More in depth testing of 5 locals using Litmus L10n tests (AKA Sara's checklist) | |||
* basic install/version id checks | |||
* L10n test matrix (add link here!) | |||
* [http://wiki.mozilla.org/L10n:Home_Page Axel's external L10n status and owner info] | |||
== Extension Testing == | |||
* [https://addons.mozilla.org/extensions/showlist.php?application=firefox&category=Popular Top 10 AMO extensions] according to download numbers. | |||
* [https://addons.mozilla.org/recommended.php Recommended sites] | |||
* http://developer.mozilla.org/contests/extendfirefox/ | |||
== Update Testing == | |||
This is the testing of the partial and full update .mar files for the various locales once the main downloads are released. | |||
== Community Testing == | |||
* [http://wiki.mozilla.org/Mozilla_QA_Community Mozilla QA Community Wiki] - Please go here for all community related updates and activities. | |||
== Configuration Testing == | |||
We need to describe our configuration testing approach better. For now, we are generally testing these OS's: | |||
* Windows XP | |||
* MacOS 10.3, 10.4 | |||
* Linux Ferdora Core 4 | |||
But we need to consider our system requirements statements. I have seen at least three versions. Here is one: | |||
* [http://www.mozilla.com/firefox/system-requirements.html mozilla.com->Products Tab -> Firefox -> System Requirements link] |
Revision as of 17:16, 18 October 2006
General Firefox 1.5.0.x Test Plan
NOTES: This will be updated shortly, for 1.5.0.8
Bug Verifications
Identify bugs to be verified
- Triage fixed bugs and categorize
- Focus on security and critical bugs first
- Add "testcase" keyword for those bugs that have reproducible steps and/or attached testcase(s)
- Identify difficult to reproduce bugs that do not have a testcase
- add [need testcase] in status whiteboard.
- request more info from reporter, developer, or anyone interested in the bug
- Spot check "no verification necessary" bugs
- Usually internal architecture changes with no externally visible effects
- Quick code inspection and checkin verification with bonsai
Confidence metrics and sign-off requirements
- Security bug verifications: 100%
- Critical bug verifications: 100%
- Non-critical bug verifications will be done on a case by case basis, depending on developer feedback and community testing.
QA resources
- MoCo QA is responsible for:
- Security and critical bug verifications
- Some non-critical bugs and special test cases
- Providing bug lists to the community and pointing people to the wiki page
- Mozilla Community tasks:
- Test and help verify fixes for non-security bugs
- Target markets and Mozilla partners:
- IBM for enterprise deployment functionality
- Mozilla Japan for jp-critical issues
Regression Testing
- Smoke Tests
- BFT on all three platforms
- Java Script
- Top Sites (See FFT)
- Key extensions
- Performance
- Gross memory usage
- Security Test Library tests
Install Testing
- Test en-US after initial packaging.
- Test locales after locale packaing.
L10n Testing
- More in depth testing of 5 locals using Litmus L10n tests (AKA Sara's checklist)
- basic install/version id checks
- L10n test matrix (add link here!)
- Axel's external L10n status and owner info
Extension Testing
- Top 10 AMO extensions according to download numbers.
- Recommended sites
- http://developer.mozilla.org/contests/extendfirefox/
Update Testing
This is the testing of the partial and full update .mar files for the various locales once the main downloads are released.
Community Testing
- Mozilla QA Community Wiki - Please go here for all community related updates and activities.
Configuration Testing
We need to describe our configuration testing approach better. For now, we are generally testing these OS's:
- Windows XP
- MacOS 10.3, 10.4
- Linux Ferdora Core 4
But we need to consider our system requirements statements. I have seen at least three versions. Here is one: