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

no edit summary
No edit summary
No edit summary
 
(3 intermediate revisions by the same user not shown)
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=
=Level 1=
''(Example sites: AMO, Mozilla.com, SUMO)''
''(Example sites: [http://addons.mozilla.org AMO], [http://www.mozilla.com Mozilla.com], [http://support.mozilla.com SUMO])''


* End-to-end testing support, consisting of:
* End-to-end testing support, consisting of:
Line 15: Line 13:


=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
* Provide basic functionality/sanity test/smoke/integration testing on a high-level basis
Line 24: Line 22:


=Level 3=
=Level 3=
''(Example sites: Personas/Labs)''
''(Example sites: [http://www.getpersonas.com Personas]/Labs)''


* Provide guidance on test approaches/best practices
* Provide guidance on test approaches/best practices
Confirmed users
9,511

edits