quarkusio/quarkus

Cannot run integration tests in IDEs in clean workspace

Open

#48273 opened on Jun 6, 2025

View on GitHub
 (7 comments) (0 reactions) (1 assignee)Java (12,967 stars) (2,464 forks)batch import
area/testinggood first issue

Description

Right-clicking and running an integration test in a clean project in any IDE (Eclipse, VS Code, IntelliJ) gives the following:

java.lang.IllegalStateException: Unable to locate the artifact metadata file created that must be created by Quarkus in order to run integration tests. Make sure this test is run after the Quarkus artifact is built from your build tool.
	at io.quarkus.test.junit.IntegrationTestUtil.readQuarkusArtifactProperties(IntegrationTestUtil.java:409)
	at io.quarkus.test.junit.QuarkusIntegrationTestExtension.ensureStarted(QuarkusIntegrationTestExtension.java:141)
	at io.quarkus.test.junit.QuarkusIntegrationTestExtension.beforeAll(QuarkusIntegrationTestExtension.java:127)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)

The problem reproduces in 3.20, so it's not related to the test classloading rewrite. mvn package on the command-line fixes it.

I don't know if we want to do a code fix for this, since the error message is pretty clear.

Contributor guide

Tech stack
java
Domain
testingbackend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
needs maintainer response
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaMavenQuarkus basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the IntegrationTestUtil.java file around line 409 to understand the condition that triggers the exception. Check the comments in the issue for any proposed solutions. Evaluate if adding a small check in the test extension to provide a more helpful error message or automatically run the build is feasible.