Unit testing with Jasmine

 Your probably already doing it (debugging)
 Prevents regression/allows REFACTORING
 Fastest form of quality feedback
 Allows you to work on other peoples code
 Improves the design of your code
 Is a form of living documentation

 “The smallest testable part of an application”
 JavaScript public function === unit
 Utility Code
 Functional Code

 TDD – test driven development
 Write a test
 Run it (it’s red)
 Write some code
 Run it (it goes green)
 Repeat.

 Testing after the fact
 Boring
 Harder to write test code
 Tightly coupled test code
 Miss ‘conceptual’ errors

 Test during development
 New features ? Test driven development
 Bug fixes ? write tests for the unit
 Before refactor ? write tests before & modify

 Comprehensive suite of tests for your app
 Test lines ratio to code @3 : 1
 Run on every commit by CI
 ‘Stop the line’ when a test fails

 Behavior driven development (bdd)
 describe(”your module", function() {
it(”should be unit tested", function() {
expect(isUnitTested()).toBe(true);
});
});

Unit testing with Jasmine

More Related Content

What's hot (20)

Viewers also liked (6)

Similar to Unit testing with Jasmine (20)

Unit testing with Jasmine