Intruducing a version test-case

[NobbZ]

In an exercise (http://exercism.io/submissions/05fb1f5acd00405aaa36844167c8d603) we assumed that an older test was used, and two of us thought it might be helpfull for thinks like this to have something that tells which version of the testsuite was used.

In the xruby path, there is one test in every suite which tests for the value of a constant of the module/class under test.

An example could be the following

-module(example_tests).

-define(TEST_VERSION, 1).

version_test() -> ?assertMatch(?TEST_VERSION, example:version()).

[kytrinyx]

We've got these in Go as well. It certainly helps people feel a little bit less miffed when the test suite changes out from under them.

[barberj]

@kytrinyx so is that an approval or does @tmcgilchrist need to weigh in?

[kytrinyx]

I approve in a generic sense. We need one of the people on the @exercism/erlang team to do the merge, though, since they know the specifics of the track.

[NobbZ]

Has this already been disussed in the @exercism/erlang team? This hasn't been touched for a month now.

[kytrinyx]

If nobody weighs in in the next 24 hours, I'll merge it.

[NobbZ]

There's nothing to merge ;) This shall just be a discussion about if we shall introduce some constant value into the testsuites that determine the suites version, as it is done in several other tracks (I know about xruby, you already mentioned xgo)

[kytrinyx]

Oh, right :)

[NobbZ]

Since I was promoted to a maintainer, I will take this one and will start to update the tests accordingly during the next two weeks while taking on #82 at the same time.

[tmcgilchrist]

Late to the party on this but this sounds like a good idea.