QA archive/Team/What We Do: Difference between revisions
< QA archive | Team
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
QA Team structure and members | = QA Team structure and members = | ||
* Tools dev - robcee, alice, coop | * Tools dev - robcee, alice, coop | ||
* Automated test development - Martijn (mw22), bc, ctalbert | * Automated test development - Martijn (mw22), bc, ctalbert | ||
* Test Execution - | * Test Execution - marcia, tracy, juanb, tomcat, tchung, abillings, stephend | ||
* Other: Community- | * Other: Community-jay, Analysis-ss, Accessibility-tkeenen | ||
Concepts | = Concepts = | ||
* Developers handle unit tests | * Developers handle unit tests | ||
* Create automated functional/integration/system tests where possible | * Create automated functional/integration/system tests where possible | ||
| Line 11: | Line 11: | ||
* Right tool for the job - depends on stage of the project and nature of the thing being testing | * Right tool for the job - depends on stage of the project and nature of the thing being testing | ||
Test Execution | = Test Execution = | ||
* Products covered: FFx, TBird, customer extensions or branding (kodak, ebay, world cup) | * Products covered: FFx, TBird, customer extensions or branding (kodak, ebay, world cup) | ||
* Releases covered: Major releases, security releases, partner builds, AMO/WebDev, | * Releases covered: Major releases, security releases, partner builds, AMO/WebDev, | ||
| Line 23: | Line 23: | ||
** Extension testing | ** Extension testing | ||
Analysis | = Analysis = | ||
* bug triage, troubleshooting, investigation | * bug triage, troubleshooting, investigation | ||
* Hendrix | * Hendrix | ||
| Line 31: | Line 31: | ||
Test Development | = Test Development = | ||
* Manual tests in litmus | * Manual tests in litmus | ||
* Automated tests | * Automated tests | ||
| Line 39: | Line 39: | ||
** Test Tools (see below) | ** Test Tools (see below) | ||
Test Tools | = Test Tools = | ||
* Tools we have developed for QA use or general use. | * Tools we have developed for QA use or general use. | ||
* RefTest | * RefTest | ||
| Line 51: | Line 51: | ||
* Spider | * Spider | ||
Community | = Community = | ||
* [http://quality.mozilla.org/ QMO] | * [http://quality.mozilla.org/ QMO] | ||
* Test days | * Test days | ||
Revision as of 22:48, 17 July 2007
QA Team structure and members
- Tools dev - robcee, alice, coop
- Automated test development - Martijn (mw22), bc, ctalbert
- Test Execution - marcia, tracy, juanb, tomcat, tchung, abillings, stephend
- Other: Community-jay, Analysis-ss, Accessibility-tkeenen
Concepts
- Developers handle unit tests
- Create automated functional/integration/system tests where possible
- Use human eyes and ears where necessary
- Right tool for the job - depends on stage of the project and nature of the thing being testing
Test Execution
- Products covered: FFx, TBird, customer extensions or branding (kodak, ebay, world cup)
- Releases covered: Major releases, security releases, partner builds, AMO/WebDev,
- Activities:
- bug verification
- en-US smoke tests, BFT, FFT
- L10n
- focused testing/exploratory testing
- Updates
- Top sites
- Extension testing
Analysis
- bug triage, troubleshooting, investigation
- Hendrix
- Reporter
- crashers - Talkback/Breakpad
- UNCO - unconfirmed bugs triage- graph
Test Development
- Manual tests in litmus
- Automated tests
- from bugs
- for new features
- eggplant tests
- Test Tools (see below)
Test Tools
- Tools we have developed for QA use or general use.
- RefTest
- Mochitest
- XPCShell
- Buildbot execution Infrastructure
- Talos - performance framework
- Minotaur - preferences checking tool for L10n and Partner builds
- L10n Metadiff
- Update Checker
- Spider