POC : Use @TableTest in a Raptor unit test to improve readability

[t2gran]

Summary

This is a POC to demonstrate TableTest in OTP. We can discuss if this is something we want to use in a dev meeting.

The TableTest is written by a colleague of mine in Scienta. The TableTest is inspired by the Spock framework.

Pros

• More readable tests. Most of the "ugly looking" @ParameterizedTest can be replaced by @TableTest

Cons

• Depend on a small utility with limited support

There is a IntelliJ plugin witch must be installed to get syntax highlighting and editing support for the tables.

In IntelliJ the test will look like this:

The custom parsing of the int values is achieved by adding a @FactorySource to the class:

@FactorySources(TableTestValueParser.class)
public class TestTripScheduleSearchTest implements RaptorTestConstants {

Issue

• This improve unit tests, no issue.

Unit tests

Improve

Documentation

JavaDoc added

Changelog

Not relevant

Bumping the serialization version id

Not needed