Run all platform and standalone TCKs for Jakarta EE 10 certification of GlassFish 7

[arjantijms]

The Jakarta EE 10 certification consists of running the platform TCKs (Full, Web, Core) and an assortment of standalone tests.

This issue tracks these:

• platform - full
• platform - web
• platform - core
• standalone - faces
• standalone - security
• standalone - authentication
• standalone - rest
• standalone - concurrency
• standalone - json-b
• standalone - json-p
• standalone - cdi
• standalone - batch
• standalone - bean validation
• standalone - (pages) debugging
• standalone - xml binding

See also:

• TCK runner Jobs for new Standalone TCKs against Glassfish 7 jakartaee/platform-tck#1032
• https://github.com/eclipse-ee4j/jakartaee-tck/pull/1039/files

[alwin-joseph]

* [x]  standalone - faces

We are expecing new service release for faces TCK as mentioned at #23960

* [x]  standalone - security

All tests passes .
CI jobs at jakartaee-tck -
https://ci.eclipse.org/jakartaee-tck/job/10/job/jakarta-security-tck-glassfish-run/
https://ci.eclipse.org/jakartaee-tck/job/10/job/jakarta-security-tck-glassfish-run-jdk17/

* [x]  standalone - authentication

It is better to get a new service release of authentication TCK after merging jakartaee/authentication#167 to include all authentication tck sources in one bundle.

[dmatej]

Just FYI, we created this spreadsheet to have the whole picture in one place:
https://docs.google.com/spreadsheets/d/18BARERS-smPDv6vfK-73k5Gy3OrA2mUvBamwL7iGA3Q/edit#gid=0
At least when we know how, we can repeat any build locally (I did not push the TCK runner anywhere as Jenkins does it's job well and nobody asks for that, but I can still do that, but critical are TCK tests outside these "old one's").

[scottmarlow]

Copying from https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/user_guides/jakartaee/src/main/jbake/content/intro.adoc:

In addition to the instructions and requirements described in this
document, all Jakarta EE 10 Platform implementations must
also pass the standalone TCKs for the following technologies:

* Jakarta Activation -- see https://jakarta.ee/specifications/activation/ for additional details
* Jakarta Authentication -- see https://jakarta.ee/specifications/authentication/3.0/ for additional details
* Jakarta Batch -- see https://jakarta.ee/specifications/batch/2.1/ for additional details
* Jakarta Bean Validation -- see https://jakarta.ee/specifications/bean-validation/3.0/ for additional details
* Jakarta Concurrency -- see https://jakarta.ee/specifications/concurrency/3.0/ for additional details
* Jakarta Contexts and Dependency Injection (including Language Model TCK) -- see https://jakarta.ee/specifications/cdi/4.0/ for additional details
* Jakarta Debugging Support for Other Languages -- see https://jakarta.ee/specifications/debugging/ for additional details
* Jakarta Dependency Injection -- see https://jakarta.ee/specifications/dependency-injection/2.0/ , for additional details
* Jakarta Faces -- see https://jakarta.ee/specifications/faces/4.0/ for additional details
* Jakarta JSON Binding -- see https://jakarta.ee/specifications/jsonb/3.0/ for additional details
* Jakarta JSON Processing -- see https://jakarta.ee/specifications/jsonp/2.1/ for additional details
* Jakarta Mail -- see https://jakarta.ee/specifications/mail/2.1/ for additional details
* Jakarta RESTFul Web Services -- see https://jakarta.ee/specifications/restful-ws/3.1/ for additional details
* Jakarta Security -- see https://jakarta.ee/specifications/security/3.0/ for additional details
* Jakarta XML Binding -- see https://jakarta.ee/specifications/xml-binding/3.0/ for additional details

All Jakarta EE 10 Web Profile implementations must also pass the standalone TCKs for the following technologies:

* Jakarta Authentication -- see https://jakarta.ee/specifications/authentication/3.0/ for additional details
* Jakarta Bean Validation -- see https://jakarta.ee/specifications/bean-validation/3.0/ for additional details
* Jakarta Concurrency -- see https://jakarta.ee/specifications/concurrency/3.0/ for additional details
* Jakarta Contexts and Dependency Injection (including Language Model TCK) -- see https://jakarta.ee/specifications/cdi/4.0/ for additional details
* Jakarta Debugging Support for Other Languages -- see https://jakarta.ee/specifications/debugging/ for additional details
* Jakarta Dependency Injection -- see https://jakarta.ee/specifications/dependency-injection/2.0/ for additional details
* Jakarta Faces -- see https://jakarta.ee/specifications/faces/4.0/ for additional details
* Jakarta JSON Binding -- see https://jakarta.ee/specifications/jsonb/3.0/ for additional details
* Jakarta JSON Processing -- see https://jakarta.ee/specifications/jsonp/2.1/ for additional details
* Jakarta RESTFul Web Services -- see https://jakarta.ee/specifications/restful-ws/3.1/ for additional details
* Jakarta Security -- see https://jakarta.ee/specifications/security/3.0/ for additional details

From the above list, I think the issue description should also include check options for Standalone TCKs: Activation, Mail, Language Model TCK.

[OndroMih]

Hi @arjantijms , is this still relevant?