Evaluating the TCK for JSR 376

Volker Simonis volker.simonis at gmail.com
Thu Jul 27 09:50:38 UTC 2017

Hi Mark,

I have access to the TCK and I did some basic tests with it. The main
problem (which I've already addressed in February but which I was told
won't be fixed for 9) is the following:

The current TCK (i.e. the ModuleGraphTest) only tests the requirements
for specific modules (i.e. tests if all the modules given on the
command line or selected in the harness, have the required export and
requires edges). There are also tests which check the "closure" of a
set of modules (with regard to the 'requires' and 'requires
transitive' relation) but again only for the specific set given on the
command line or choose in the harness.

That's a nice feature for playing around, but I think the TCK
conformance test should by default really use and test all the default
platform modules from the runtime image under test and automatically
tests all these modules (i.e. it should check all exports, all the
requires transitive relations and finally it should check if the
modules form a "closed" subset with regard to the specification (i.e.
'requires transitive') and also a "closed" subset with regard to the
implementation (i.e. 'requires')).

I think this will make it possible for malicious people to certify
custom images which don't conform to the specification (because as far
as I see the TCK doesn't test a complete implementation but just the
part you ask it to test). But you probably already know that.


On Tue, Jul 25, 2017 at 9:54 PM,  <mark.reinhold at oracle.com> wrote:
> If any member of this EG would like to evaluate the TCK for this JSR
> (i.e., the JCK), and if you do not already have access to it, please
> let me know and I'll make the necessary arrangements.
> - Mark

More information about the jpms-spec-observers mailing list