```))

Write a file in the users project directory.

File paths are relative to the users directory.

@action(write('file.js', 'hello world!'))

// writes to 'projectWorkingDirectory/file.js'

Write a file to the users project directory by reading another file.

@action(writeFromFile('file.js', 'data/example.js'))

// reads from 'tutorial/data/example.js'

// writes to 'projectWorkingDirectory/file.js'

Set the cursor position.

it('must be a function')

it('isn\'t a function')

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.

*Note: When using spies, stubs or mocks, initiate them above your loader call.*

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

var data=42;

*test.spec.js*

Users can access global data by name in their file.

*user-file.js*

var secret= data-1;

* #"diff-3f0a052b44acfd92a825dcef177c9f9bfadf3f9cf904f3d94c2418a8a4fd7a47-17-16-0" data-selected="false" role="gridcell" tabindex="-1" valign="top">17

* Python:[*pytest-coderoad*](//github.com/coderoad/pytest-coderoad)

We need more test runners. Why not build one?