[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jakartaee-platform-dev] [External] : Re: Review of Platform TCK removal of duplicate Jakarta JSON Binding tests
|
On 3/1/22 12:58 PM, arjan tijms wrote:
Hi
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:
- REST Standalone TCK
- Supports testing the Java SE (add jars to classpath) way.
- Supports Java EE testing (deploy test deployment + deploy
vendor deployment descriptors) way.
- JSON-B Standalone TCK
- Supports testing the Java SE (add jars to classpath) way.
- JSON-P Standalone TCK
- Supports testing the Java SE (add jars to classpath) way.
- Batch Standalone TCK
- Supports testing the Java SE (add jars to classpath) way.
- Supports Java EE testing (deploy test deployment) way.
- Concurrency Standalone TCK
- Supports Java EE testing (deploy test deployment) way.
- Faces Standalone TCK
- 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