SlideShare a Scribd company logo

Five Easy Ways to QA Your Drupal Site

•Download as ZIP, PDF•
•
Mediacurrent
Mediacurrent

The Five Easy Ways to QA Your Site has been presented at DrupalCamp South Florida as well as DrupalCamp Florida. The talk addresses the issue of using simple methods to add polish to your site through established Quality Assurance methods. During this presentation you'll learn quick and easy tasks as well as what tools to use to provide a high level of quality.

Related slideshows

Integration testing - A&BP CC
Integration testing - A&BP CCIntegration testing - A&BP CC
Integration testing - A&BP CC
 
Continuous Integration Testing in Django
Continuous Integration Testing in DjangoContinuous Integration Testing in Django
Continuous Integration Testing in Django
 
CI / CD w/ Codeception
CI / CD w/ CodeceptionCI / CD w/ Codeception
CI / CD w/ Codeception
 
1 of 21
Five Easy Ways to QA Your Site By Andrew M. Riley Mediacurrent Consultant @andrewmriley
Goal Introduce users to basic Quality Assurance techniques and tools. This talk will not involve programming in any way!
Goal You want to break your as much as possible so when you deliver your product you are confident that it will work in a specified manner. tl;dr: Break stuff before your client can.
Your Target • Who will be using your sites? • What browsers will you support? • What devices will you support?
Create a test plan
Test Plan • This is your guide follow it • Test case = test only one thing per test • Make a test case for everything (lots of them) • Record everything • This will grow over time • Keep it simple
Super Simple Example
Automated Tests Tools
Link Checkers • Integrity (OS X) - http://peacockmedia.co.uk/integrity/ • XENU (Windows) - http://home.snafu.de/tilman/xenulink.html
Spelling/HTML/Links • Total Validator - http://www.totalvalidator.com/ • HTML • CSS • Links • Spelling! • 508
Browser Testing
Manual • One test per page, per browser • Clear your cache, check your browser settings • Virtual Machines (VMs) help • Manually compare each page • Check Firebug/IE JS warnings
Automated • BrowserCam - http://www.browsercam.com/ • BrowserShots - http://browsershots.org/ • BrowserStack - http://www.browserstack.com/
IE VMs • Windows Users - http://j.mp/AlCgq2 • Not Windows Users - http://j.mp/zBpToY
Functional Testing
Functional Tests Create your test cases from your specifications documents or contract. If you don’t have these documents, you’ll have to go through your site manually and look for things to break.
Functional Tests • Break it down to the smallest element • Can be done in one browser* • Remember negative test cases • Check your Drupal watchdog/logs • Think outside the box.
Tickets
Track Everything 1. Error on the side of creating too many tickets 2. One ticket per bug, one bug per ticket 3. Use a tracking system (it can be free) 4. Describe the issue, take a screenshot or video. 5. Include a link and include any data
Too Much Work While this feels like a lot of work it can make the difference between a launch and a polished launch.
Five Easy Ways to QA Your Site http://j.mp/pJ2JIj By Andrew M. Riley Mediacurrent Consultant @andrewmriley

More Related Content

Five Easy Ways to QA Your Drupal Site

  • 1. Five Easy Ways to QA Your Site By Andrew M. Riley Mediacurrent Consultant @andrewmriley
  • 2. Goal Introduce users to basic Quality Assurance techniques and tools. This talk will not involve programming in any way!
  • 3. Goal You want to break your as much as possible so when you deliver your product you are confident that it will work in a specified manner. tl;dr: Break stuff before your client can.
  • 4. Your Target • Who will be using your sites? • What browsers will you support? • What devices will you support?
  • 6. Test Plan • This is your guide follow it • Test case = test only one thing per test • Make a test case for everything (lots of them) • Record everything • This will grow over time • Keep it simple
  • 9. Link Checkers • Integrity (OS X) - http://peacockmedia.co.uk/integrity/ • XENU (Windows) - http://home.snafu.de/tilman/xenulink.html
  • 10. Spelling/HTML/Links • Total Validator - http://www.totalvalidator.com/ • HTML • CSS • Links • Spelling! • 508
  • 12. Manual • One test per page, per browser • Clear your cache, check your browser settings • Virtual Machines (VMs) help • Manually compare each page • Check Firebug/IE JS warnings
  • 13. Automated • BrowserCam - http://www.browsercam.com/ • BrowserShots - http://browsershots.org/ • BrowserStack - http://www.browserstack.com/
  • 14. IE VMs • Windows Users - http://j.mp/AlCgq2 • Not Windows Users - http://j.mp/zBpToY
  • 16. Functional Tests Create your test cases from your specifications documents or contract. If you don’t have these documents, you’ll have to go through your site manually and look for things to break.
  • 17. Functional Tests • Break it down to the smallest element • Can be done in one browser* • Remember negative test cases • Check your Drupal watchdog/logs • Think outside the box.
  • 19. Track Everything 1. Error on the side of creating too many tickets 2. One ticket per bug, one bug per ticket 3. Use a tracking system (it can be free) 4. Describe the issue, take a screenshot or video. 5. Include a link and include any data
  • 20. Too Much Work While this feels like a lot of work it can make the difference between a launch and a polished launch.
  • 21. Five Easy Ways to QA Your Site http://j.mp/pJ2JIj By Andrew M. Riley Mediacurrent Consultant @andrewmriley

Editor's Notes

  1. \n
  2. \n
  3. \n
  4. \n
  5. \n
  6. \n
  7. \n
  8. \n
  9. \n
  10. \n
  11. \n
  12. \n
  13. \n
  14. \n
  15. \n
  16. \n
  17. \n
  18. \n
  19. \n
  20. \n
  21. \n