Re: [jakartaee-platform-dev] [External] : Re: Review of Platform TCK rem

[Scott Marlow <smarlow@xxxxxxxxxx>]

On 3/1/22 12:58 PM, arjan tijms wrote:

Hi

On Tue, Mar 1, 2022 at 4:48 PM Romain Manni-Bucau <rmannibucau@xxxxxxxxx> wrote:

Hi,

just to clarify that standalone tests can be ran against any server thanks the runner and without any change so I think we cover all the mentionned case already and implementations have no blocker at all as already proven by MP and EE server

Sounds good, how does that work? The user guide only seems to refer to putting a .jar on your classpath and running against that. I didn't see it mention a server, but maybe I missed it. Do you have an example of running it against an MP or EE server?

New Standalone Specification TCKs that (currently) only target Java SE style testing will only work by putting a .jar on your classpath and running against that.  For running against a server, the respective Standalone TCK would need to be enhanced to support running against a server.

Currently for new Standalone TCKS:

1. REST Standalone TCK
1. Supports testing the Java SE (add jars to classpath) way.
   
2. Supports Java EE testing (deploy test deployment + deploy vendor deployment descriptors) way.
2. JSON-B Standalone TCK
1. Supports testing the Java SE (add jars to classpath) way.
3. JSON-P Standalone TCK
1. Supports testing the Java SE (add jars to classpath) way.
4. Batch Standalone TCK
1. Supports testing the Java SE (add jars to classpath) way.
2. Supports Java EE testing (deploy test deployment) way.
5. Concurrency Standalone TCK
1. Supports Java EE testing (deploy test deployment) way.
6. Faces Standalone TCK
1. Supports Java EE testing (deploy test deployment) way.

I hope that helps,

Regards,
Scott

Thanks!

Kind regards,

Arjan

 

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev