db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1133) Split jdbc4 tests so that the suite can be run independently under the embedded and DerbyNetClients like other Derby test suites
Date Tue, 21 Mar 2006 18:41:59 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1133?page=all ]

Rick Hillegas updated DERBY-1133:
---------------------------------

    Attachment: bug1133.diff

This submission makes the following changes:

1) Rototills the jdbc4 tests so that, in general, they get their connections using ij.startJBMS()
as other unit tests do. This lets us run a given test under multiple frameworks. It also eliminates
the following curious behavior of these tests: they used to run themselves back-to-back embedded
and then under DerbyNetClient.

2) Eliminates the jdbc4 suite and replaces it with two new suites: jdbc40 and jdbc40_embeddedOnly.
The new jdbc40 suite can be run under either the embedded or the DerbyNetClient frameworks.
The new jdbc40_embeddedOnly suite only runs embedded. Hopefully, over time tests will migrate
out of jdbc40_embeddedOnly into jdbc40 and we can eliminate jdbc40_embeddedOnly.

3) Adds a short webpage describing how to run the jdbc4 tests. This webpage is wired into
the top level testing help (java/testing/README.htm) as section 6.

This patch affects the following files:

M      java\testing\README.htm
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\TestConnection.java
A      java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\default_app.properties
D      java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\TestJDBC40Exception_app.properties
D      java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\TestDbMetaData_app.properties
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\TestPreparedStatement_app.properties
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\TestQueryObject_app.properties
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\TestCallableStatementMethods.java
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\TestPreparedStatementMethods.java
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\StartTestConnection.java
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\TestResultSetMethods.java
A      java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\README.html
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\TestConnectionMethods.java
D      java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\TestCallableStatementMethods_app.properties
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\TestJDBC40Exception.java
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\TestPreparedStatementMethods_app.properties
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\TestDbMetaData.java
D      java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\TestResultSetMethods_app.properties
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\TestQueryObject.java
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\TestConnectionMethods_app.properties
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\copyfiles.ant
M      java\testing\org\apache\derbyTesting\functionTests\master\TestDbMetaData.out
A      java\testing\org\apache\derbyTesting\functionTests\suites\jdbc40_embeddedOnly.runall
A      java\testing\org\apache\derbyTesting\functionTests\suites\jdbc40_embeddedOnly.properties
D      java\testing\org\apache\derbyTesting\functionTests\suites\jdbc4.runall
A      java\testing\org\apache\derbyTesting\functionTests\suites\jdbc40.runall
D      java\testing\org\apache\derbyTesting\functionTests\suites\jdbc4.properties
A      java\testing\org\apache\derbyTesting\functionTests\suites\jdbc40.properties

> Split jdbc4 tests so that the suite can be run independently under the embedded and DerbyNetClients
like other Derby test suites
> --------------------------------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-1133
>          URL: http://issues.apache.org/jira/browse/DERBY-1133
>      Project: Derby
>         Type: Improvement
>   Components: Test
>     Versions: 10.2.0.0
>     Reporter: Rick Hillegas
>     Assignee: Rick Hillegas
>  Attachments: bug1133.diff
>
> Right now the jdbc4 suite runs under the DerbyNetClient. However, under the covers, the
tests also run themselves against the embedded client. We should fix these tests so that the
whole suite can run just under DerbyNetClient or just under the embedded client.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message