Version 5 has some drawbacks but on the positive side, APIs like assertThrows are very useful.
Gary On Sun, Oct 23, 2022, 04:31 Michael Osipov <micha...@apache.org> wrote: > Am 2022-10-22 um 17:14 schrieb Oleg Kalnichevski: > > The JUnit 5 upgrade was a <self censored> cluster<self censored>. > > > > The original contributor ported some of the easy test cases that did > > not have a complex resource setup and left most complex and most > > important protocol and integration tests still partially using JUnit 4 > > features through the JUnit 5 migration layer. I cannot blaim him. JUnit > > 5 after so many years still have no reasonable way of parameterizing > > test cases through constructors. What the original contributor did not > > do (by mistake or by oversight) is activating the vintage JUnit support > > for Maven Surefire plugin. > > > > As a result we have been running CI of the 5.2 code _without_ > > integration tests for a _whole_ <self censored> year (since Nov 2021). > > That is really sad. I have also noticed that people uprading these days > for the sake of upgrading instead of real improvements. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org > For additional commands, e-mail: dev-h...@hc.apache.org > >
