Difference between revisions of "Template:Testchecklist"

From 2value wiki 2
Jump to navigation Jump to search
 
(12 intermediate revisions by 2 users not shown)
Line 2: Line 2:
 
</noinclude><!--
 
</noinclude><!--
 
-->
 
-->
−
{{#if: {{{level}}}=basic
+
{{Image|name=Checklist256px|width=256px|pad=20px|ilink=File:Checklist256px.png|float=right}}
 
==Frontend tests==
 
==Frontend tests==
 
: 1) valideert de html en de css
 
: 1) valideert de html en de css
Line 13: Line 13:
 
:::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===
−
*Typography and layout
+
#Typography and layout
−
**Check for incorrect punctuation marks, particularly apostrophes, quotation marks and hyphens/dashes  
+
{{#ifexpr: {{#expr: {{#ifeq:{{{level}}}|medium|1|0}} or {{#ifeq:{{{level}}}|pro|1|0}} }} |
−
**Check headings for where you could potentially use ligatures  
+
##Check for incorrect punctuation marks, particularly apostrophes, quotation marks and hyphens/dashes  
−
**Check for widow/orphan terms in important paragraphs  
+
##Check headings for where you could potentially use ligatures  
−
*Spelling and grammar
+
##Check for widow/orphan terms in important paragraphs  
−
*Consistency  
+
#Spelling and grammar
−
**Capitalisation (especially of main headings)  
+
|}}#Consistency  
−
**Tense/Style of writing  
+
{{#ifexpr: {{#expr: {{#ifeq:{{{level}}}|medium|1|0}} or {{#ifeq:{{{level}}}|pro|1|0}} }} |
−
**Recurring/common phrases (e.g. ‘More about X’ links)  
+
##Capitalisation (especially of main headings)  
−
**Variations in words (e.g. Websites vs Web Sites, or UK vs US spelling)  
+
##Tense/Style of writing  
−
**Treatment of bulleted lists (e.g. periods or commas at end of each item)
+
##Recurring/common phrases (e.g. ‘More about X’ links)  
−
*Check for hard-coded links to staging domain (i.e. ensure all links will change to ‘live’ URL/domain when site is launched)  
+
##Variations in words (e.g. Websites vs Web Sites, or UK vs US spelling)  
−
*Ensure no test content on site
+
##Treatment of bulleted lists (e.g. periods or commas at end of each item)
−
*Check how important pages (e.g. content items) print  
+
|}}{{#ifexpr: {{#expr: {{#ifeq:{{{level}}}|medium|1|0}} or {{#ifeq:{{{level}}}|pro|1|0}} }} |
−
*For re-designs, ensure important old/existing URLs are redirected to relevant new URLs, if the URL scheme is changing  
+
#Check for hard-coded links to staging domain (i.e. ensure all links will change to ‘live’ URL/domain when site is launched)  
−
*Check all ‘Hidden Copy’ (e.g. alt text, transcriptions, text in JavaScript functions)  
+
#Ensure no test content on site
 +
|}}{{#ifexpr: {{#expr: {{#ifeq:{{{level}}}|pro|1|0}} }} |
 +
#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  
 +
#Check all ‘Hidden Copy’ (e.g. alt text, transcriptions, text in JavaScript functions)  
 +
|}}
 
===Standards and Validation===
 
===Standards and Validation===
−
{{Who|Developer|Webmaster||||}}
+
#Accessibility  
−
*Accessibility  
+
#HTML validation -> http://validator.w3.org/
−
*HTML validation -> http://validator.w3.org/
+
#JavaScript validation  
−
*JavaScript validation  
+
#CSS validation -> http://jigsaw.w3.org/css-validator/\
−
*CSS validation -> http://jigsaw.w3.org/css-validator/
+
 
 +
Further reading: [[Testing/Technical test]]
  
 +
{{#ifexpr: {{#expr: {{#ifeq:{{{level}}}|medium|1|0}} or {{#ifeq:{{{level}}}|pro|1|0}} }} |
 
===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.
−
*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)  
+
|}}{{#ifexpr: {{#expr: {{#ifeq:{{{level}}}|medium|1|0}} or {{#ifeq:{{{level}}}|pro|1|0}} }} |
−
*Ensure content is marked-up semantically/correctly (HTML-tags, etc.)  
+
#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 target keyword usage in general content  
+
#Ensure content is marked-up semantically/correctly (HTML-tags, etc.)  
−
*Check format (user/search engine friendliness) of URLs  
+
#Check for target keyword usage in general content  
−
*Set up Analytics, FeedBurner, and any other packages for measuring ongoing succes <br/> -> http://www.google.com/analytics (use twovalue@gmail.com as username. See http://service.2value.nl for password)
+
#Check format (user/search engine friendliness) of URLs  
−
*Create an XML Sitemap <br/>-> consider the Joomla! extension [http://extensions.joomla.org/extensions/structure-a-navigation/site-map/3066 Xmap]
+
#Set up Analytics, FeedBurner, and any other packages for measuring ongoing succes <br/> -> http://www.google.com/analytics (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)
+
#Create an XML Sitemap <br/>-> consider the Joomla! extension [http://extensions.joomla.org/extensions/structure-a-navigation/site-map/3066 Xmap]
 +
#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 besproken/complex functionality  
−
*Check search functionality (including relevance of results)  
+
#Check search functionality (including relevance of results)  
−
*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)  
+
#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)  
−
*Check on common variations of Screen Resolution  
+
#Check on common variations of Screen Resolution  
−
*Test all forms (e.g. contact us, blog comments), including anti-spam features, response emails/text, etc.  
+
#Test all forms (e.g. contact us, blog comments), including anti-spam features, response emails/text, etc.  
−
*Test without JavaScript, Flash, and other plug-ins  
+
#Test without JavaScript, Flash, and other plug-ins  
−
*Check all external links are valid -> [[Associate:Checklist/linkcheckers|lees meer]]
+
#Check all external links are valid -> [[Associate:Checklist/linkcheckers|lees meer]]
 +
{{#ifexpr: {{#expr: {{#ifeq:{{{level}}}|medium|1|0}} or {{#ifeq:{{{level}}}|pro|1|0}} }} |
 +
===Security/Risk===
 +
#Configure backup schedule, and test recovery from backup.
 +
#Protect any sensitive pages (e.g. administration area)
 +
|}}{{#ifexpr: {{#expr: {{#ifeq:{{{level}}}|pro|1|0}} }} |
 +
#Use robots.txt where necessary
 +
#Security/Penetration test
 +
#Turn-off verbose error reporting
 +
#Check disk space/capacity
 +
#Set-up email/SMS monitoring/alerts (e.g. for errors, server warnings); consider internal and external monitoring services
 +
|}}
  
−
===Security/Risk===
 
−
*Configure backup schedule, and test recovery from backup.
 
−
*Protect any sensitive pages (e.g. administration area)
 
−
*Use robots.txt where necessary
 
−
*Security/Penetration test
 
−
*Turn-off verbose error reporting
 
−
*Check disk space/capacity
 
−
*Set-up email/SMS monitoring/alerts (e.g. for errors, server warnings); consider internal and external monitoring services
 
 
===Performance===
 
===Performance===
−
{{Who|Webmaster|Developer|Templatebuilder||}}
+
#Load test
−
*Load test  
+
{{#ifexpr: {{#expr: {{#ifeq:{{{level}}}|medium|1|0}} or {{#ifeq:{{{level}}}|pro|1|0}} }} |  
−
*Check image optimisation <br/>-> [http://www.smushit.com/ysmush.it/ All Smush.it]
+
#Check image optimisation <br/>-> [http://www.smushit.com/ysmush.it/ All Smush.it]
−
*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
−
*Minify/compress static (JavaScript/HTML/CSS) files <br/>-> use compress plugins
+
|}}{{#ifexpr: {{#expr:  {{#ifeq:{{{level}}}|pro|1|0}} }} |
−
*Optimise your CSS: use short image paths; make full-use ‘cascading’ nature of CSS, etc. <br/>-> use compress plugins
+
#Minify/compress static (JavaScript/HTML/CSS) files <br/>-> use compress plugins
−
*Check correct database indexing  
+
#Optimise your CSS: use short image paths; make full-use ‘cascading’ nature of CSS, etc. <br/>-> use compress plugins
−
*Check configuration at every level (Web server, Database, any other software e.g. Content Management System)  
+
#Check correct database indexing  
−
*Configure server-based logging/measurement tools (e.g. database/web server logging)
+
#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)
−
 
+
#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===
−
{{Who|Webmaster|Developer|Templatebuilder||}}
+
#Create a favicon
−
*Create custom 404/error pages <br/>-> consider the Joomla! extension [http://extensions.joomla.org/extensions/site-management/url-redirection/9989 Dynamic404]
+
{{#ifexpr: {{#expr: {{#ifeq:{{{level}}}|medium|1|0}} or {{#ifeq:{{{level}}}|pro|1|0}} }} |
−
*Create a favicon
+
#Create custom 404/error pages <br/>-> consider the Joomla! extension [http://extensions.joomla.org/extensions/site-management/url-redirection/9989 Dynamic404]
 +
|}}
 
===Joomla! specific===
 
===Joomla! specific===
−
* Remove testcontent from configuration.php
+
# Remove testcontent from configuration.php
−
 
+
{{#ifexpr: {{#expr: {{#ifeq:{{{level}}}|pro|1|0}} }} |
 
==Post-Launch==
 
==Post-Launch==
 
===Marketing===
 
===Marketing===
−
{{Who|Marketing|||||}}
+
#Social Marketing: Twitter, LinkedIn, Digg, Facebook, Stumbleupon, etc.  
−
*Social Marketing: Twitter, LinkedIn, Digg, Facebook, Stumbleupon, etc.  
+
#Submit to search engines  
−
*Submit to search engines  
+
#Set-up PPC/Google Adwords where necessary  
−
*Set-up PPC/Google Adwords where necessary  
+
#Check formatting of site results in SERPs  
−
*Check formatting of site results in SERPs  
 
 
===Ongoing===
 
===Ongoing===
−
{{Who|Marketing|Webmaster||||}}
+
#Monitor and respond to feedback (direct feedback, on Social Media sites, check for chatter through Google, etc.)  
−
*Monitor and respond to feedback (direct feedback, on Social Media sites, check for chatter through Google, etc.)  
+
#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
+
|}}{{#ifexpr: {{#expr: {{#ifeq:{{{level}}}|medium|1|0}} or {{#ifeq:{{{level}}}|pro|1|0}} }} |
 +
'''For an updated list check -> http://www.boxuk.com/blog/the-ultimate-website-launch-checklist'''
 +
|}}
 +
<noinclude>
 +
==Uitleg Template==
  
−
For an updated list check -> http://www.boxuk.com/blog/the-ultimate-website-launch-checklist
+
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</noinclude>
  
−
<noinclude>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</noinclude>
+
Level ''basic'' is minimum dat ie terug geeft

Latest revision as of 08:50, 13 June 2012

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
  2. 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/\

Further reading: Testing/Technical test


Functional Testing

  1. Check all besproken/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=8047"