Difference between revisions of "Template:Testchecklist"

From 2value wiki 2
Jump to navigation Jump to search
Line 2: Line 2:
 
</noinclude><!--
 
</noinclude><!--
 
-->
 
-->
−
 
 
==Frontend tests==
 
==Frontend tests==
 
: 1) valideert de html en de css
 
: 1) valideert de html en de css
Line 13: Line 12:
 
:::1) geeft status report foutmeldingen?
 
:::1) geeft status report foutmeldingen?
 
: 4) kan men inloggen? zijn de userrechten voor tenminste 1 redacteur geregeld
 
: 4) kan men inloggen? zijn de userrechten voor tenminste 1 redacteur geregeld
−
 
 
==Pre-Launch==
 
==Pre-Launch==
 
===Content and Style===
 
===Content and Style===
Line 29: Line 27:
 
##Variations in words (e.g. Websites vs Web Sites, or UK vs US spelling)  
 
##Variations in words (e.g. Websites vs Web Sites, or UK vs US spelling)  
 
##Treatment of bulleted lists (e.g. periods or commas at end of each item)
 
##Treatment of bulleted lists (e.g. periods or commas at end of each item)
−
}}
+
}}{{#if: {{{level}}}=medium || {{{level}}} = pro  
−
{{#if: {{{level}}}=medium || {{{level}}} = pro  
 
 
#Check for hard-coded links to staging domain (i.e. ensure all links will change to ‘live’ URL/domain when site is launched)  
 
#Check for hard-coded links to staging domain (i.e. ensure all links will change to ‘live’ URL/domain when site is launched)  
 
#Ensure no test content on site
 
#Ensure no test content on site
−
}}
+
}}{{#if: {{{level}}}=pro
−
{{#if: {{{level}}}=pro
 
 
#Check how important pages (e.g. content items) print  
 
#Check how important pages (e.g. content items) print  
 
#For re-designs, ensure important old/existing URLs are redirected to relevant new URLs, if the URL scheme is changing  
 
#For re-designs, ensure important old/existing URLs are redirected to relevant new URLs, if the URL scheme is changing  
 
#Check all ‘Hidden Copy’ (e.g. alt text, transcriptions, text in JavaScript functions)  
 
#Check all ‘Hidden Copy’ (e.g. alt text, transcriptions, text in JavaScript functions)  
 
}}
 
}}
−
 
−
 
 
===Standards and Validation===
 
===Standards and Validation===
 
#Accessibility  
 
#Accessibility  
Line 46: Line 40:
 
#JavaScript validation  
 
#JavaScript validation  
 
#CSS validation -> http://jigsaw.w3.org/css-validator/
 
#CSS validation -> http://jigsaw.w3.org/css-validator/
−
 
 
{{#if: {{{level}}}=medium || {{{level}}} = pro
 
{{#if: {{{level}}}=medium || {{{level}}} = pro
 
===Search Engine Visibility, SEO and Metrics===
 
===Search Engine Visibility, SEO and Metrics===
 
#Page Titles are important; ensure they make sense and have relevant keywords in them.  
 
#Page Titles are important; ensure they make sense and have relevant keywords in them.  
 
#Create metadata descriptions for important pages.
 
#Create metadata descriptions for important pages.
−
}}
+
}}{{#if: {{{level}}} = pro  
−
{{#if: {{{level}}} = pro  
 
 
#Check for canonical domain issues (e.g. variations in links to http://site.com http://www.site.com http://www.site.com/index.html should be reduced to a single consistent style)  
 
#Check for canonical domain issues (e.g. variations in links to http://site.com http://www.site.com http://www.site.com/index.html should be reduced to a single consistent style)  
 
#Ensure content is marked-up semantically/correctly (HTML-tags, etc.)  
 
#Ensure content is marked-up semantically/correctly (HTML-tags, etc.)  
Line 61: Line 53:
 
#Configure Google Webmaster Console and Yahoo! Site Explorer <br/>-> http://www.google.com/webmasters/tools (use twovalue@gmail.com as username. See http://service.2value.nl for password)
 
#Configure Google Webmaster Console and Yahoo! Site Explorer <br/>-> http://www.google.com/webmasters/tools (use twovalue@gmail.com as username. See http://service.2value.nl for password)
 
}}
 
}}
−
 
 
===Functional Testing===
 
===Functional Testing===
 
#Check all bespoke/complex functionality  
 
#Check all bespoke/complex functionality  
Line 74: Line 65:
 
#Configure backup schedule, and test recovery from backup.  
 
#Configure backup schedule, and test recovery from backup.  
 
#Protect any sensitive pages (e.g. administration area)  
 
#Protect any sensitive pages (e.g. administration area)  
−
}}
+
}}{{#if: {{{level}}} = pro
−
{{#if: {{{level}}} = pro
 
 
#Use robots.txt where necessary
 
#Use robots.txt where necessary
 
#Security/Penetration test  
 
#Security/Penetration test  
Line 88: Line 78:
 
#Check and implement caching where necessary <br/>-> [http://www.nonumber.nl/extensions/cachecleaner NoNumber Cache Cleaner]
 
#Check and implement caching where necessary <br/>-> [http://www.nonumber.nl/extensions/cachecleaner NoNumber Cache Cleaner]
 
#Check total page size/download time <br/>-> Firefox plugin Yslow
 
#Check total page size/download time <br/>-> Firefox plugin Yslow
−
}}
+
}}{{#if: {{{level}}} = pro
−
{{#if: {{{level}}} = pro
 
 
#Minify/compress static (JavaScript/HTML/CSS) files <br/>-> use compress plugins
 
#Minify/compress static (JavaScript/HTML/CSS) files <br/>-> use compress plugins
 
#Optimise your CSS: use short image paths; make full-use ‘cascading’ nature of CSS, etc. <br/>-> use compress plugins
 
#Optimise your CSS: use short image paths; make full-use ‘cascading’ nature of CSS, etc. <br/>-> use compress plugins
Line 95: Line 84:
 
#Check configuration at every level (Web server, Database, any other software e.g. Content Management System)  
 
#Check configuration at every level (Web server, Database, any other software e.g. Content Management System)  
 
#Configure server-based logging/measurement tools (e.g. database/web server logging)
 
#Configure server-based logging/measurement tools (e.g. database/web server logging)
−
 
 
#Lees meer hierover in de SlideShare presentatie van [[user:hkuijpers|Hans Kuijpers]] over [http://www.slideshare.net/hans2103/site-performance-optimization-joomla Site Performance Optimization]
 
#Lees meer hierover in de SlideShare presentatie van [[user:hkuijpers|Hans Kuijpers]] over [http://www.slideshare.net/hans2103/site-performance-optimization-joomla Site Performance Optimization]
 
}}
 
}}
−
 
 
===Finishing Touches===
 
===Finishing Touches===
 
#Create a favicon
 
#Create a favicon
Line 106: Line 93:
 
===Joomla! specific===
 
===Joomla! specific===
 
# Remove testcontent from configuration.php
 
# Remove testcontent from configuration.php
−
 
 
{{#if:  {{{level}}} = pro
 
{{#if:  {{{level}}} = pro
 
==Post-Launch==
 
==Post-Launch==
Line 118: Line 104:
 
#Check analytics for problems, popular pages etc. and adjust as necessary  
 
#Check analytics for problems, popular pages etc. and adjust as necessary  
 
#Update content
 
#Update content
−
}}
+
}}{{#if: {{{level}}} = pro
−
{{#if: {{{level}}} = pro
 
 
'''For an updated list check -> http://www.boxuk.com/blog/the-ultimate-website-launch-checklist'''
 
'''For an updated list check -> http://www.boxuk.com/blog/the-ultimate-website-launch-checklist'''
 
}}
 
}}

Revision as of 15:40, 23 November 2010

Template:Testchecklist (talk, backlinks, edit)

Frontend tests

1) valideert de html en de css
2) hoe is de front-end performance
3)cms specific test:
joomla
1) zijn dir rechten goed?
2) is htaccess enabled
drupal
1) geeft status report foutmeldingen?
4) kan men inloggen? zijn de userrechten voor tenminste 1 redacteur geregeld

Pre-Launch

Content and Style

  1. Typography and layout
  1. Consistency

Standards and Validation

  1. Accessibility
  2. HTML validation -> http://validator.w3.org/
  3. JavaScript validation
  4. CSS validation -> http://jigsaw.w3.org/css-validator/

Functional Testing

  1. Check all bespoke/complex functionality
  2. Check search functionality (including relevance of results)
  3. Check on common variations of browser (Internet Explorer, Firefox, Safari, Chrome etc.), version (6, 7, 2.2, 3.1 etc.) and platform (Windows, OSX, Linux)
  4. Check on common variations of Screen Resolution
  5. Test all forms (e.g. contact us, blog comments), including anti-spam features, response emails/text, etc.
  6. Test without JavaScript, Flash, and other plug-ins
  7. Check all external links are valid -> lees meer

Performance

  1. Load test

Finishing Touches

  1. Create a favicon

Joomla! specific

  1. Remove testcontent from configuration.php


Uitleg Template

Een template maken die een parameter mee krijgt? level=basic -> retourneert bulletpoints die dit level in de standaard cheklist behelzen, level=medium -> extra set bullets per onderdeel, etc

Level basic is minimum dat ie terug geeft

Retrieved from "http://wiki.2value.nl/index.php?title=Template:Testchecklist&oldid=8037"