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
As Quarkus "reboots" for each different @TestProfile, much time might be wasted if you have x > 1 QuarkusTests without a profile and y QuarkusTests with a profile (or any similar combination).
JUnit 5.8 comes with a global test class ordering feature that could be very helpful, in that with such an orderer we could sort non profile QuarkusTests to the beginning and QuarkusTests with profiles after that, in alphabetical order of the FQCN of the profile class.
Description
As Quarkus "reboots" for each different
@TestProfile
, much time might be wasted if you have x > 1 QuarkusTests without a profile and y QuarkusTests with a profile (or any similar combination).JUnit 5.8 comes with a global test class ordering feature that could be very helpful, in that with such an orderer we could sort non profile QuarkusTests to the beginning and QuarkusTests with profiles after that, in alphabetical order of the FQCN of the profile class.
Implementation ideas
https://junit.org/junit5/docs/5.8.0/user-guide/index.html#writing-tests-test-execution-order-classes
As agreed on Zulip, this orderer shouldn't be registered automatically but should be documented instead.
Ideally, the orderer should be extendable easily so that users can add some custom ordering logic.
The text was updated successfully, but these errors were encountered: