QA/Execution/Web Testing/Project Checklist: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 34: Line 34:
*Google Maps API key on staging?
*Google Maps API key on staging?
*Metrics code is correct/working for the site (typically Webtrends)
*Metrics code is correct/working for the site (typically Webtrends)
=Tools=
*You're using as many of the [https://wiki.mozilla.org/QA/Execution/Web_Testing#Useful_Tools tools] as appropriate

Revision as of 06:58, 6 January 2011

Purpose of this document


This is meant to be a quite-literal checklist for determing "go/no-go" status for your website. Where it doesn't apply, feel free to use it rather as a discussion point, but be sure all points are raised and noted.

Browser compatibility/coding standards

Video Support

  • What are the supported video formats?
    • Appropriate fallback in place and working?
      • No Flash
      • Firefox 3.0
      • Firefox 3.5
      • Latest beta

General

RSS Feeds

  • Validate: http://feedvalidator.org/
  • Links all work
  • l10n: other locales look fine (special chars, Unicode, etc.)
  • Correct timestamps

Performance

  • Doesn't tank on YSlow! (Strive for an A with ruleset v2)

Security

Project/release-cycle

Site Config

  • Has a favicon? That works in IE, too?
  • reCaptcha APIs on staging?
  • Google Maps API key on staging?
  • Metrics code is correct/working for the site (typically Webtrends)

Tools

  • You're using as many of the tools as appropriate