tracks/erlang/config/exercise_readme.go.tmpl in trackler-2.2.1.110 vs tracks/erlang/config/exercise_readme.go.tmpl in trackler-2.2.1.111

- old
+ new

@@ -2,13 +2,51 @@ {{ .Spec.Description -}} {{- with .Hints }} {{ . }} {{ end }} -{{- with .TrackInsert }} -{{ . }} -{{ end }} -{{- with .Spec.Credits -}} +## Running tests + +In order to run the tests, issue the following command from the exercise +directory: + +For running the tests provided, `rebar3` is used as it is the official build and +dependency management tool for erlang now. Please refer to [the tracks installation +instructions](http://exercism.io/languages/erlang/installation) on how to do that. + +In order to run the tests, you can issue the following command from the exercise +directory. + +```bash +$ rebar3 eunit +``` + +### Test versioning + +Each problem defines a macro `TEST_VERSION` in the test file and +verifies that the solution defines and exports a function `test_version` +returning that same value. + +To make tests pass, add the following to your solution: + +```erlang +-export([test_version/0]). + +test_version() -> + 1. +``` + +The benefit of this is that reviewers can see against which test version +an iteration was written if, for example, a previously posted solution +does not solve the current problem or passes current tests. + +## Questions? + +For detailed information about the Erlang track, please refer to the +[help page](http://exercism.io/languages/erlang) on the Exercism site. +This covers the basic information on setting up the development +environment expected by the exercises. +{{ with .Spec.Credits }} ## Source {{ . }} {{ end }} ## Submitting Incomplete Solutions