diff --git a/chapters/testing/images/nodeunit_failing_all.png b/chapters/testing/images/nodeunit_failing_all.png
new file mode 100644
index 0000000..6890a2d
Binary files /dev/null and b/chapters/testing/images/nodeunit_failing_all.png differ
diff --git a/chapters/testing/images/nodeunit_failing_better.png b/chapters/testing/images/nodeunit_failing_better.png
new file mode 100644
index 0000000..c112de5
Binary files /dev/null and b/chapters/testing/images/nodeunit_failing_better.png differ
diff --git a/chapters/testing/images/nodeunit_passing.png b/chapters/testing/images/nodeunit_passing.png
new file mode 100644
index 0000000..d1759f6
Binary files /dev/null and b/chapters/testing/images/nodeunit_passing.png differ
diff --git a/chapters/testing/testing_with_nodeunit.md b/chapters/testing/testing_with_nodeunit.md
new file mode 100644
index 0000000..ecdd5e9
--- /dev/null
+++ b/chapters/testing/testing_with_nodeunit.md
@@ -0,0 +1,172 @@
+---
+layout: recipe
+title: Testing with Nodeunit
+chapter: Testing
+---
+## Problem
+
+You are writing a simple calculator using CoffeeScript and you want to verify it functions as expected.  You decide to use the <a href="https://github.com/caolan/nodeunit" target="_blank">Nodeunit</a> test framework.
+
+## Discussion
+
+Nodeunit is a JavaScript implementation of the xUnit family of Unit Testing libraries, similar libraries are available for Java, Python, Ruby, Smalltalk etc.
+
+When using xUnit family test frameworks, you write tests in a file that describes the expected functionality of the code to be tested.
+
+For example, we expect our calculator will be able to add and subtract and will function correctly with both positive and negative numbers.  Our test is listed below.
+
+{% highlight coffeescript %}
+
+# tests/calculator.test.coffee
+
+Calculator = require '../calculator'
+
+exports.CalculatorTest =
+
+    'test can add two positive numbers': (test) ->
+        calculator = new Calculator
+        result = calculator.add 2, 3
+        test.equal(result, 5)
+        test.done()
+
+    'test can handle negative number addition': (test) ->
+        calculator = new Calculator
+        result = calculator.add -10, 5
+        test.equal(result,  -5)
+        test.done()
+
+    'test can subtract two positive numbers': (test) ->
+        calculator = new Calculator
+        result = calculator.subtract 10, 6
+        test.equal(result, 4)
+        test.done()
+
+    'test can handle negative number subtraction': (test) ->
+        calculator = new Calculator
+        result = calculator.subtract 4, -6
+        test.equal(result, 10)
+        test.done()
+
+{% endhighlight %}
+
+### Installing Nodeunit
+
+Before you can run your tests, you must install Nodeunit:
+
+First of allcreate a package.json file
+
+{% highlight javascript %}
+{
+  "name": "calculator",
+  "version": "0.0.1",
+  "scripts": {
+    "test": "./node_modules/.bin/nodeunit test"
+  },
+  "dependencies": {
+    "coffee-script": "~1.4.0",
+    "nodeunit": "~0.7.4"
+  }
+}
+{% endhighlight %}
+
+Next from a terminal run.
+
+{% highlight bash %}
+$ npm install
+{% endhighlight %}
+
+## <span style="color: red;">Running the Tests</span>
+
+It's easy to run the tests from the command-line:
+
+{% highlight bash %}
+$ npm test
+{% endhighlight %}
+
+The test runner should fail, because we have no calculator.coffee
+
+<img src="images/nodeunit_failing_all.png" alt="All failing tests" />
+
+Let's create a simple file 
+
+
+{% highlight coffeescript %}
+
+# calculator.coffee
+
+class Calculator
+
+module.exports = Calculator
+{% endhighlight %}
+
+And re-run the test suite.
+
+<img src="images/nodeunit_failing_better.png" alt="Still failing, but better" />
+
+## <span style="color: green;">Getting the Tests to Pass</span>
+
+Let's implement our methods and see if we can get these tests to pass.
+
+{% highlight coffeescript %}
+
+# calculator.coffee
+
+class Calculator
+
+  add: (a, b) ->
+    a + b
+
+  subtract: (a, b) ->
+    a - b
+
+module.exports = Calculator
+{% endhighlight %}
+
+When we rerun the tests we see they're all passing:
+
+<img src="images/nodeunit_passing.png" alt="All passing" />
+
+
+## <span style="color: green;">Refactoring the Tests</span>
+
+Now that our tests pass, we should look to see if our code or our test(s) can be refactored.
+
+In our test file, each test creates its own calculator instance.  This can make our tests quite repetitive especially for larger test suites.  Ideally, we should consider moving that initialization code into a routine that runs before each test.  
+
+In common with other xUnit libraries, Nodeunit provides a setUp (and tearDown) function which will be called before each test.
+
+{% highlight coffeescript %}
+
+Calculator = require '../calculator'
+
+exports.CalculatorTest =
+
+    setUp: (callback) ->
+        @calculator = new Calculator
+        callback()
+
+    'test can add two positive numbers': (test) ->
+        result = @calculator.add 2, 3
+        test.equal(result, 5)
+        test.done()
+
+    'test can handle negative number addition': (test) ->
+        result = @calculator.add -10, 5
+        test.equal(result,  -5)
+        test.done()
+
+    'test can subtract two positive numbers': (test) ->
+        result = @calculator.subtract 10, 6
+        test.equal(result, 4)
+        test.done()
+
+    'test can handle negative number subtraction': (test) ->
+        result = @calculator.subtract 4, -6
+        test.equal(result, 10)
+        test.done()
+
+{% endhighlight %}
+
+We can rerun the tests and everything should continue to pass.
+
+<img src="images/nodeunit_passing.png" alt="All passing" />