JBeret TCK Testing Process

I have recorded the process to do the TCK test for JBeret here:

Currently, it’s a manual process. In the future I plan to automate the testing process.

Here is some additional info:

To download the TCK zip, here is the command:

➤ wget https://download.eclipse.org/jakartaee/batch/2.1/jakarta.batch.official.tck-2.1.1.zip                                                                 02:18:59
--2023-10-16 02:19:00--  https://download.eclipse.org/jakartaee/batch/2.1/jakarta.batch.official.tck-2.1.1.zip
正在解析主机 download.eclipse.org (download.eclipse.org)...
正在连接 download.eclipse.org (download.eclipse.org)||:443... 已连接。
已发出 HTTP 请求,正在等待回应... 200 OK
长度:2668103 (2.5M) [application/zip]
正在保存至: “jakarta.batch.official.tck-2.1.1.zip”

jakarta.batch.official.tck-2.1.1.zip      100%[===================================================================================>]   2.54M  59.2KB/s  用时 2m 17s

2023-10-16 02:21:19 (19.0 KB/s) - 已保存 “jakarta.batch.official.tck-2.1.1.zip” [2668103/2668103])

Prepare the projects for testing:

cd jberet_tck                                                                                                                                               02:37:50
➤ ls                                                                                                                                                          02:37:53
jakarta.batch.official.tck-2.1.1	jakarta.batch.official.tck-2.1.1.zip	jberet-tck-porting			wildfly

To do EE testing, it needs WildFly.

The jberet-tck-porting1 project contains POMs that use JBeret as dependency that can be copied to jakarta.batch.official.tck-2.1.12 project for testings.

In addition, it contains the JAR file that needs to be copied into WildFly for EE testings.

The detail of test process it recorded in the comment of the above PR link.


My Github Page: https://github.com/liweinan

Powered by Jekyll and Theme by solid

If you have any question want to ask or find bugs regarding with my blog posts, please report it here: