Open*Atom-Coderoad* to view your tutorial. Your package should appear as a loaded package. Click on it.

Reload*Atom* to view changes. You can use the Atom[command-palette](https://atom.io/docs/latest/getting-started-atom-basics#command-palette) to find "reload" or simply use the reload hot-key.

* Windows & Linux: alt-ctrl-r

* Mac: ctrl-alt-cmd-l

Reload*Atom* to view changes. You can use the Atom[command-palette](https://atom.io/docs/latest/getting-started-atom-basics#command-palette) to find "reload" or simply use the reload hot-key (*Windows & Linux*: alt-ctrl-r,*Mac*: ctrl-alt-cmd-l).

}

`testDir` is appended to all@test calls, and`testSuffix` is added to the end.

`testDir` is appended to all*@test* calls, and`testSuffix` is added to the end.

*@test* loads a test file. It is important that these files are loaded in the correct order.*@test* can take a single test file, or an array of test files.

@test(['path/to/file', 'path/to/file2'])

The first example would load the file'./tutorial/path/to/file.spec.js' in the project root directory.

The first example would load the file*./tutorial/path/to/file.spec.js* in the project root directory.

See an[example](https://github.com/coderoad/coderoad-functional-school/blob/master/tutorial/1/01/filter.md) using*@test*.

file:2016-01-06-loaders.md

Tutorials may be written in different programming languages or for different compilers, so there isn't yet a standard way to load data from user created files. Instead, you'll have to load/transpile your files for the test runner. Rolling your own solution allows you to load data in a way that fits your project.

Tutorials may be written in different programming languages or for different compilers, so there isn't yet a standard way to load data from user created files. Instead, you'll have to load (and possiblytranspile) your files for the test runner. Rolling your own solution allows you to load data in a way that fits your project.

There may be a simpler approach in the future, but for now these snippets should help:

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.

* Add the contents of*snippets.cson* to your global*snippets.cson* file.

* Read the test runner README to see which snippets are available and which prefixes you should use.

For example, typing the snippet`mochacr-f` will generate an entire set of tests for a*mocha-coderoad* function. See an example:

Specified test runner. Currently only"mocha-coderoad" is available.

Specified test runner. Currently only*mocha-coderoad* is available.

* "name" - beginning with'coderoad-'

* "name" - beginning with*coderoad-*

* "description" - about your tutorial

* "author" or "authors" information

* "keywords" - about your tutorial

CodeRoad will become more flexible & powerful with time.

* Improved test coverage

* Lint for input errors before running (ESLint)

* Final Loader solution

* Improved animations

* Test Tools Snippets to generate common unit test configurations

* More test runners to support different programming languages (currently only Mocha test runner for JS)

*@continue for page completion actions

* cursor position option