Confirmed users
6,361
edits
QA/Firefox3/Strategy: Difference between revisions
Jump to navigation
Jump to search
→Areas not Covered
| Line 23: | Line 23: | ||
* Feature Unit Tests - | * Feature Unit Tests - | ||
These are normally covered by feature developers, not QA. However, we do have a Javascript test suite that will collectively find bugs with in-testsuite javascript test cases that Bob Clary will run on occasion. Need more definition here on what QA/Dev should own. | <BR>These are normally covered by feature developers, not QA. However, we do have a Javascript test suite that will collectively find bugs with in-testsuite javascript test cases that Bob Clary will run on occasion. Need more definition here on what QA/Dev should own. | ||
* String Localization Tests - | * String Localization Tests - | ||
Many of these tests are owned by localizers and SmartWare, our third party testing company. See more in the | <BR>Many of these tests are owned by localizers and SmartWare, our third party testing company. See more in the L10n Test Deliverables section. | ||
* In depth functionality of Plugins, Extensions, and Themes - | * In depth functionality of Plugins, Extensions, and Themes - | ||
Many extensions are hosted on AMO, but are not developed and tested by mozilla. We rely on our volunteers to manage these third party extensions. Mozilla QA will focus on high level Addon management, error handling, and a few top extensions supported. But extension functionality will not be covered by Mozilla QA. | <BR>Many extensions are hosted on AMO, but are not developed and tested by mozilla. We rely on our volunteers to manage these third party extensions. Mozilla QA will focus on high level Addon management, error handling, and a few top extensions supported. But extension functionality will not be covered by Mozilla QA. | ||
== Schedule == | == Schedule == | ||