| Re: [jakartaee-tck-dev] Are the EE 10 Platform TCK rules for controlling the filtering of which tests to run in the ant script/build.xml files? Some tests aren't controlled by keyword properties... |
On Fri, Jan 19, 2024, 3:01 PM Scott Marlow <smarlow@xxxxxxxxxx> wrote:Hi,
With the EE 10 Platform TCK, if I run the com.sun.ts.tests.ejb30.bb.session.stateless.annotation.appexception.annotated tests, we only run the "at*" tests such as "atCheckedAppExceptionTest" which I think is the reverse of what the code comment in https://github.com/jakartaee/platform-tck/blob/master/src/com/sun/ts/tests/ejb30/common/appexception/ClientBase.java#L49 indicates "Tests whose name does NOT begin with "at" are for the /annotated/".
It would also be helpful to know how to identify other ClientBase classes that have optional tests that are similar.If this is the only case, we can easily introduce a new ClientBase class that doesn't have optional tests. The bigger problem is finding all of the ClientBase classes with optional tests.
Regardless, we need to understand what in the Jakarta EE 10 (and earlier) TCK tests is ensuring that com.sun.ts.tests.ejb30.bb.session.stateless.annotation.appexception.annotated (https://github.com/jakartaee/platform-tck/tree/master/src/com/sun/ts/tests/ejb30/bb/session/stateless/annotation/appexception/annotated) only run the "at" (tests that begin with "at") and the com.sun.ts.tests.ejb30.bb.session.stateless.annotation.appexception.override (https://github.com/jakartaee/platform-tck/tree/master/src/com/sun/ts/tests/ejb30/bb/session/stateless/annotation/appexception/override) tests run the "at" tests plus other tests.
Are the rules for controlling the filtering of which com.sun.ts.tests.ejb30.bb.session.stateless.annotation.appexception tests to run in the ant script/build.xml files?
Having the answer will help us to proceed with TCK refactoring.
Thanks,
Scott