Unit testing involves writing small tests for individual units or functions of an application to ensure they work as expected. Tests should be written from the start of a project to prevent bugs and regressions. Unit tests allow for collaborative work by different contributors, help automate catching errors, and produce more reliable code by testing features as they are developed. While unit testing requires upfront effort, it saves work in the long run by reducing unexpected bugs that would otherwise be found by users. The testing framework QUnit can be used to write unit tests in separate .js files and run them from an index.html page.

1. Unit Testing
jQuery Foundation Developer Summit 2015
@leobalter

2. Unit Testing is easy

3. Unit Testing is easy
if you test from day one.

4. Units
The very small parts of your app, like a
specific return on a simple function call.

5. Why Unit Tests?
• Collaborative work
• Automation
• Prevents regressions
• Reliable Code

6. Collaborative Work
Contributors do not know the whole API, and may
work on specific features only.

7. Automation
You can run the tests several times, in many
environments, on many machines, by any
developer

8. Prevents regressions
New features might break something else,
catch it while you can.

9. Reliable Code
Helps preventing lots of unexpected nightmares

10. Hard Work
Work hard, to work less later.

11. If you don’t test, users will.

12. QUnit

13. • test/index.html
• qunit.js
• qunit.css
• my_app.js
• test/my_tests.js

14. QUnit Example