Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide JUnit 5.8 test class orderer for efficient ordering of @TestProfile #20117

Closed
famod opened this issue Sep 13, 2021 · 1 comment · Fixed by #20156
Closed

Provide JUnit 5.8 test class orderer for efficient ordering of @TestProfile #20117

famod opened this issue Sep 13, 2021 · 1 comment · Fixed by #20156
Labels
area/testing kind/enhancement New feature or request
Milestone

Comments

@famod
Copy link
Member

famod commented Sep 13, 2021

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.

@famod famod added kind/enhancement New feature or request area/testing labels Sep 13, 2021
@quarkus-bot
Copy link

quarkus-bot bot commented Sep 13, 2021

You added a link to a Zulip discussion, please make sure the description of the issue is comprehensive and doesn't require accessing Zulip.

This message is automatically generated by a bot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/testing kind/enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants