QA/Execution/Web Testing/Support Levels: Difference between revisions

QA/Execution/Web Testing/Support Levels (view source)

134 bytes added , 10 February 2010

no edit summary

Confirmed users

9,511

edits

@@ 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; it is meant to be a guide when discussing QA's role in a project, and can (and probably should) be customized per-project.
-'''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: [http://addons.mozilla.org AMO], [http://www.mozilla.com Mozilla.com], [http://support.mozilla.com SUMO])''
-= Level 1 =
-''(Example sites: AMO, Mozilla.com, SUMO)''
 * End-to-end testing support, consisting of:
@@ Line 14: / Line 12: @@
 ** Creating and running automation scripts (such as Selenium)
-= Level 2 =
+=Level 2=
-''(Example sites: SpreadFirefox [production, redesign is a Level 1])''
+''(Example sites: [http://www.spreadfirefox.com SpreadFirefox] [production, redesign is a Level 1])''
 * Provide basic functionality/sanity test/smoke/integration testing on a high-level basis
@@ Line 23: / Line 21: @@
 ** (Or a combination of the above, customized)
-= Level 3 =
+=Level 3=
-''(Example sites: Personas/Labs)''
+''(Example sites: [http://www.getpersonas.com Personas]/Labs)''
 * Provide guidance on test approaches/best practices