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

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 2: Line 2:


=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 13: 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 22: 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

Revision as of 08:44, 10 February 2010

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 (XHTML 1.0 Strict, etc.)
    • Creating and running automation scripts (such as Selenium)

Level 2

(Example sites: SpreadFirefox [production, redesign is a Level 1])

  • 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)
    • Can be a specific set of bugs, or time-based
    • (Or a combination of the above, customized)

Level 3

(Example sites: Personas/Labs)

  • Provide guidance on test approaches/best practices
  • Provide as-needed test assistance to the development team, who should do the majority of the bug verifications
  • Typically don't attend triage meetings
    • "Testing when we can fit it in"