"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? Should it be possible to run CompatibilitySuite with junit.swingui.TestRunner? It does not work for me. I get an NPE... > - 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? -- dt
