You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to move all tests to JUnit 5 and maybe we can also use testcontainers to start containers on demand instead of using docker-compose on Travis.
The text was updated successfully, but these errors were encountered:
ok, I'll do an initial PR to migrate the majority of the tests.
Is there a restriction on using java 1.7? To migrate P6TestOptionsRepository I'd like to use lambdas (assertThrows).
The parameterised tests are not really going to be able to be migrated in their current form, afaik. It would be certainly rather ugly, at least -- the JUnit5-Parameterized is just too different. The test-setup in the base-class would have to be completely different. Therefore I think it would be just as good to leave those tests on JUnit-4 for the time being.
rjo67
added a commit
to rjo67/p6spy
that referenced
this issue
Apr 18, 2021
It would be nice to move all tests to JUnit 5 and maybe we can also use testcontainers to start containers on demand instead of using docker-compose on Travis.
The text was updated successfully, but these errors were encountered: