roman-numerals: make test failures easier to troubleshoot

[jtigger]

roman-numerals uses the JUnit Parameterized test runner. This was done to make the test more compact (and once you learn how the mechanism works, easier to read).

However, when a test fails, the error message does not indicate which value failed. This makes it really difficult to know why the test failed.

Test failures should clearly indicate what failed.

To Do:

• ensure that this exercise is using JUnit 4.12 or later
• add a format string to the @Parameters annotation.

(ref: #147)

[stkent]

Related: exercism/problem-specifications#451

[bscharm]

@jtigger is a more "documentation style" description preferred? or a more sentence style description? e.g.:

@Parameters(name = "#getRomanNumeral() for RomanNumeral({0}) should return \"{1}\"")
translates to:
[#getRomanNumeral() for RomanNumeral(3) should return "III"]

vs.

@Parameters(name = "Roman Numeral representation of {0} is \"{1}\"")
translates to:
[Roman Numeral representation of 3 is "III"]

EDIT:
just saw @stkent comment...should descriptions indicate what the test is after as opposed to what it expects?

[jtigger]

Thanks for looking into this, @bscharm!

To your question: implementer's choice. Which would you find more useful as the practitioner running through the exercise?