Five Easy Ways to QA Your Drupal Site
Download as ZIP, PDF3 likes4,150 views
The document outlines five essential quality assurance techniques for website testing without requiring programming knowledge. Key steps include creating a test plan, utilizing automated testing tools, performing functional testing, and effectively tracking bugs through a systematic ticketing process. The emphasis is on thorough testing to ensure a reliable product delivery before client interaction.
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?
- 5. Create a test plan
- 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
- 11. Browser Testing
- 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.
- 18. Tickets
- 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