test snippets docs

ShMcK · ShMcK · commit a8b34a549bbb · 2016-02-27T15:46:28.000-08:00
diff --git a/_posts/2016-01-07-test-snippets.md b/_posts/2016-01-07-test-snippets.md
@@ -0,0 +1,9 @@
+---
+layout: docs
+title: Test snippets
+id: test-snippets
+file: 2016-01-07-test-snippets.md
+---
+Test Runners may have pre-made [Atom snippets](https://atom.io/docs/latest/using-atom-snippets) to quickly generate test files. See [*mocha-coderoad* snippets](https://github.com/coderoad/mocha-coderoad/blob/master/snippets.cson) as an example.
+
+Open up *Atom* -> *Open Your Snippets*. Add the contents of `snippets.cson` to your global `snippets.cson` file. Read the project README to see which snippets are available and which prefixes you should use. For example: 'mochacr-f' for testing a "mocha-coderoad" function.
diff --git a/_posts/2016-01-08-test-examples.md b/_posts/2016-01-08-test-examples.md
@@ -2,7 +2,7 @@
 layout: docs
 title: Test Examples
 id: test-examples
-file: 2016-01-07-test-examples.md
+file: 2016-01-08-test-examples.md
 ---
 
 Here are examples using *mocha* with *chai*'s *expect*. See the [docs](http://chaijs.com/api/bdd/).
@@ -122,9 +122,3 @@ if (process.env.TASK_POSITION !== '4') {
 ```
 
 See a full [example](https://github.com/coderoad/coderoad-functional-school/blob/master/tutorial/1/04/01-forEach.spec.js).
-
-### Test Writing Tool
-
-It's entirely possible to create a simplified testing tool that could make writing tests faster & easier.
-
-The easiest solution would be to use editor snippets to generate a page of tests from a simple configuration object. This does not yet exist.
diff --git a/_posts/2016-01-09-config.md b/_posts/2016-01-09-config.md
@@ -2,7 +2,7 @@
 layout: docs
 title: Config
 id: config
-file: 2016-01-08-config.md
+file: 2016-01-09-config.md
 ---
 CodeRoad tutorial configurations can be set in the *package.json* config.
 
diff --git a/_posts/2016-01-10-publish.md b/_posts/2016-01-10-publish.md
@@ -2,7 +2,7 @@
 layout: docs
 title: Publishing
 id: publish
-file: 2016-01-09-publish.md
+file: 2016-01-10-publish.md
 ---
 Make sure your tutorial is ready and user tested before publishing to NPM.
 
diff --git a/_posts/2016-01-11-test-runner.md b/_posts/2016-01-11-test-runner.md
@@ -2,7 +2,7 @@
 layout: docs
 title: Test Runners
 id: test-runners
-file: 2016-01-10-test-runner.md
+file: 2016-01-11-test-runner.md
 ---
 A CodeRoad test runner works by creating a child process and calling a test framework with target files, then returning the result as a JSON object.
 
@@ -86,6 +86,6 @@ The result should output the *taskPosition* after the test. The field *change* r
 
 #### 4. handleLog
 
-A callback function that should return the output **log** statement. 
+A callback function that should return the output **log** statement.
 
 *If you need help setting up a new test runner, please send an email to coderoadapp@gmail.com.*
diff --git a/_posts/2016-01-12-roadmap.md b/_posts/2016-01-12-roadmap.md
@@ -2,7 +2,7 @@
 layout: docs
 title: Test Runners
 id: test-runners
-file: 2016-01-11-test-runner.md
+file: 2016-01-12-test-runner.md
 ---
 CodeRoad will become more flexible & powerful with time.
 
diff --git a/_posts/2016-01-13-contributing.md b/_posts/2016-01-13-contributing.md
@@ -2,7 +2,7 @@
 layout: docs
 title: Contributing
 id: contributing
-file: 2016-01-12-contributing.md
+file: 2016-01-13-contributing.md
 ---
 See our [development boards](https://coderoad.herokuapp.com/).
 
