Confirmed users
9,511
edits
QA/Execution/Web Testing/Support Levels: Difference between revisions
Jump to navigation
Jump to search
QA/Execution/Web Testing/Support Levels (view source)
Revision as of 22:23, 8 February 2009
, 8 February 2009no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Purpose: This page intends to outline the varying support levels for web-application testing | Purpose: This page intends to outline the varying support levels for web-application testing | ||
Level 1: | Level 1: (Example sites: AMO, Mozilla.com, SUMO) | ||
* End-to-end testing support, consisting of: | * End-to-end testing support, consisting of: | ||
** Devising a test plan | ** Devising a test plan | ||
** Executing the test plan | ** Executing the test plan | ||
Level 2: | 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 devise a test plan | * Help devise a test plan | ||
Level 3: | Level 3: (Example sites: Personas/Labs) | ||
* Provide guidance on test approaches | * Provide guidance on test approaches/best practises | ||
* Provide as-needed test assistance to the development team | * Provide as-needed test assistance to the development team | ||