Re: [ejb-dev] Removal of tests for pruned technologies versus making tes

[Jean-Louis Monteiro <jlmonteiro@xxxxxxxxxxxxx>]

As discussed today, I think consistency would be my choice.

I'll look at the impact in terms of TCK.

--

Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com

On Tue, Sep 29, 2020 at 6:36 PM Scott Marlow <smarlow@xxxxxxxxxx> wrote:

Hi,

During the Platform call [1] today it was pointed out that TCKs should
consistently handle all pruned/removed technologies the same (e.g.
either remove related tests or allow related tests to be run optionally).

We removed the Jakarta Platform EE TCK tests for Jakarta XML Registries,
Jakarta XML RPC, Jakarta Deployment, Jakarta Management but recently
updated the Platform TCK to treat the com/sun/ts/tests/ejb30 that use
Corba as optional [2].  By default the EJB tests that use Corba are not
run (default is !rmi_iiop&!corba ).

I added David Belevins + the EJB ml to ask what the impact would be if
we adjusted the changes made in [2] to instead remove the ejb30 tests
that use Corba?

We also updated the com/sun/ts/tests/rmiiiop tests to be optional as
well [2].  By default these tests are not run (default is
!rmi_iiop&!corba ).

Feedback on removing the RMI-IIOP tests instead of marking them optional
by default would also be appreciated.

Thank you Guru for all of your hard work and patience on [2].

Scott

[1]
https://docs.google.com/document/d/1EJ2ilaPhMnQqa3aw6AmwjRbBPGL3_np4uuwklgfqPZI/edit?pli=1

[2] https://github.com/eclipse-ee4j/jakartaee-tck/pull/521

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