Hi, Dyre, my responses inline.
[EMAIL PROTECTED] wrote:
"David W. Van Couvering" <[EMAIL PROTECTED]> writes:
Hi, Dyre. It is fairly easy to integrate with the test harness.
- Place your test under tests/junitTests. Create a new subdirectory
(lang is most likely correct) if it seems appropriate.
- Have your test extend
org.apache.derbyTesting.functionTests.util.DerbyJUnitTest
Thanks David. Rick also mentioned this in
http://article.gmane.org/gmane.comp.apache.db.derby.devel/10429/match=derbyjunittest
- Make sure it has a main() routine, which runs the unit test. See
junitTests.compatibility.CompatibilitySuite for an example
This I didn't know. Is it documented anywhere? And why does it need
that? Couldn't the harness just start it with junit.textui.TestRunner?
I don't know if it's documented anywhere. If it isn't, it would be
great if someone took the initiative to do so.
Yes, I suppose it could use TestRunner directly, but that's not what the
harness does today, it only works with main routines. Are you
suggesting that be changed?
Should it be possible to run CompatibilitySuite with
junit.swingui.TestRunner? It does not work for me. I get an NPE...
Got me on that one. Rick?
- All public methods with the pattern testXXX() will automatically be run
- Add your test to a test suite (e.g. derbylang)
Will that not make it part of derbyall? Do we really want all
bugfix-regression-unit tests to be run in derbyall?
Well, that's your choice, it seems to me in general bugfix unit tests
should be part of some kind of regression test, and as far as I know
derbyall is all we have.
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
