The document discusses testing JavaScript code. It covers why JavaScript is hard to test, how to make JavaScript more testable, and tools that can help with testing. Specifically, it notes that untestable JavaScript code is a major problem, provides examples of testable versus untestable code, and recommends using unit test frameworks like Jasmine along with functional test frameworks. It also recommends the sinon.js, ember-testing, and Karma tools to facilitate testing.

1. Testing JavaScript
© 2013 Eric Wendelin
@eriwen

2. Eric Wendelin
Blog: eriwen.com
Twitter: @eriwen
Code: git.io/eric

4. Today, we’ll talk about
• What makes JS testing hard
• A few ways we can make our JS more
testable
• Some tools that make testing easier

5. Why is testing your
JavaScript important?

6. The community is
behind in testing

7. Why is JavaScript so
hard to test?

12. Un-testable JS is
most of the problem

13. Don’t do this!
Do this!

14. Use with caution!
Better!

15. Don’t do this!
Do this!

16. Don’t do this!
Do this!

17. Don’t do this!
Do this!

18. Writing Tests

19. 1 unit test framework +
1 functional test framework
= Infinite Pocket Bacon

20. Logic / Computation
unit test

21. Computation Example

22. User Interaction
functional test

23. Interaction Example

24. sinon.js
sinonjs.org

28. sinon.js goodies
• Jasmine Adapter
• QUnit Adapter
• Mocha Adapter
• Buster.js Adapter
• Chai-specific matchers
• Jasmine matchers
• ... much more

29. ember-testing
/ember.js/packages/ember-testing

30. Karma
karma-runner.github.io

31. {F*** IT! WE’LL
DO IT LIVE!}

32. culture of testing

33. Code at: git.io/eric
Blog: eriwen.com
Twitter: @eriwen