Skip to content

Gradle quarkusIntTest does not execute regular tests since 3.22 #48048

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

Closed
ls-bit opened this issue May 26, 2025 · 7 comments · Fixed by #48131
Closed

Gradle quarkusIntTest does not execute regular tests since 3.22 #48048

ls-bit opened this issue May 26, 2025 · 7 comments · Fixed by #48131
Labels
area/gradle Gradle env/windows Impacts Windows machines kind/bug Something isn't working
Milestone

Comments

@ls-bit
Copy link
Contributor

ls-bit commented May 26, 2025

Describe the bug

Since 3.22 running ./gradlew quarkusIntTest does not run @QuarkusTest or JUnit tests anymore.

Before 3.22 the task ran all tests, as described in the docs:

This task depends on both test and quarkusBuild tasks. The final artifact will be produced before running tests.

Expected behavior

./gradlew quarkusIntTest runs @QuarkusIntegrationTest and @QuarkusTest tests

Actual behavior

./gradlew quarkusIntTest only runs @QuarkusIntegrationTest tests

How to Reproduce?

  1. Generate a Quarkus 3.22 project with gradle https://code.quarkus.io/?b=GRADLE
  2. Change the test in GreetingResourceTest to fail
  3. Run ./gradlew quarkusIntTest -> build does not fail

Output of uname -a or ver

Microsoft Windows [Version 10.0.26100.3775]

Output of java -version

openjdk version "21.0.2" 2024-01-16 OpenJDK Runtime Environment GraalVM CE 21.0.2+13.1 (build 21.0.2+13-jvmci-23.1-b30) OpenJDK 64-Bit Server VM GraalVM CE 21.0.2+13.1 (build 21.0.2+13-jvmci-23.1-b30, mixed mode, sharing)

Quarkus version or git rev

3.22.3

Build tool (ie. output of mvnw --version or gradlew --version)

Gradle 8.13

Additional information

No response

@ls-bit ls-bit added the kind/bug Something isn't working label May 26, 2025
@quarkus-bot quarkus-bot bot added area/gradle Gradle env/windows Impacts Windows machines labels May 26, 2025
Copy link

quarkus-bot bot commented May 26, 2025

/cc @glefloch, @quarkusio/devtools

@geoand
Copy link
Contributor

geoand commented May 26, 2025

This was actually changed in #46676 as a response to #44383.

@aloubyansky I assume this change of behavior was intentional?

@ls-bit
Copy link
Contributor Author

ls-bit commented May 26, 2025

If the change is intentional, then it would be great if the docs were updated at https://quarkus.io/guides/gradle-tooling#running-integration-tests and to mention in the migration guide since it breaks previous behaviour.

@aloubyansky
Copy link
Member

@ls-bit you're right, we should document it. It was indeed an intentional change. We need to make sure check runs all the tests.

@geoand
Copy link
Contributor

geoand commented May 27, 2025

@ls-bit would you be interested in contributing the docs fix?

@ls-bit
Copy link
Contributor Author

ls-bit commented May 27, 2025

Thanks for the feedback! Yeah, i can try to prepare a PR. Hopefully, i will find some time later this week

@geoand
Copy link
Contributor

geoand commented May 27, 2025

🙏🏽

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/gradle Gradle env/windows Impacts Windows machines kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants