Andreas Korneliussen wrote:
I propose to introduce a new test type called "junit" (current test
types are: sql,sql2,unit,java,multi,demo - unit is not junit)
Then you can use:
java org.apache.derbyTesting.functionTests.harness.RunTest
<TestCaseClassName>.junit
to run a Junit test - instead of:
java org.apache.derbyTesting.functionTests.harness.RunTest
<AnotherClassWithMainMethod>.java
If I understand this proposal correctly, there will be a one-to-one
mapping between so-called ".junit" tests and ".java" files, right? And
there will be no actual files ending with ".junit", but the harness will
map the test names ending with ".junit" to actual java/class files
containing the actual JUnit test code?
I guess I am asking because at the moment I don't fully understand how
the different types in the current harness work, i.e. how to run/invoke
the different types of tests, and how the harness handles these cases.
Is this documented somewhere? The java/testing/README.htm file mentions
briefly that the .java, .sql, .sql2, .multi and .unit test types exist,
but not much more. The "demo" type is not mentioned at all...
By the way, there is apparently a bug in this README.html file, which
states that for multi tests, "the actual test files live under
org/apache/derbyTesting/functionTests/multiTests" (a directory which
does not exist in the repository). I guess this directory should be
"org/apache/derbyTesting/functionTests/multi".
--
John
