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 5: | Line 5: | ||
** Devising a test plan | ** Devising a test plan | ||
** Executing the test plan | ** Executing the test plan | ||
*** Full browser-compatibility | *** Full browser-compatibility testing | ||
*** JavaScript-disabled testing | *** JavaScript-disabled testing | ||
*** Doctype validation | *** Doctype validation | ||
Revision as of 02:50, 23 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 testing
- JavaScript-disabled testing
- Doctype validation
- Creating and running automation scripts (such as Selenium)
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