Sha256: 19d878db58faa119f1a003e0980dc533d89c2bcb9c0c959ad1b659214ee64a04
Contents?: true
Size: 1.5 KB
Versions: 40
Compression:
Stored size: 1.5 KB
Contents
The Elm exercise test suites may be run from the exercise directory. ```bash $ cd ~/exercism/elm/hello-world $ elm test ``` ## Hints and tips ### Watch for changes Automatically run tests again when you save changes: ```bash $ elm test --watch ``` ### 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.
Version data entries
40 entries across 40 versions & 1 rubygems