1,457
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 16:03, 2 April 2009
, 2 April 2009no edit summary
No edit summary |
Samuelsidler (talk | contribs) 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 | Note: Projects will not have QA coverage after 6pm unless this has been negotiated at least a week prior or is an emergency. | ||
==== 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 | ||
| Line 10: | Line 14: | ||
** Creating and running automation scripts (such as Selenium) | ** Creating and running automation scripts (such as Selenium) | ||
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 devising a test plan | * Help devising a test plan | ||
* More milestone-based testing support (QA tests at various checkpoints) | * More milestone-based testing support (QA tests at various checkpoints) | ||
Level 3 | ==== 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 | ||