-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Integrate @ShouldPin/@ShouldNotPin into QuarkusTests #35992
Conversation
🙈 The PR is closed and the preview is expired. |
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great stuff!
Do not merge, we are still discussing if it should be in-quarkus or outside. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It works well!
At first the name of the module confused me as it doesn't do anything related to junit5, but then I saw the lifecycle callbacks were from quarkus-junit5.
We can migrate pinning-test executions under integration-tests/virtual-threads
to this.
...it5-virtual-threads/src/main/java/io/quarkus/test/junit/virtual/internal/InternalEvents.java
Outdated
Show resolved
Hide resolved
9c30a25
to
b52bc97
Compare
After discussion, we decided to move the junit5 extension under independent projects, to allow other projects to use it. The functionality is not Quarkus-specific. The PR has been updated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍🏼
This commit brings the functionality from loom-unit (partially, but the important ones are there) into Quarkus. Thus, @ShouldPin and @ShouldNotPin can be used on a @QuarkusTest directly as soon as the junit5-virtual-threads dependency is in the project and the extension declared on the test case with the `io.quarkus.test.junit5.virtual.VirtualThreadUnit` annotation. loom-unit original repo: https://github.com/cescoffier/loom-unit
b52bc97
to
8d80397
Compare
✔️ The latest workflow run for the pull request has completed successfully. It should be safe to merge provided you have a look at the other checks in the summary. |
This PR brings the functionality from loom-unit (partially, but the important ones are there) into Quarkus.
Thus, @ShouldPin and @ShouldNotPin can be used on a @QuarkusTest directly as soon as the quarkus-junit5-virtual-threads dependency is in the project.
loom-unit original repo: https://github.com/cescoffier/loom-unit