helidon-io
TCK Tracking: Jakarta EE 10 Core Profile
Work, issues, progress associated with compatibility verification for Jakarta EE 10, Core Profile
Current status:
CDI: I am excluding the groups as it is written here: https://jakartaee.github.io/cdi-tck/#_using_the_cdi_tck_with_the_jakarta_ee_core_profile
However, I missed to add the dependency: jakarta.enterprise:cdi-tck-web-impl
After adding it I have more than what they reported (it was 725 tests). There are unfortunately 3 failures. Tests run: 758, Failures: 3, Errors: 0, Skipped: 6
Regarding the interceptor tests, as it is written here:https://jakartaee.github.io/cdi-tck/#_using_the_cdi_tck_with_the_jakarta_ee_core_profile#_about_the_cdi_tck They are included already
CDI Lang Model: Added and passing successfully
Jakarta EE Core Profile TCK: No action required, it is already: Tests run: 13, Failures: 0, Errors: 0, Skipped: 0
Concurrency TCK: Should not be added. In fact, there is no concurrent-api in Helidon
JSON P Pluggability: Added and passing successfully
DI TCK: There was one test executing the full suite, and the output was only one test. I verified it executes: Tests run: 50, Failures: 0, Errors: 0
RESTful: Some tests were excluded because it is pending a new release of Jersey and a TCK Challenge that was approved. If I enable them I get: Tests run: 2647, Failures: 1, Errors: 2
Note that the failure and the errors will be gone after a new Jersey and TCK release.
Still, we are under 2660 + 7. That 7 is related to se_bootstrap. Santiago said that is optional.
JSONB and JSONP: They are already fine.
Regarding CDI, we don't have to includejakarta.enterprise:cdi-tck-web-impl for core profile, so it was fine as it was.
@edbratt we are done at this point. We still need new release in Jersey and REST-TCK including the next: https://github.com/eclipse-ee4j/jersey/pull/5490 https://github.com/jakartaee/rest/pull/1200
We still have some differences in the number of tests compared with https://github.com/wildfly/certifications/blob/EE10/WildFly_27.0.0.Alpha5/jakarta-core-jdk17.adoc#jakarta-core-profile-1000-tck-java-se-17-results
Maybe that is related to minor version changes in TCKs. If you want I can investigate this, although I was already double checking with some people whether the excluded groups are fine.
@edbratt @m0mus
Helidon 4.x should be ready to pass TCK core profile certification: https://github.com/helidon-io/helidon/wiki/MicroProfile-6-and-Jakarta-EE-10-Core-Profile-Certification,-Helidon-4
There is one TCK Challenge still openned in CDI, but they told me we have to ignore the test: https://github.com/jakartaee/cdi-tck/issues/485
Also note there are some discrepancies between WildFly and Helidon results. I think it is related to differences on TCK versions: https://github.com/wildfly/certifications/blob/EE10/WildFly_31.0.0.Final/jakarta-core-jdk21.adoc
Helidon: jakarta-cdi-tck 4.0.12: Tests run: 712, Failures: 0, Errors: 0, Skipped: 0
WildFly: CDI 4.0.6: Tests run: 715, Failures: 0, Errors: 0, Skipped: 0
Helidon: jakarta-restful-ws-tck 3.1.5: Tests run: 2647, Failures: 0, Errors: 0, Skipped: 132
WildFly: restfull 3.1.1: Tests run: 2654, Failures: 0, Errors: 0, Skipped: 130