Great news. Welcome onboard.
From: cu-dev <cu-dev-bounces@xxxxxxxxxxx> On Behalf Of Nathan Rauh
Sent: 13 September 2021 15:39
To: cu developer discussions <cu-dev@xxxxxxxxxxx>
Subject: Re: [cu-dev] Do you plan to move your TCK tests out of the Platform TCK project for Jakarta EE 10+?
A developer from my company, Kyle Aure, has volunteered to work on getting our TCK tests ported over from the platform to the spec project (as was the topic of the forwarded email chain).
This should make it much easier for us to write and run additional TCK tests for our new EE 10 features that will be going in. Thanks Kyle and welcome to the Jakarta Concurrency project!
From: "Steve Millidge (Payara)" <steve.millidge@xxxxxxxxxxx>
To: "cu developer discussions" <cu-dev@xxxxxxxxxxx>
Date: 07/02/2021 02:45 AM
Subject: [EXTERNAL] Re: [cu-dev] Do you plan to move your TCK tests out of the Platform TCK project for Jakarta EE 10+?
Sent by: "cu-dev" <cu-dev-bounces@xxxxxxxxxxx>
I'm in favour also but again don't know where to start or how much effort is involved.
From: cu-dev <cu-dev-bounces@xxxxxxxxxxx> on behalf of Nathan Rauh <nathan.rauh@xxxxxxxxxx>
Sent: 01 July 2021 8:05 PM
To: cu developer discussions <cu-dev@xxxxxxxxxxx>
Subject: Re: [cu-dev] Do you plan to move your TCK tests out of the Platform TCK project for Jakarta EE 10+?
I'm unsure how much effort it will require, but ignoring that aspect, I'm in favor of this because it will ultimately give us the option of delivering specification updates and the corresponding TCK updates to test them together under a single pull. And it seems like the natural place for the tests to be maintained. MicroProfile is arranged this way and it works very nicely there.
From: Scott Marlow <smarlow@xxxxxxxxxx>
To: cu developer discussions <cu-dev@xxxxxxxxxxx>
Date: 06/22/2021 02:33 PM
Subject: [EXTERNAL] [cu-dev] Do you plan to move your TCK tests out of the Platform TCK project for Jakarta EE 10+?
Sent by: "cu-dev" <cu-dev-bounces@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_______________________________________________
cu-dev mailing list
cu-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cu-dev
_______________________________________________
cu-dev mailing list
cu-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cu-dev
