Skip to content

Jakarta EE 10 TCK Tests

Jump to bottom
David Matějček edited this page Mar 14, 2024 · 15 revisions

Introduction

All TCK tests can be executed directly from the GlassFish git repository. Prerequisities are:

  • JDK17
  • Maven 3.9.6+
  • Ant 1.10.14+
  • Docker host(s)

Or you can use precreated docker node for these builds: dmatej/glassfish-jenkins-node for builds on your Jenkins.

In 2022 we were able to run all TCK tests on private computers in addition to the Eclipse TCK project (Platform TCK Builds and Standalone TCK Builds). Results with some really short info are here (Google Docs table).

Since then we made some changes, so now we are not using a bash script any more, but all TCK tests were integrated to the GlassFish build.

Some of TCK sets have a standalone and a platform variant of execution. That is because the whole TCK Platform package is really huge amount of tests and quite complicated and old piece of software containing around 40 000 of integration tests. The TCK Team started first gained some control over the project, then started stabilizing it and finally they started with the refactoring which is still in progress. But that did not stop Jakarta EE evolution, so with the release of Jakarta EE 10 we had some pieces twice while there is an effort to keep them synchronized and consistent.

Activation

  • 93 tests, 1 minute.
mvn clean install -Ptck -pl :jakarta-activation-tck,:glassfish-external-tck-activation

Application Client

  • 50 tests, 16 minutes.
mvn clean install -Ptck -pl :platform-tck-runner -Dit.test=ApplicationClientITest

Authentication

  • 68 tests, 17 minutes.
mvn clean install -Ptck -pl :jakarta-authentication-tck,:glassfish-external-tck-authentication

Authorization

  • 40 tests, 10 minutes.

Standalone variant:

mvn clean install -Ptck -pl :jakarta-authorization-tck,:glassfish-external-tck-authorization

Platform variant:

mvn clean install -Ptck -pl :platform-tck-runner -Dit.test=AuthorizationITest
Clone this wiki locally