Websites/Mozilla.org/One Mozilla/Documentation/Checklist-QA: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Replaced content with "[https://wiki.mozilla.org/QA/Execution/Web_Testing/Project_Checklist QA's Web Testing Project Checklist]")
Line 1: Line 1:
''March 2012, let's create a basic pre and post-launch QA checklist here''
[https://wiki.mozilla.org/QA/Execution/Web_Testing/Project_Checklist QA's Web Testing Project Checklist]
 
=QA=
 
==Pre-Launch List for New Website/webpages==
*OS & Browser testing - renders gracefully in:
**Safari version #s?
**IE version #s?
**Firefox builds & version #s?
**Chrome version #s?
**Site appears consistent across windows, linux, and mac operating systems
*Style sheets
**Viewable without right-scrolling in 1024 and larger screen size resolutions
**Does it print? (should it print?)
**Does it render for mobile? (should it render for mobile?)
*Spelling & copy
*Page Titles & SEO [https://wiki.mozilla.org/One-Mozilla-Project/Documentation/Checklist-SEO SEO checklist]
*Images/CDN/Caching
*L10N
**User agent testing
*Mobile
**Is there a mobile site?
**Does content (e.g. download buttons) change based on UA detection?
***ios sniffing
***Android sniffing
***B2G sniffing?
*Rich Media:
**Videos, music, and multimedia play on demand only
*Redirects:
**.htaccess, 301 or 302 redirects, manage traffic for moved, renamed, or deleted pages
 
==Post-Launch List for Websites/Webpages==
''not everything can be predicted or tested in pre-launch QA, what can go here for cleanup?''
 
==Blog==
''no staging environment exists, so this is trickier''
*All blogs should be print friendly (Blogzilla covers this)
*All blogs should use Blogzilla (how can we plan for new browser versions?)

Revision as of 18:25, 13 March 2012