Aha, this is the secret sauce I was missing. I had arrived at the same conclusion as you did, but couldn’t figure out how to actually change which tests were being run. Merely deleting a test description from the source didn’t seem to do
it on its own. It makes sense that the testsuite.jtd would just always be used if it’s present.
I assume the initial cache gets generated at some point in the TCK’s build process? I haven’t looked into that aspect of things yet to figure that out.
The initial cache isn't generated during TCK build process. The
com.sun.ts.lib.harness.TS Platform TCK class has some of the magic which is used when tests are run.
I didn't look for how the jakartaeetck/src/testsuite.jtd test cache file is invalidated between test runs as it must be updated when running a different test deployment (e.g. since we need to parse the test sources for the different deployment to see what the test methods are).
I'm not really sure why we even have a jakartaeetck/src/testsuite.jtd file but I am guessing that could reduce the time it takes when rerunning a test for certain cases (e.g. perhaps when developers are running the same test repeatedly which I think is the only time the jakartaeetck/src/testsuite.jtd file is useful IMO). It would be nice if the ant scripts deleted jakartaeetck/src/testsuite.jtd if any jakartaeetck/src/**.java files have been modified.
Scott