Testing/Standaard checklist

2Value vraagt klanten om mee te denken over de testen waaraan het op te leveren systeem moet voldoen.

Komen klanten na ons verzoek niet met een lijst van testonderdelen, dan hanteert 2Value een eigen standaard checklist. Om de kwaliteit van het geleverde te waarborgen.

De rol van Tester en Developer zijn gescheiden. Hoe de verantwoordelijkheden liggen staat hier beschreven. Hoe er na de (oplever)test met de resultaten wordt omgegaan komt in de Evaluatie ter sprake.

Onderdelen van test

Onze standaard checklist heeft een of meer van de volgende onderdelen afhankelijk van de opdracht en de fase waarin de ontwikkeling of de support zich bevindt.

Benadering

Testen kunnen over verschillende gebieden worden uitgevoerd. Verder kun je per gebied zeer grondig te werk gaan. Dit ligt niet altijd binnen de budgettaire mogelijkheden of het risico van gebreken is te laag om hoge uitgaven te verantwoorden. We maken onderscheid en laten de klant kiezen:

1. Basic standard checklist
2. Medium standard checklist
3. Pro standard checklist

Basic

2Value doet bij een standaard checklist "Basic" aan cherry picking: hoe kunnen we gemakkelijk en snel belangrijke in het oog lopende dingen testen? Als de klant zelf niks kan verzinnen, pakken we zelf een de minimale testinspanning die wel de must haves redelijkerwijs allemaal eruit haalt.

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

Level basic is minimum dat ie terug geeft

Medium

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. Check for incorrect punctuation marks, particularly apostrophes, quotation marks and hyphens/dashes
   2. Check headings for where you could potentially use ligatures
   3. Check for widow/orphan terms in important paragraphs
2. Spelling and grammar#Consistency
   1. Capitalisation (especially of main headings)
   2. Tense/Style of writing
   3. Recurring/common phrases (e.g. ‘More about X’ links)
   4. Variations in words (e.g. Websites vs Web Sites, or UK vs US spelling)
   5. Treatment of bulleted lists (e.g. periods or commas at end of each item)
3. Check for hard-coded links to staging domain (i.e. ensure all links will change to ‘live’ URL/domain when site is launched)
4. Ensure no test content on site

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

Search Engine Visibility, SEO and Metrics

1. Page Titles are important; ensure they make sense and have relevant keywords in them.
2. Create metadata descriptions for important pages.
3. 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)
4. Ensure content is marked-up semantically/correctly (HTML-tags, etc.)
5. Check for target keyword usage in general content
6. Check format (user/search engine friendliness) of URLs
7. Set up Analytics, FeedBurner, and any other packages for measuring ongoing succes
   -> http://www.google.com/analytics (use twovalue@gmail.com as username. See http://service.2value.nl for password)
8. Create an XML Sitemap
   -> consider the Joomla! extension Xmap
9. Configure Google Webmaster Console and Yahoo! Site Explorer
   -> http://www.google.com/webmasters/tools (use twovalue@gmail.com as username. See http://service.2value.nl for password)

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

Security/Risk

1. Configure backup schedule, and test recovery from backup.
2. Protect any sensitive pages (e.g. administration area)

Performance

1. Load test
2. Check image optimisation
   -> All Smush.it
3. Check and implement caching where necessary
   -> NoNumber Cache Cleaner
4. Check total page size/download time
   -> Firefox plugin Yslow

Finishing Touches

1. Create a favicon
2. Create custom 404/error pages
   -> consider the Joomla! extension Dynamic404

Joomla! specific

1. Remove testcontent from configuration.php

For an updated list check -> http://www.boxuk.com/blog/the-ultimate-website-launch-checklist

Level basic is minimum dat ie terug geeft

Pro

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. Check for incorrect punctuation marks, particularly apostrophes, quotation marks and hyphens/dashes
   2. Check headings for where you could potentially use ligatures
   3. Check for widow/orphan terms in important paragraphs
2. Spelling and grammar#Consistency
   1. Capitalisation (especially of main headings)
   2. Tense/Style of writing
   3. Recurring/common phrases (e.g. ‘More about X’ links)
   4. Variations in words (e.g. Websites vs Web Sites, or UK vs US spelling)
   5. Treatment of bulleted lists (e.g. periods or commas at end of each item)
3. Check for hard-coded links to staging domain (i.e. ensure all links will change to ‘live’ URL/domain when site is launched)
4. Ensure no test content on site
5. Check how important pages (e.g. content items) print
6. For re-designs, ensure important old/existing URLs are redirected to relevant new URLs, if the URL scheme is changing
7. Check all ‘Hidden Copy’ (e.g. alt text, transcriptions, text in JavaScript functions)

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

Search Engine Visibility, SEO and Metrics

1. Page Titles are important; ensure they make sense and have relevant keywords in them.
2. Create metadata descriptions for important pages.
3. 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)
4. Ensure content is marked-up semantically/correctly (HTML-tags, etc.)
5. Check for target keyword usage in general content
6. Check format (user/search engine friendliness) of URLs
7. Set up Analytics, FeedBurner, and any other packages for measuring ongoing succes
   -> http://www.google.com/analytics (use twovalue@gmail.com as username. See http://service.2value.nl for password)
8. Create an XML Sitemap
   -> consider the Joomla! extension Xmap
9. Configure Google Webmaster Console and Yahoo! Site Explorer
   -> http://www.google.com/webmasters/tools (use twovalue@gmail.com as username. See http://service.2value.nl for password)

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

Security/Risk

1. Configure backup schedule, and test recovery from backup.
2. Protect any sensitive pages (e.g. administration area)
3. Use robots.txt where necessary
4. Security/Penetration test
5. Turn-off verbose error reporting
6. Check disk space/capacity
7. Set-up email/SMS monitoring/alerts (e.g. for errors, server warnings); consider internal and external monitoring services

Performance

1. Load test
2. Check image optimisation
   -> All Smush.it
3. Check and implement caching where necessary
   -> NoNumber Cache Cleaner
4. Check total page size/download time
   -> Firefox plugin Yslow
5. Minify/compress static (JavaScript/HTML/CSS) files
   -> use compress plugins
6. Optimise your CSS: use short image paths; make full-use ‘cascading’ nature of CSS, etc.
   -> use compress plugins
7. Check correct database indexing
8. Check configuration at every level (Web server, Database, any other software e.g. Content Management System)
9. Configure server-based logging/measurement tools (e.g. database/web server logging)
10. Lees meer hierover in de SlideShare presentatie van Hans Kuijpers over Site Performance Optimization

Finishing Touches

1. Create a favicon
2. Create custom 404/error pages
   -> consider the Joomla! extension Dynamic404

Joomla! specific

1. Remove testcontent from configuration.php

Post-Launch

Marketing

1. Social Marketing: Twitter, LinkedIn, Digg, Facebook, Stumbleupon, etc.
2. Submit to search engines
3. Set-up PPC/Google Adwords where necessary
4. Check formatting of site results in SERPs

Ongoing

1. Monitor and respond to feedback (direct feedback, on Social Media sites, check for chatter through Google, etc.)
2. Check analytics for problems, popular pages etc. and adjust as necessary
3. Update contentFor an updated list check -> http://www.boxuk.com/blog/the-ultimate-website-launch-checklist

Level basic is minimum dat ie terug geeft