I think as the discussion moved from the unit-test framework to the framework
we create the assertions with, this deserves a dedicated discussion.
I think the options on the table are currently: JUnits on-board Assertions,
AssertJ or Hamcrest.
I too am not very fond of the ordinary Junit assertions and I’ll add Niclas’
very helpful input to the topic.
Even if I like the way AssertJ handles exceptions a bit more than the Hamcrest
way, I never was particularly fond of never-ending fluent expressions. So I
would opt for the Hamcrest version.
What do you think?
Here’s the link to Niclas’ changeset again: