User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
On 7/28/21 3:02 PM, Vano Beridze wrote:
By anyone I meant myself too :)
Thank you Vano!
Is there any guide or quick write-up how to
proceed with this?
There is the [1] document which is not a guide but does link to
some other discussions that may be helpful. I hope to get started
myself with helping soon.
If you want to fork the
https://github.com/eclipse-ee4j/jakartaee-tck/tree/tckrefactor
branch and start updating one of the many `ejb` folders (e.g.
`ejb32`) to use `Apache Maven` to invoke one of the contained
tests via Arquillian, that would be a good start.
This will be easier to start once we have an initial test
converted to use as an example.
Scott
Maybe take some other spec's TCK as an analogy?
Also as there is no standalone ejb-tck project
on github, how one should create one?
[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].