If we set the version back to 2.4.3, for example, the warnings go away.
I suspect this depends on the order JUnit adds tests to the list of
tests to execute.
ARQTestSuite.java sets a couple of flags to make those warnings
disappear, but this does not happen when we execute tests from Maven.
makes sense - the suites should set the flags themselves.
While I was looking into this, I noticed that when we execute tests with
Maven the total number of tests executed is 3913. However, running
ARQTestSuite from Eclipse gives a total of 4360 tests. Of course,
running ARQTestSuite from Maven (i.e. mvn test -Dtest=ARQTestSuite)
gives the same result, but we lose the benefit of seeing which tests are
running and their failures.
This has always been a mystery to me - at various times the counts has
differed, and also some tests get counted and not run under Junit/Eclipse.
My suspicion is that it is something to do with the scripted tests but I
haven't looked recently.
We should probably make sure we run all tests from Maven as well by
creating an appropriate TS_*.java test suite. Isn't it?
As long as everything is Junit4 we can use @RunWith.
Junit4 does not have a way to create tests programmatically that I've
found. The scripted tests are built by reading a manifest (in RDF) and
constructing tests.
As long as this feature can be wrapped into JUnit4, as can TS_* ize the
suite properly. It's never made it to the top of the
priority/annoyances to fix list for long enough.
Or split in two - java tests and scripted tests.
Andy
Paolo
