WildFly Arquillian Adapter

Table of Contents

Building
Usage

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

Building

The current minimum is Java 11 and Maven 3.8.0. To build execute the following command.

mvn clean install

Usage

BOM Usage

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>

Standalone

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>

Domain

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>

Bootable JAR

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>

wildfly / wildfly-arquillian