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

Integrate @ShouldPin/@ShouldNotPin into QuarkusTests #35992

Merged
merged 1 commit into from
Sep 21, 2023

Conversation

cescoffier
Copy link
Member

@cescoffier cescoffier commented Sep 18, 2023

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

@quarkus-bot quarkus-bot bot added area/dependencies Pull requests that update a dependency file area/documentation area/testing labels Sep 18, 2023
@github-actions
Copy link

github-actions bot commented Sep 18, 2023

🙈 The PR is closed and the preview is expired.

@quarkus-bot

This comment has been minimized.

Copy link
Contributor

@geoand geoand left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great stuff!

@cescoffier
Copy link
Member Author

Do not merge, we are still discussing if it should be in-quarkus or outside.

@geoand geoand added the triage/needs-decision This issue proposes a design change. Needs to be discussed in the ML label Sep 19, 2023
Copy link
Contributor

@ozangunalp ozangunalp left a 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.

@cescoffier cescoffier force-pushed the loom-unit-integration branch from 9c30a25 to b52bc97 Compare September 20, 2023 05:55
@cescoffier cescoffier removed the triage/needs-decision This issue proposes a design change. Needs to be discussed in the ML label Sep 20, 2023
@cescoffier
Copy link
Member Author

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.

Copy link
Contributor

@geoand geoand left a 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
@cescoffier cescoffier force-pushed the loom-unit-integration branch from b52bc97 to 8d80397 Compare September 20, 2023 06:36
@quarkus-bot
Copy link

quarkus-bot bot commented Sep 20, 2023

✔️ 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.

@cescoffier cescoffier merged commit 5ac4f50 into quarkusio:main Sep 21, 2023
53 checks passed
@quarkus-bot quarkus-bot bot added this to the 3.5 - main milestone Sep 21, 2023
@cescoffier cescoffier deleted the loom-unit-integration branch September 25, 2023 08:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dependencies Pull requests that update a dependency file area/documentation area/testing
Projects
Development

Successfully merging this pull request may close these issues.

3 participants