db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "DerbyTopLevelJunitTests" by DanDebrunner
Date Tue, 16 Jan 2007 22:03:15 GMT
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 DanDebrunner:

New page:
= Introduction =
This page lists the various top-level tests that can be run against Derby, it applies to the
trunk only.
In most cases a test class can be run directly by any JUnit test runner without setting system

= Functional and Unit Tests =
The test classes that need to be run to cover all functional and unit tests for Derby.

|| '''Test Class''' || '''Run by junit-all''' || '''Comments''' ||
|| `org.apache.derbyTesting.functionTests.suites.All` || Yes, though the ant targets contain
logic that matches the contents of suites.All rather than running suites.All directly. ||
Majority of the functional & unit tests, all intended to be run as a single Junit test
run invocation. If details are needed on the tests included then look at the source and see
what tests are included. Any test class run directly or indirectly by suites.All can be run
as a standalone JUnit test, e.g. `...functionTests.tests.jdbcapi._Suites` for all the JDBC
API tests `...functionTests.tests.lang.MathTrigFunctionsTest` to just test the math trig functions.
|| `org.apache.derbyTesting.functionTests.tests.jdbcapi.AutoloadTest` ||<|4> Yes, via
target `junit-autoloadtest` ||<|4> Each test class needs to be in a separate JUnit run
in its own JVM as these are testing the auto-loading of JDBC drivers at JVM startup. ||
|| `org.apache.derbyTesting.functionTests.tests.jdbcapi.JDBCDriversEmbeddedTest` ||
|| `org.apache.derbyTesting.functionTests.tests.jdbcapi.JDBCDriversClientTest`||
|| `org.apache.derbyTesting.functionTests.tests.jdbcapi.JDBCDriversAllTest`||
|| `org.apache.derbyTesting.functionTests.tests.upgradeTests._Suite` || No || Upgrade tests,
requires the system property `derbyTesting.oldReleasePath` to be set to a folder containing
previous releases. See the source comments for upgradeTests._Suite for details on how the
folder is expected to look. ||

= System Tests =
= Performance Tests =

View raw message