documentation updates from atom-coderoad@0.11 & 0.12

ShMcK · ShMcK · commit 50a74131055c · 2016-08-16T18:01:05.000-07:00
diff --git a/_posts/tutorial-docs/2016-01-02-coderoad-api.md b/_posts/tutorial-docs/2016-01-02-coderoad-api.md
@@ -121,6 +121,27 @@ Add text to the bottom of the active text editor.
 ```))
 ```
 
+### write
+
+Write a file in the users project directory.
+File paths are relative to the users directory.
+
+```markdown
+@action(write('file.js', 'hello world!'))
+// writes to 'projectWorkingDirectory/file.js'
+```
+
+
+### writeFromFile
+
+Write a file to the users project directory by reading another file.
+
+```markdown
+@action(writeFromFile('file.js', 'data/example.js'))
+// reads from 'tutorial/data/example.js'
+// writes to 'projectWorkingDirectory/file.js'
+```
+
 #### ::>
 
 Set the cursor position.
diff --git a/_posts/tutorial-docs/2016-01-03-tests.md b/_posts/tutorial-docs/2016-01-03-tests.md
@@ -29,44 +29,3 @@ it('should be a function')
 it('must be a function')
 it('isn\'t a function')
 ```
-
-### Loaders
-
-Use a **loader** to run the user saved file in the context of your file. Think of a loader as a way to place the file your testing inside of your test file. Loaders are written as comments.
-
-```js
-/// load('user-file.js')
-```
-
-*Note: When using spies, stubs or mocks, initiate them above your loader call.*
-
-
-
-### Loading Data Files
-
-Data can be loaded in the user's file by loading it from your tutorial folder. Just call `load` with a second parameter, `true`.
-
-Although bad practice, it can be easiest to set data to the global scope.
-
-*path/to/tutorial/data/file.js
-
-```js
-var data = 42;
-```
-
-*test.spec.js*
-
-```
-/// load('data/file.js', true)
-/// load('user-file.js')
-
-/* tests here */
-```
-
-Users can access global data by name in their file.
-
-*user-file.js*
-
-```js
-var secret = data - 1;
-```
diff --git a/_posts/tutorial-docs/2016-01-09-test-runner.md b/_posts/tutorial-docs/2016-01-09-test-runner.md
@@ -14,7 +14,6 @@ In this way, the test runner not only determines how unit tests will be written,
 ### Current Test Runners
 
 * Javascript: [*mocha-coderoad*](//github.com/coderoad/mocha-coderoad)
-* Python: [*pytest-coderoad*](//github.com/coderoad/pytest-coderoad)
 
 We need more test runners. Why not build one?
 
