QA/Execution/Web Testing/Project Checklist

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

• All supported browsers look "pretty good" and are 100% functional
  • If not, exceptions are noted and called out prior to shipping
• Team has gone through https://wiki.mozilla.org/WebDev:FrontendCodeStandards

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

• HTML validates: http://html5.validator.nu/

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)
  • CDN is hooked up, if needed (static images, CSS, JS, videos)

Security

• Gone through https://wiki.mozilla.org/WebAppSec/Secure_Coding_QA_Checklist and filed the appropriate bugs
• Runs on both HTTP / HTTPS? Mixed-content warnings?
  • Check to see that third-party assets use relative paths, where possible

Project/release-cycle

• Has a Webdev bug, filed from https://intranet.mozilla.org/webtools/authenticate/login
  • Has a test plan (which can augment this, but lists specific bugs, milestones, project owners, etc.)
    • Reviewed by team

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