You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by Apache Wiki <wi...@apache.org> on 2006/02/11 18:54:14 UTC

[Db-derby Wiki] Update of "TestingFrameworks" by BryanPendleton

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by BryanPendleton:
http://wiki.apache.org/db-derby/TestingFrameworks

New page:
The Derby regression test suites contain multiple tests. The
tests are arranged into suites for ease of use in running
multiple related tests.

Some of the test suites run the tests in alternate frameworks:

 * derbynetmats: basic network server tests using the IBM Universal JDBC driver
 * derbynetclientmats: basic network server tests using the Derby client driver

The general rule for test authors is that it is best if a test
can run in all three frameworks (embedded, and the two client configurations).
For tests that verify pure SQL behavior, the framework shouldn't matter. 
Many of the derbyLang tests are meant to test just SQL behavior, so many 
just run in embedded framework only. Running these tests in other frameworks 
might generate different outputs so you may have to generate different masters.

To see in which suites a particular test runs, you can examine the 'suites'
directory. You could also invoke the tests without actually running them 
and then see if your test gets picked up in the framework of your interest. 
RunTest has listOnly option.

There is a *lot* more information in the file: java/testing/README.htm in
the source tree.