QA/Execution/Web Testing/Support Levels: Difference between revisions
< QA | Execution | Web Testing
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
Level 2: (Example sites, SpreadFirefox) | Level 2: (Example sites, SpreadFirefox) | ||
* Provide basic functionality/sanity test/smoke/integration testing on a high-level basis | * Provide basic functionality/sanity test/smoke/integration testing on a high-level basis | ||
* Help | * Help devising a test plan | ||
* More milestone-based testing support (QA tests at various checkpoints) | |||
Level 3: (Example sites: Personas/Labs) | Level 3: (Example sites: Personas/Labs) | ||
* Provide guidance on test approaches/best practices | * Provide guidance on test approaches/best practices | ||
* Provide as-needed test assistance to the development team | * Provide as-needed test assistance to the development team | ||
Revision as of 22:26, 8 February 2009
Purpose: This page intends to outline the varying support levels for web-application testing
Level 1: (Example sites: AMO, Mozilla.com, SUMO)
- End-to-end testing support, consisting of:
- Devising a test plan
- Executing the test plan
- Full browser-compatibility support
- JavaScript-disabled testing
- Doctype validation
Level 2: (Example sites, SpreadFirefox)
- Provide basic functionality/sanity test/smoke/integration testing on a high-level basis
- Help devising a test plan
- More milestone-based testing support (QA tests at various checkpoints)
Level 3: (Example sites: Personas/Labs)
- Provide guidance on test approaches/best practices
- Provide as-needed test assistance to the development team