elm/docs/TESTS.md

Elm exercises within your exercism project directory can be run by changing to the exercise directory, and running `elm-test NameOfTests.elm`.

```bash
$ cd exercism/project/directory/elm/hello-world
$ elm-test HelloWorldTests.elm
```

When you first run `elm-test` for an exercise it will prompt you to install the test library dependencies. If you type "y" and hit enter, the script should take care of the rest.

## Hints and tips

### Coding the exercise

The README.md for each exercise gives a general description but the Elm test program will be very specific. Open the test program and give it a quick look - if it seems like cheating, do it anyway. Look for helpful comments, test data, and just the names of the test functions. Try running the test command before you have written anything and see if the error messages give you an idea of where to start.

Your first goal it to get something to compile, even though it fails tests. For this, you should "stub" functions. That means leave the body empty, except for whatever it must return. Write something like `myFunc param = 0` or whatever it takes just to get it to compile. Sometimes to figure out function types you will have to go back to the test program and read in more detail. Once you have figured out all the required function signatures, the test program will complain that `0` is the wrong answer. Now start filling in function bodies.

### Fixing

It will often be helpful to focus on the first failing test. Fix that one, repeat until no errors. Compile errors and warnings will produce lots of helpful output.

### Cleaning up your code

Consider running [`elm-format`](https://github.com/avh4/elm-format) on your code before submitting it.
Update docs and hello-world to reflect exercise specific elm-package.json files. 2016-03-13 18:29:54 +00:00			Elm exercises within your exercism project directory can be run by changing to the exercise directory, and running `elm-test NameOfTests.elm`.

Add docs in support of x-api v3 2015-11-25 16:24:04 +00:00			```bash
Update docs and hello-world to reflect exercise specific elm-package.json files. 2016-03-13 18:29:54 +00:00			`$ cd exercism/project/directory/elm/hello-world`
			`$ elm-test HelloWorldTests.elm`
Add docs in support of x-api v3 2015-11-25 16:24:04 +00:00			```

Update docs and hello-world to reflect exercise specific elm-package.json files. 2016-03-13 18:29:54 +00:00			When you first run `elm-test` for an exercise it will prompt you to install the test library dependencies. If you type "y" and hit enter, the script should take care of the rest.
Add docs in support of x-api v3 2015-11-25 16:24:04 +00:00
Update docs and hello-world to reflect exercise specific elm-package.json files. 2016-03-13 18:29:54 +00:00			`## Hints and tips`
Add docs in support of x-api v3 2015-11-25 16:24:04 +00:00
Update docs and hello-world to reflect exercise specific elm-package.json files. 2016-03-13 18:29:54 +00:00			`### Coding the exercise`
Add docs in support of x-api v3 2015-11-25 16:24:04 +00:00
Update docs and hello-world to reflect exercise specific elm-package.json files. 2016-03-13 18:29:54 +00:00			`The README.md for each exercise gives a general description but the Elm test program will be very specific. Open the test program and give it a quick look - if it seems like cheating, do it anyway. Look for helpful comments, test data, and just the names of the test functions. Try running the test command before you have written anything and see if the error messages give you an idea of where to start.`

			Your first goal it to get something to compile, even though it fails tests. For this, you should "stub" functions. That means leave the body empty, except for whatever it must return. Write something like `myFunc param = 0` or whatever it takes just to get it to compile. Sometimes to figure out function types you will have to go back to the test program and read in more detail. Once you have figured out all the required function signatures, the test program will complain that `0` is the wrong answer. Now start filling in function bodies.

			`### Fixing`

			`It will often be helpful to focus on the first failing test. Fix that one, repeat until no errors. Compile errors and warnings will produce lots of helpful output.`

			`### Cleaning up your code`

			Consider running [`elm-format`](https://github.com/avh4/elm-format) on your code before submitting it.