You should be able to tell by looking what suites it is in. If it's not in derbynetclientmats then it may very well not be able to run with the network client.

I too wish all our tests ran with the network client, but we're just not there yet. Maybe someone can do a scan through the tests to see if some *could* be added but just haven't yet.

David

[EMAIL PROTECTED] wrote:
"KAH" == Knut Anders Hatlen <[EMAIL PROTECTED]> writes:


    KAH> See jdbcapi/users.sql for an example. It seems like you can skip
    KAH> "jdbc:derby:" from the connection url.

    KAH> connect 'wombat;shutdown=true;user=francois;password=paceesalute';
    KAH> connect 'myDB;create=true;user=dan;password=MakeItFaster';

Hmm, I just discovered, to my surprise and disappointment, that I
am unable to test that this actually works, because
lang/triggerGeneral.sql does not run under DerbyNet or DerbyNetClient.

Why is that? I assumed, in my naivete, that tests should run in
all three frameworks, unless the test is testing something that is specific
to a particular framework...
Is there a way to know if a particular test is only intended for one,
or some frameworks? Other than running it in that framework and seeing
that it fails...? I guess could always run find java/testing -name <testname>.out and see how many master files the test has. Will that work, or is the output compared to a default master if there isn't one for that framework?
begin:vcard
fn:David W Van Couvering
n:Van Couvering;David W
org:Sun Microsystems, Inc.;Database Technology Group
email;internet:[EMAIL PROTECTED]
title:Senior Staff Software Engineer
tel;work:510-550-6819
tel;cell:510-684-7281
x-mozilla-html:TRUE
version:2.1
end:vcard

Reply via email to