[ejb-dev] Fwd: Fwd: Do you plan to move your TCK tests out of the Platfo

[Scott Marlow <smarlow@xxxxxxxxxx>]

Is there any interest from the Jakarta Enterprise Beans development team in moving EJB tests from github.com/eclipse-ee4j/jakartaee-tck to github.com/eclipse-ee4j/ejb-api?  Whether that happens or not, we would very much appreciate help with refactoring the EJB tests.

Thoughts?

Scott
-------- Forwarded Message --------

Subject:	Fwd: Do you plan to move your TCK tests out of the Platform TCK project for Jakarta EE 10+?
Date:	Tue, 22 Jun 2021 15:54:53 -0400
From:	Scott Marlow <smarlow@xxxxxxxxxx>
To:	jakartaee-tck developer discussions <jakartaee-tck-dev@xxxxxxxxxxx>

FYI, I just sent the below message to the following teams asking if they are interested in moving their tests to their Spec project:

ca-dev@xxxxxxxxxxx, cu-dev@xxxxxxxxxxx, jca-dev@xxxxxxxxxxx, el-dev@xxxxxxxxxxx, jacc-dev@xxxxxxxxxxx, jaxrs-dev@xxxxxxxxxxx, jakartabatch-dev@xxxxxxxxxxx, jaxws-dev@xxxxxxxxxxx, messaging-dev@xxxxxxxxxxx, jpa-dev@xxxxxxxxxxx, faces-dev@xxxxxxxxxxx, jsonb-dev@xxxxxxxxxxx, jsonp-dev@xxxxxxxxxxx, jstl-dev@xxxxxxxxxxx, jsp-dev@xxxxxxxxxxx, jta-dev@xxxxxxxxxxx, es-dev@xxxxxxxxxxx, servlet-dev@xxxxxxxxxxx, websocket-dev@xxxxxxxxxxx

I intended to include all of the Specifications for which a Standalone TCK is generated from the Platform TCK.  Which ones did I miss?  :-)

Scott

-------- Forwarded Message --------

Subject:	Do you plan to move your TCK tests out of the Platform TCK project for Jakarta EE 10+?
Date:	Tue, 22 Jun 2021 15:37:04 -0400
From:	Scott Marlow <smarlow@xxxxxxxxxx>
To:	jakartabatch developer discussions <jakartabatch-dev@xxxxxxxxxxx>

[1][2] is a proposal for how to produce Standalone TCKs by extracting TCK tests from the Platform TCK.  The process for extracting Standalone TCK tests is described via the GUIDELINE FOR EXTRACTING TCK section [3].

Do you plan to move your TCK tests out of the Platform TCK project and into your Specification project?  If yes, you will publish your Standalone TCK artifacts to Maven so that the Platform TCK can consume your tests.  Some Standalone Specification TCKs will also be consumed by the Core Profile TCK (and possibly other EE profiles).

From the [1] feedback received so far, both TestNG + Junit5 are popular test frameworks.  Maven is the likely choice to switch to using in the EE Platform TCKs.

The Platform TCK community needs to take a deep look at the Platform TCK internals and consider what the Jakarta EE 10+ Platform TCK architecture will look like.  But I think first, we should do some incremental hacking to bring in some Maven based testing as suggested by jakartaee-tck/issues/51 [4].

Scott

[1] https://docs.google.com/document/d/1yDXTUUULUrFrUi1DV_9OcBKIiZLVxrZkA38MMvYdP-U/edit#
[2] https://github.com/eclipse-ee4j/jakartaee-platform/issues/333
[3] https://docs.google.com/document/d/1yDXTUUULUrFrUi1DV_9OcBKIiZLVxrZkA38MMvYdP-U/edit#heading=h.gt76s6wqkrva
[4] https://github.com/eclipse-ee4j/jakartaee-tck/issues/51