| [jakartaee-tck-dev] Fwd: Update regarding guidance on how to produce standalone TCKs for Jakarta EE 10... |
I blind copied the TCK mailing list on the below but that went
into moderation since blind copying to a Jakarta EE mailing list
is not allowed, so forwarding instead.
For feedback specific to our plan for the Jakarta EE 10/10.1
(version is not certain yet) Platform TCK, please respond here on
jakartaee-tck-dev@xxxxxxxxxxx. So what is the plan exactly for
the Jakarta EE 10/10.1 Platform TCK? That is what we need to
figure out soon so we can get started and be able to deliver the
Platform TCKs.
So, what are the requirements for the EE 10/10.1 Platform TCK? Please see some ideas in [2]. The [2] `Platform TCK Plan` section talks about updating all of the existing Platform TCK tests to use TestNG or JUnit5 but that may not be possible to accomplish in a reasonable time period (not that we have a target date for the Jakarta EE 10/10.1 Platform yet.) Another idea could be to integrate multiple test frameworks (Java Test Harness, TestNG, JUnit5) to be used for running Platform TCK tests (perhaps with a mix of using Arquillian for test deployment/control). Any other ideas?
IMO, the overall goal should be to come up with a plan to produce
the expected Platform TCKs so that Jakarta EE 10/10.1 Platform can
be released after passing one or more compatible implementations.
I suggest that we have some (recorded) meetings so we can all sync up on the plan. We also need to figure out who will provide the expertise on the different technologies to be integrated.
I also think that now would be an awesome time to record an interview with anyone that worked on refactoring TCKs from using multiple Make tools, to instead use Apache Ant. And get their recommendation on the different paths that might get us to having working EE 10 Platform TCKs that can be reasonably run by various EE 10/10.1 implementations. Lance? Others?
Lastly, just to summarize why we are having a discussion on the
Platform + TCK mailing lists. The Platform discussion is for
getting input on any aspect but also is for determining the
Platform level requirements for the TCK changes. The TCK
discussion is also for getting input on any aspect but will turn
into a plan that describes how we will produce the Jakarta EE
10/10.1 Platform TCKs. There is also overlap of the planning with
the different Specification teams that will be moving some
Standalone tests into their Specification project (please think of
common Maven artifacts being produced by Platform TCK that
Standalone Specifications will consume and the Platform TCK will
consume TCK test artifacts from the Standalone Specifications).
Nothing is cast in stone yet, so please share your ideas for
moving forward. Feedback/help is welcome in [2] as well!
Scott
| Subject: | Re: Update regarding guidance on how to produce standalone TCKs for Jakarta EE 10... |
|---|---|
| Date: | Tue, 8 Jun 2021 13:45:18 -0400 |
| From: | Scott Marlow <smarlow@xxxxxxxxxx> |
| To: | jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx> |
[2] links to a proposal on producing Jakarta EE 10 standalone
TCKs. Everyone with a google account should have the ability to
comment on the document. I know that some Specification teams
are looking at using different test harnesses (TestNG, JUnit5
and some testing with EE containers) which are mentioned as
options in [2].
IMO, there are unknown costs to updating the Platform TCK to
work with different test harnesses but if we get volunteers to
help integrate different test harnesses, that will reduce the
time to release a Platform TCK based on EE 10. I'm speaking to
everyone reading this email, you don't have to be a Platform TCK
committer to jump in and help us reach the Platform TCK
milestone1 goal mentioned in [2].
Scott