And to add to this, to reply to the comment by �ystein Gr�vlen:
>> because earlier today one email contained something about putting a
>> test in some file to _exclude_ it from the network server test.
>> test in some file to _exclude_ it from the network server test.
That test was in the jdbcapi or jdbc20 suite, which suite is in derbyall as well as in derbynetmats. So, that ran with embedded and DerbyNet (and via the derbynetclientmats which includes derbynetmats, with DerbyNetClient). In that case, putting it -temporarily- into the
DerbyNet.exclude list is a neat way of working around a problem we have no control over.
I hope that hasn't added to the confusion again.
Myrna
On 5/26/05, Army <[EMAIL PROTECTED]> wrote:
�ystein Gr�vlen wrote:
> I must admit that I did not understand what was needed to get it to
> run as part of the network server test. I am still a bit confused,
I agree that this can be confusing. There is some documentation on the harness
here:
https://svn.apache.org/viewcvs.cgi/*checkout*/incubator/derby/code/trunk/java/testing/README.htm
but maybe you've already read that and are still uncertain?
In a word, there are suites and there are sub-suites. For a given suite
<suiteA>, all of the tests in <suiteA>.runall are run, PLUS all of the
sub-suites listed in the "suites" property of the <suiteA>.properties file.
Sub-suites are run using their own properties PLUS any properties inherited from
their parent suite. If the parent suite and subsuite both define a property,
the parent suite's property takes precedence.
That said, the suite that gets run every night is the "derbyall" suite. So in
order for a test to run every night, it must be part of a subsuite (either
directly or through several depths of recursion) that is specified in the
"suites" property of the derbyall.properties file.
One of the subsuites that derbyall runs is "derbynetmats", which will run all of
the tests listed in derbynetmats.runall PLUS four other sub-suites listed in
derbynetmats.properties. Since the "framework" property in
derbynetmats.properties is "DerbyNet", that means that all tests/sub-suites run
from derbynetmats will run against the server using the JCC driver.
*SO*, in order to make a test run against the server every night, you have to
ensure that one of the following is true:
1) the test is included (either directly or by recursion) in one of the
subsuites listed in derbynetmats.properties,
OR
2) the test is listed in derbynetmats.runall .
In your case, since the ConcurrentImplicitCreateSchema.java test isn't part of
any of the sub-suites listed in derbynetmats.properties (it's in the "derbylang"
suite), you have to add it to the derbynetmats.runall file.
I don't think that's as clear as I'd like it to be, but hopefully it helps. And
if it doesn't...well, the important thing is that you add your new test to the
"derbynetmats.runall", and trust that that'll work ;)
> I will do this and resubmit the patch. Should it also be added to the
> derbynetclientmats.runall?
The "derbynetclientmats" suite has "derbynetmats" as a sub-suite. That means
that all files in derbynetmats.runall will be run as part of derbynetclientmats,
as well. Thus, if you add your new test to derbynetmats.runall, you will NOT
have to add it to derbynetclientmats.runall; it will be included by recursion.
Hope that helps,
Army
