WildFly EE 11 TCK test runner

An example WildFly runner for the ported EE 11 TCK tests.

Setup

The runner needs the following dependencies. These will be installed by the setup.sh script run in the next section.

• Jakarta EE 11 TCK build, https://github.com/jakartaee/platform-tck.git.
• The jakartaee-tck-tools, https://github.com/eclipse-ee4j/jakartaee-tck-tools.git. This alternates between the latest staged version and a local snapshot build depending on if we are working on fixes to the arquillian protocols. Currently the version.jakarta.tck.arquillian is set to 1.0.0-SNAPSHOT.
• The EE10 TCK cts-10-mods requires VPN access to download not to use.
• The EE10 TCK scripts also requires VPN to clone, but not run.

TCK ENV Setup

Run the setup.sh script from the root of the wildfly-ee11-tck-runner repo on a host with a Red Hat VPN connection. The script does the following:

• Clones and builds the 11.0.0-SNAPSHOT of the EE 11 TCK test artifacts
• Clones and builds a 1.0.0-SNAPSHOT of the jakartaee-tck-tools/arquillian protocols used by the TCK
• Clones the JBoss CTS scripts
• Runs the tck10.sh script to:
  • build the Wildfly EE 11 preview
  • download the EE10 TCK
  • download derby
  • download glassfish7
  • configure wildfly with EE10 content
  • init derby with EE10 TCK content
  • run the EE10 tck script run a dummy test to start/stop wildfly

After the script completes, your wildflytckroot should contain:

[starksm@scottryzen tck-test]$ ls ../wildflytckroot/
apache-ant-1.10.6           glassfish-7.0.13.zip             platform-tck
cts-10-mods                 jakartaeetck                     scripts
db-derby-10.15.2.0-bin      jakartaee-tck-tools              tck10.log
db-derby-10.15.2.0-bin.zip  jakarta-jakartaeetck-10.0.5.zip  wildfly
glassfish7                  logs

Setup ENV Variables used in wildfly-ee11-tck-runner/pom.xml

The TS_HOME env should be set to the root of the EE10 TCK, which should be: export TS_HOME=$wildflytckroot/jakartaeetck

The WFLY_HOME should be the just built wildfly preview: export WFLY_HOME=$wildflytckroot/wildfly/dist/target/wildfly-34.0.0.Beta1-SNAPSHOT

The exact version number will depend on when you run the script, so validate the build version.

Verify the setup

To verify the setup, run these two commands from the wildfly-ee11-tck-runner root:

mvn -Pstaging surefire:test@smoketest-javatest mvn -Pstaging surefire:test@smoketest-appclient

[starksm@scottryzen tck-test]$ mvn -Pstaging surefire:test@smoketest-javatest
[INFO] Scanning for projects...
[INFO] 
[INFO] -----------------< org.wildfly.ee:wildfly-tck-runner >------------------
[INFO] Building wildfly-tck-runner 1.0
[INFO]   from pom.xml
[INFO] --------------------------------[ jar ]---------------------------------
[INFO] 
[INFO] --- surefire:3.3.1:test (smoketest-javatest) @ wildfly-tck-runner ---
[INFO] Using auto detected provider org.apache.maven.surefire.junitplatform.JUnitPlatformProvider
[INFO] 
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running com.sun.ts.tests.ejb32.lite.timer.service.stateless.ClientEjbliteservletTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.635 s -- in com.sun.ts.tests.ejb32.lite.timer.service.stateless.ClientEjbliteservletTest
[INFO] 
[INFO] Results:
[INFO] 
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO] 
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  7.625 s
[INFO] Finished at: 2024-08-29T11:58:57-06:00
[INFO] ------------------------------------------------------------------------

[starksm@scottryzen tck-test]$ mvn -Pstaging surefire:test@smoketest-appclient
[INFO] Scanning for projects...
[INFO] 
[INFO] -----------------< org.wildfly.ee:wildfly-tck-runner >------------------
[INFO] Building wildfly-tck-runner 1.0
[INFO]   from pom.xml
[INFO] --------------------------------[ jar ]---------------------------------
[INFO] 
[INFO] --- surefire:3.3.1:test (smoketest-appclient) @ wildfly-tck-runner ---
[INFO] Using auto detected provider org.apache.maven.surefire.junitplatform.JUnitPlatformProvider
[INFO] 
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running com.sun.ts.tests.ejb32.relaxedclientview.stateless.ClientTest
[INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 23.27 s -- in com.sun.ts.tests.ejb32.relaxedclientview.stateless.ClientTest
[INFO] 
[INFO] Results:
[INFO] 
[INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0
[INFO] 
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  25.272 s
[INFO] Finished at: 2024-08-29T13:08:52-06:00
[INFO] ------------------------------------------------------------------------

The first validates a basic ejb32 test using the javatest arquillian protocol. The second validates an appclient talking to a basic ejb32 using the appclient arquillian protocol.

Running the Tests

So far, there are example runners for:

• ejb30
• ejb32
• jms
• jpa

Each tck module has its own execution section with the id set to the module name. To run a single test module, use mvn surefire:test@<module-name>. For example, to run the JPA tests, use:

mvn -Pstaging surefire:test@jpa
mvn -Pstaging surefire:test@jpa -Dtest=org.jboss.spec.javax.persistence.jpa.test.criteria.CriteriaQueryTest

The second command runs a single test class from the JPA module.

Running the test in an IDE

You can run a test like com.sun.ts.tests.ejb32.lite.timer.schedule.tx.ClientEjblitejsfTest from within your IDE, but you need to configure the system properties for the test runner to something similar to the surefire. The most important system property is the arquillian.xml (-Darquillian.xml=javatest-arquillian.xml) since the Arquillian container configuration descriptor uses a non-default name. If youadd another container configuration for your server, either make it the default or change the arquillian.launch system property to the name of your configuration.