[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[cdi-dev] Fwd: Fwd: Do you plan to move your TCK tests out of the Platform TCK project for Jakarta EE 10+?
|
Dear CDI team,
The forwarded (2 levels now) below is about moving Platform TCK
tests into the various Standalone Specification repositories to
simplify TCK test development and the Specification ballot release
process.
What do you think about the idea of updating the Jakarta EE
Platform TCK to be based on Junit5/TestNG, Arquillian?
Do you recommend using TestNG over JUnit5 for the Platform TCK?
We likely will need to support running tests from both test
frameworks but I am not sure which framework is easier to use for
converting the 2+ million lines of Platform TCK tests.
Are there any Arquillian extensions that support adding EE vendor
specific deployment descriptors to the TCK test deployments? I
would like to make this as easy as possible for those running the
Jakarta EE Platform TCK tests.
Thanks for your input on ^ and
any of the below!
Scott
-------- Forwarded Message --------
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