Ok ... today Justin pointed out my changes from yesterday caused tests to fail
I tried and had to agree with him ... the code was simply wrong. But I wrote
tests for it and when manually executing the tests in IntelliJ they failed.
As I did a full maven build with tests before committing and Jenkins also was
fine with my changes it seems that the current Junit 5 support is simply not
reliable.
I did see that there are now also options for running parametrized test without
some insane hackery, so I would also join your opinion that I think it's best
to switch to Junit 4
So I'll whip up a vote thread on this. Just that we get to vote a little more
here __
Chris
Am 26.01.18, 10:47 schrieb "Justin Mclean" <jus...@classsoftware.com>:
Hi,
> Well the one thing I like with TestNG is the support for parametrized
tests.
> With JUnit 4 this sucks greatly and it very easy with TestNG. I do think
that we need parametrized tests as we do have a lot of options to test.
There are some existing parametrised tests and I've used it in Junit4 (ages
ago) and don’t remember it being that bad, but I’ve not used that in TestNG so
perhaps it’s better there?
Thanks,
Justin
