Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jakartaee-tck-dev] legacy test vehicles within refactored Platform TCK

Hi Scott Marlow, Scott Stark,
Jakarta EE Platform specification defines requirements for individual Jakarta technology specification(Eg:batch) for the Platform, the specification also provides details of container types required for individual Jakarta technology specification.
For Example, Jakarta EE Platform specification for `batch` mentions requirement as "In a full Jakarta EE product, all Jakarta EE web containers and Jakarta Enterprise Beans containers are required to support the Batch API". Jakarta EE Platform specification does not mention vehicles(as in legacy TCK).

IMO, if Platform TCK executes tests inside container as defined in platform specification that would comply with Platform specification and Platform TCK will not require legacy test vehicles for refactored TCK.


Arquillian container + ShrinkWrap + Arquillian protocol tooling helps with deployment into container as required by Platform specification. I am of the opinion that Platform TCK refactor work will be simpler without javatest and legacy Vehicles.
My current opinion is based on Arquillian Servlet Protocol and Arquillian Appclient Protocol being sufficient to run refactored platform TCK tests within required containers. Please correct me, if the assumption is wrong.

regards,
Guru

Back to the top