The WildFly Arquillian Adapter can be used to test your application with WildFly Application Server or JBoss EAP. It works with both managed and unmanaged standalone and domain servers. As of 3.0.0 there is also a bootable JAR adapter as well.
Versions under 3.0.0 should work with any version of WildFly and JBoss EAP 7.0 and higher. Version 3.0.0 requires a minimum of WildFly 13 or JBoss EAP 7.2. Versions 5.0 for Jakarta EE 10 and work with WildFly 27 and higher and JBoss EAP 8.0 and higher.
Found a bug or want a new feature? Please file a bug on the issue tracker.
The current minimum is Java 11 and Maven 3.8.0. To build execute the following command.
mvn clean install
You can import the org.wildfly.arquillian:wildfly-arquillian-bom to easily include the dependencies you’d need.
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.wildfly.arquillian</groupId>
<artifactId>wildfly-arquillian-bom</artifactId>
<version>${version.org.wildfly.arquillian}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>The WildFly Arquillian Adapter can manage the container process with the following dependency.
<dependency>
<groupId>org.wildfly.arquillian</groupId>
<artifactId>wildfly-arquillian-container-managed</artifactId>
<scope>test</scope>
</dependency>If you’d to manage the container process via a different method use the following dependency.
<dependency>
<groupId>org.wildfly.arquillian</groupId>
<artifactId>wildfly-arquillian-container-remote</artifactId>
<scope>test</scope>
</dependency>The WildFly Arquillian Adapter can manage the container process with the following dependency.
<dependency>
<groupId>org.wildfly.arquillian</groupId>
<artifactId>wildfly-arquillian-container-domain-managed</artifactId>
<scope>test</scope>
</dependency>If you’d to manage the container process via a different method use the following dependency.
<dependency>
<groupId>org.wildfly.arquillian</groupId>
<artifactId>wildfly-arquillian-container-domain-remote</artifactId>
<scope>test</scope>
</dependency>Since version 3.0.0 of the adapter you can now use Arquillian to test your bootable JAR’s.
<dependency>
<groupId>org.wildfly.arquillian</groupId>
<artifactId>wildfly-arquillian-container-bootable</artifactId>
<scope>test</scope>
</dependency>|
Important
|
The Please migrate to the new WildFly Testing Tools project: <dependency>
<groupId>org.wildfly.testing</groupId>
<artifactId>wildfly-testing-tools</artifactId>
<version>${version.org.wildfly.testing}</version>
<scope>test</scope>
</dependency> |
The testing tools provide utilities for working with deployments and modules in WildFly tests, including:
-
Creating deployment descriptors (jboss-deployment-structure.xml, jboss-web.xml, permissions.xml)
-
Building and managing JBoss Modules for testing
-
XML utilities for test configuration
When migrating from org.wildfly.arquillian:wildfly-testing-tools to org.wildfly.testing:wildfly-testing-tools, update your imports:
| Old Package | New Package |
|---|---|
|
|
|
|
The deprecated artifact contains compatibility shims that delegate to the new artifact, so the migration can be done incrementally. Simply update your dependency and fix the import statements when deprecation warnings appear.
|
Important
|
The annotations in Please migrate to the new annotations in the WildFly Testing Tools project: <dependency>
<groupId>org.wildfly.testing</groupId>
<artifactId>wildfly-junit-api</artifactId>
<version>${version.org.wildfly.testing}</version>
<scope>test</scope>
</dependency> |
When migrating, update your annotation imports from:
-
org.wildfly.arquillian.junit.annotationstoorg.wildfly.testing.junit.annotation
Example:
// Old
import org.wildfly.arquillian.junit.annotations.AnyOf;
import org.wildfly.arquillian.junit.annotations.JBossHome;
import org.wildfly.arquillian.junit.annotations.RequiresModule;
import org.wildfly.arquillian.junit.annotations.RequiresModules;
// New
import org.wildfly.testing.junit.annotation.AnyOf;
import org.wildfly.testing.junit.annotation.JBossHome;
import org.wildfly.testing.junit.annotation.RequiresModule;
import org.wildfly.testing.junit.annotation.RequiresModules;|
Note
|
If you use the |
Releasing this project requires access to JBoss Nexus.
To perform a release ensure you’re on the correct branch and that branch is up to date. Once done you can simply use
the release.sh bash script.
./release.sh -r 5.1.0.Final -d 5.1.1.Final-SNAPSHOTIf this was successful, instructions will be printed on the console with the next set of instructions for processing.
...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 48.454 s
[INFO] Finished at: 2025-09-08T15:03:05-07:00
[INFO] ------------------------------------------------------------------------
Your release has been successful. Check the validation after 15:13:05 on https://repository.jboss.org/nexus.
Once validation is successful, execute the following command:
git checkout v5.1.0.Final
mvn nxrm3:staging-move -Dmaven.repo.local="/tmp/m2/repository/wildfly-arquillian"
git checkout release-update
git push upstream release-update
git push upstream v5.1.0.Final