End to End Unit Testing for Web Developers

Everyone knows theyre valuable, but writing unit tests for web applications can be a major pain in the butt. Few developers truly understand the many facets of unit testing, and choosing the right tools can be problematic in itself.

In this session, Arthur Kay will examine the various ways you can test an application and offer realistic suggestions on how to integrate unit tests into your project.

Transcript

1. END-TO-END UNIT TESTING FOR WEB DEVELOPERS Arthur Kay Sencha, Inc.
2. Who am I? Arthur Kay Solutions Engineer www.akaWebDesign.com @arthurakay
3. UNIT TESTS ARE HARD Common problems and what to do about them.
4. What do I test? • Structure •  Code itself • Logic •  Assertions • Presentation •  Behavior
5. What tools do I use? • Integration • Automation • Easy to install and maintain!
6. Reporting? • Pre-commit hooks •  Prevent mistakes • Continuous Integration •  Fail builds • (Q/A Process)
7. EXPECTATIONS Defining success.
8. Unit Tests Should… •  Prevent regressions •  Compliment greater testing process •  Imply functionality / intent •  Build confidence Should not… •  Imply no bugs exist •  Replace actual QA testing •  Test things at random •  Attempt 100% coverage
9. TOOLS AND EXAMPLES
10. Remember: •  Automation is required •  Solves a specific problem •  Feedback via reporting •  Not all tools integrate the same way! •  Sometimes you need to hack •  Document everything!
12. Unit Tests: Structure • Stable code across browsers • Maintain best practices • Monitor performance Tools: •  JSLint / JSHint •  LintRoller •  W3C Validator •  YSlow •  CSS Lint Automation: •  Node.js •  PhantomJS •  Ant •  CI servers (Travis)
13. Examples LintRoller YSlow
14. Unit Tests: Logic • Write testable code! • Few (or no) DOM dependencies • Models • Validations • Utilities Tools: •  Jasmine •  Siesta •  100 others Automation: •  Node.js •  PhantomJS •  Testacular •  Ant •  CI servers
15. Example Jasmine Testacular
16. Unit Tests: Presentation • Verify functionality or display • Components vs QA Tools: •  Testacular •  Siesta •  Selenium •  CasperJS Automation: •  CI servers •  PhantomJS •  Selenium RC
17. Examples Testacular Siesta
18. END-TO-END TESTING Doesn’t mean test everything!
19. Advice •  Pick your battles •  Weaknesses •  High-impact •  Some testing is better than no testing •  As long as it’s automated •  Remember the “unit” in “Unit Test” •  Solve specific problems •  Use the right tool •  “Set it and forget it”
20. SAMPLE APP - GITHUB https://github.com/arthurakay/CCC-EndToEndTest
21. Links •  For this presentation: •  https://speakerdeck.com/arthurakay •  http://spkr8.com/s/118941 •  https://github.com/arthurakay/ •  Sencha Webinar on Unit Testing: •  https://vimeo.com/58665998 •  Me: •  http://www.akawebdesign.com •  http://www.twitter.com/arthurakay
22. Review •  Unit Tests: •  Structure •  Logic •  Presentation •  Tests are SPECIFIC •  Tests must be AUTOMATED •  Tests need REPORTING
23. Fin