Add previous/next links to documentation files

Author: randycoulman

docs/1-installation.md

@@ -100,3 +100,6 @@ QUnit.testDone(function() {
   td.reset()
 })
 ```
+
+***
+Next:  [Purpose](2-howto-purpose.md)

docs/2-howto-purpose.md

@@ -109,3 +109,7 @@ in adapter functions to fake those adapters instead of the 3rd-party API—this
 will decrease the degree to which test doubles will leak throughout the
 integrated test suite and afford some opportunity for responding to hard-to-test
 situations by improving the API design of your adapters.
+
+***
+Previous: [Installing testdouble.js](1-installation.md)
+Next:  [Getting Started](3-getting-started.md)

docs/3-getting-started.md

@@ -354,3 +354,7 @@ Further reading that documents the features shown off in this tutorial include:
 * [Creating test doubles with `function()` and `object()`](4-creating-test-doubles.md)
 * [Stubbing responses with `when()`](5-stubbing-results.md)
 * [Verifying invocations with `verify()`](6-verifying-invocations.md)
+
+***
+Previous: [Purpose](2-howto-purpose.md)
+Next: [Creating Test Doubles](4-creating-test-doubles.md)

docs/4-creating-test-doubles.md

@@ -223,3 +223,7 @@ FakeCat.prototype.scratch // a test double function named '#scratch'
 ## Conclusion
 
 As you can see, there are a plethora of ways to create test doubles with testdouble.js, each designed to handle a different style of organizing JavaScript code. We recommend on landing on one consistent style (e.g. each module as one function) for each project, which in turn would encourage one consistent style of creating test doubles. This API is written to be flexible for a number of potential contexts across objects, but it has come at the cost of a large enough surface area that if any project were to make ample use of all or most of the above invocation styles, it would confuse readers.
+
+***
+Previous: [Getting Started](3-getting-started.md)
+Next: [Stubbing behavior](5-stubbing-results.md)

docs/5-stubbing-results.md

@@ -622,3 +622,7 @@ other major feature of any test double library—verifying an invocation took
 place—has an API that was carefully-designed to be completely symmetrical! Read
 on about [verifying interactions with `verify()`](6-verifying-invocations.md),
 and rest easy knowing that you already know exactly how to do it.
+
+***
+Previous: [Creating Test Doubles](4-creating-test-doubles.md)
+Next: [Verifying interactions](6-verifying-invocations.md)

docs/6-verifying-invocations.md

@@ -373,3 +373,7 @@ td.verify(doNotCall(), {times: 0, ignoreExtraArgs: true}) // passes
 And that's everything there is to know about verifying behavior with
 testdouble.js! At this point, you know everything you need to know to be pretty
 dangerous writing isolated tests.
+
+***
+Previous: [Stubbing behavior](5-stubbing-results.md)
+Next: [Replacing Real Dependencies with Test Doubles](7-replacing-dependencies.md)

docs/7-replacing-dependencies.md

@@ -228,4 +228,6 @@ path shouldn't exist yet, a second argument `manualReplacement` can be provided
 to short-circuit any attempts to load and imitate a module at
 `relativePathToModule`.
 
-
+***
+Previous: [Verifying interactions](6-verifying-invocations.md)
+Next: [Custom argument matchers](8-custom-matchers.md)

docs/8-custom-matchers.md

@@ -64,3 +64,7 @@ opportunity to mutate the matcher instance or have some other side effect. The
 
 For some examples of `td.matchers.create()` in action, check out the
 [built-in matchers](src/matchers/index.coffee) provided by testdouble.js.
+
+***
+Previous: [Replacing Real Dependencies with Test Doubles](7-replacing-dependencies.md)
+Next: [Debugging with testdouble.js](9-debugging.md)

docs/9-debugging.md

@@ -79,4 +79,6 @@ If you'd like to make `explain()` even better, consider sending a pull request
 to make [`explain` describe test double objects](https://github.com/testdouble/testdouble.js/issues/48)
 in addition to functions.
 
-
+***
+Previous: [Custom argument matchers](8-custom-matchers.md)
+Next: [Plugins](A-plugins.md)

docs/A-plugins.md

@@ -46,3 +46,7 @@ testing that a component debounces user input).
 This API has been ported for use with testdouble.js by
 [@kuy](https://github.com/kuy) as
 [testdouble-timers](https://github.com/kuy/testdouble-timers).
+
+***
+Previous: [Debugging with testdouble.js](9-debugging.md)
+Next: [Frequently Asked Questions](B-frequently-asked-questions.md)