Index of /data/main/d/derby/10.14.2.0-2/java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4

• Parent Directory
• AbortTest.java
• BlobClobTestSetup.java
• BlobSetMethodsTest.java
• BlobTest.java
• CallableStatementTest.java
• CallableStatementTestSetup.java
• ClobTest.java
• ConnectionMethodsTest.java
• ConnectionTest.java
• DataSourceTest.java
• Derby2017LayerBTest.java
• Derby3650Test.java
• Driver40Test.java
• Driver40UnbootedTest.java
• JDBC4FromJDBC3DataSourceTest.java
• LobSortTest.java
• LobStreamTest.java
• LoginTimeoutTest.java
• ParameterMetaDataWrapperTest.java
• PreparedStatementTest.java
• PreparedStatementTest42.java
• README.html
• ResultSetMetaDataTest.java
• ResultSetTest.java
• RowIdNotImplementedTest.java
• SetObjectUnsupportedTest.java
• StatementEventsTest.java
• StatementTest.java
• StatementTestSetup.java
• StreamTruncationTest.java
• TestDbMetaData.java
• TestJDBC40Exception.java
• UnsupportedVetter.java
• VerifySignatures.java
• Wrapper41.java
• Wrapper41Conn.java
• Wrapper41DataSource.java
• Wrapper41Driver.java
• Wrapper41Test.java
• XA40Test.java
• _Suite.java
• build.xml
• copyfiles.ant
• default_app.properties
• noAbortPermission.policy

Running the JDBC4 Tests

Currently, there is one suite of tests used to verify JDBC4 features:

• jdbc40 - These tests can run with either the embedded or network client, that is, under either the embedded or DerbyNetClient frameworks. In general, JDBC4 tests do not run the JCC client (DerbyNet framework) because that old client does not support the new JDBC4 feature set.

Verifying the JDBC4 feature set is a little tiresome right now. You must run the following commands in a shell window whose JAVA_HOME points at your jdk1.6 installation. After each suite run, check the test results.

java org.apache.derbyTesting.functionTests.harness.RunSuite jdbc40

# make sure the above test run succeeded

java -Dframework=DerbyNetClient org.apache.derbyTesting.functionTests.harness.RunSuite jdbc40

# make sure the above test run succeeded