See: Description
Class | Description |
---|---|
_Suite |
Runs a minimal set of compatibility tests aimed at discovering
incompatibilities introduced in the latest development version (trunk).
|
_SuiteDevFull |
Tests trunk against all available versions of old Derby releases.
|
_SuiteOld |
Tests all the newest branch releases and trunk against each other.
|
_SuiteOldFull |
Tests all available versions of Derby against each other.
|
AbstractCompatibilityTest |
Abstract test case with common functionality often required when writing
JDBC client driver compatibility tests.
|
ClientCompatibilityRunControl |
Spawns the JVM process running the compatibility tests for the given client
version.
|
ClientCompatibilitySuite |
Returns the test suite run by each client in the compatibility test.
|
JDBCDriverTest |
A set of client driver compatibility tests.
|
JDBCDriverTest.T_CN |
Helper class capturing TypeCoercion logic.
|
JDBCDriverTest.TypeDescriptor |
Description of a legal datatype and the version of Derby
where the datatype first appears.
|
VersionCombinationConfigurator |
Generates a set of client-server combinations to run the compatibility
tests for.
|
VersionedNetworkServerTestSetup |
Starts a network server of the specified Derby version.
|
Classes used to test the compatibility between different versions of Derby clients and Derby servers. The main entry point is the _Suite class, with the other suites as alternatives giving more test coverage in terms of the number of combinations tested.
The MATS version of the compatibility test should be run as part of suites.All. It is your responsibility to keep the local release repository up to date (the default location is $HOME/.derbyTestingReleases/, this can be overridden by using derbyTesting.oldReleasePath).
For non-default runs, the following steps should be considered:
Note that the set of combinations computed depends on the old Derby releases that are available through the release repository. For this reason it is important to keep the local repository updated. Once initialized, i.e svn co http://svn.apache.org/repos/asf/db/derby/jars $HOME/.derbyTestingReleases, you only have to update it each time a new Derby release comes out.
Testing the compatibility between a given client driver and a given server is best done by running those two components in separate processes. This simplifies handling multiple versions of the code base, but introduces some challenges for properly handling the external processes.
Apache Derby V10.13 Internals - Copyright © 2004,2016 The Apache Software Foundation. All Rights Reserved.