Unit testing with Jasmine
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
781
On Slideshare
597
From Embeds
184
Number of Embeds
1

Actions

Shares
Downloads
3
Comments
0
Likes
0

Embeds 184

http://www.trisis.co.uk 184

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Unit testing with
  • 2.  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
  • 3.  “The smallest testable part of an application”  JavaScript public function === unit Utility Code Functional Code
  • 4. Practical
  • 5.  TDD – test driven development  Write a test  Run it (it’s red)  Write some code  Run it (it goes green)  Repeat.
  • 6.  Testing after the fact  Boring  Harder to write test code  Tightly coupled test code  Miss ‘conceptual’ errors
  • 7.  Test during development  New features ? Test driven development  Bug fixes ? write tests for the unit  Before refactor ? write tests before & modify
  • 8.  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
  • 9.  Behavior driven development (bdd)  describe(”your module", function() { it(”should be unit tested", function() { expect(isUnitTested()).toBe(true); }); });