Sha256: 20d21edf17ba3c1b15882e17aac19884f6b9ddd9db2a1294729c81d36294325f
Contents?: true
Size: 1.48 KB
Versions: 68
Compression:
Stored size: 1.48 KB
Contents
# {{ .Spec.Name }}
{{ .Spec.Description -}}
{{- with .Hints }}
{{ . }}
{{ end }}
## 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
It's possible to submit an incomplete solution so you can see how others have completed the exercise.
Version data entries
68 entries across 68 versions & 1 rubygems