QA/Execution/Web Testing/Project Checklist: Difference between revisions
< QA | Execution | Web Testing
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 14: | Line 14: | ||
***Firefox 3.5 | ***Firefox 3.5 | ||
***Latest beta | ***Latest beta | ||
=General= | =General= | ||
*HTML validates: http://html5.validator.nu/ | *HTML validates: http://html5.validator.nu/ | ||
| Line 21: | Line 22: | ||
*l10n: other locales look fine (special chars, Unicode, etc.) | *l10n: other locales look fine (special chars, Unicode, etc.) | ||
*Correct timestamps | *Correct timestamps | ||
=Performance/load testing= | =Performance/load testing= | ||
*Doesn't tank on [http://developer.yahoo.com/yslow/ YSlow!] (Strive for an A with ruleset v2) | *Doesn't tank on [http://developer.yahoo.com/yslow/ YSlow!] (Strive for an A with ruleset v2) | ||
**CDN is hooked up, if needed (static images, CSS, JS, videos) | **CDN is hooked up, if needed (static images, CSS, JS, videos) | ||
*Load-tested? | *Load-tested? | ||
=Accessibility= | |||
*Is the site generally accessible? | |||
=Security= | =Security= | ||
| Line 30: | Line 34: | ||
*Runs on both HTTP / HTTPS? Mixed-content warnings? | *Runs on both HTTP / HTTPS? Mixed-content warnings? | ||
**Check to see that third-party assets use relative paths, where possible | **Check to see that third-party assets use relative paths, where possible | ||
=Project/release-cycle= | =Project/release-cycle= | ||
*Has a Webdev bug, filed from https://intranet.mozilla.org/webtools/authenticate/login | *Has a Webdev bug, filed from https://intranet.mozilla.org/webtools/authenticate/login | ||
Revision as of 07:22, 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
- 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
- Appropriate fallback in place and working?
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/load testing
- Doesn't tank on YSlow! (Strive for an A with ruleset v2)
- CDN is hooked up, if needed (static images, CSS, JS, videos)
- Load-tested?
Accessibility
- Is the site generally accessible?
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
- Has a test plan (which can augment this, but lists specific bugs, milestones, project owners, etc.)
- Has clear bug-filing/tracking, either in a new Bugzilla component, existing (with whiteboard, etc.), or in Basecamp
- If in Bugzilla, has clear milestones
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)
- Any rewrite/redirect rules are in place and working?
Tools
- You're using as many of the tools as appropriate