You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <de...@db.apache.org> on 2006/03/20 19:33:58 UTC
[jira] Created: (DERBY-1133) Split jdbc4 tests so that the suite
can be run independently under the embedded and DerbyNetClients like other
Derby test suites
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
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
Re: [jira] Commented: (DERBY-1133) Split jdbc4 tests so that the suite can be run independently under the embedded and DerbyNetClients like other Derby test suites
Posted by Myrna van Lunteren <m....@gmail.com>.
On 3/21/06, Kristian Waagan (JIRA) <de...@db.apache.org> wrote:
>
> [
> http://issues.apache.org/jira/browse/DERBY-1133?page=comments#action_12371295]
>
> Kristian Waagan commented on DERBY-1133:
> ----------------------------------------
>
> It is a bit unclear to me why we need to have two different suites.
> Is it done to make it easier to keep the overview?
>
> Questions:
> 1) Are there specific reasons why the exclude mechanisms of the test
> harness are not used?
> Would it work to have only one suite, then add the (currently) two tests
> not supposed to be run under DerbyNetClient to
> 'suites/DerbyNetClient.exclude', with comments describing why they are
> excluded?
> 2) Is there a flag in the harness for excluding runs for JDK 1.5?
The functionTest harness' jvm skip mechanism is really a 'runwith<jvm>'
flag, which gets padded with the 'code' for each jvm version. So,
runwithjdk15=false should work to skip a test when running with jdk 1.5.
> 3) Should the jdbc40 suite be added to any other suites? (derbyall and
> derbynetclientmats)
>
> Great work fixing up the jdbc4 suite :)
>
> > 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
>
>
[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
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1133?page=all ]
Rick Hillegas updated DERBY-1133:
---------------------------------
Attachment: bug1133_rev2.diff
Hi Kristian,
Thanks for reviewing this patch. Here are responses to your review:
1) No good reason. I just didn't know about DerbyNetClient.exclude. Thanks for teaching me about this corner of our test harness fractal. I have eliminated the useless jdbc40_embeddedOnly suite and attached a second rev of the patch. This is much better.
2) I think Myrna answered this question affirmatively on derby-dev.
3) I agree that we want to wire jdbc40 into derbyall and derbynetclientmats once Anurag finishes work on DERBY-955.
> 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, bug1133_rev2.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
[jira] Reopened: (DERBY-1133) Split jdbc4 tests so that the suite
can be run independently under the embedded and DerbyNetClients like other
Derby test suites
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas reopened DERBY-1133:
----------------------------------
> 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: https://issues.apache.org/jira/browse/DERBY-1133
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.2.1.6
> Reporter: Rick Hillegas
> Assigned To: Rick Hillegas
> Fix For: 10.2.2.1
>
> Attachments: bug1133.diff, bug1133_3_cruft.diff, bug1133_rev2.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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1133) Split jdbc4 tests so that the suite
can be run independently under the embedded and DerbyNetClients like other
Derby test suites
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1133?page=comments#action_12371331 ]
Andrew McIntyre commented on DERBY-1133:
----------------------------------------
Hi Rick, just read the readme. If you want to keep the running of the jdbc40 tests to a single command, you could always set the suite files up like so:
jdbc40all.properties:
suites=jdbc40 jdbc40netclient
jdbc40netclient.properties:
framework=DerbyNetClient
suites=jdbc40
Then you just need to run jdbc40all to get both runs in a single command.
> 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, bug1133_rev2.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
[jira] Commented: (DERBY-1133) Split jdbc4 tests so that the suite
can be run independently under the embedded and DerbyNetClients like other
Derby test suites
Posted by "Kristian Waagan (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1133?page=comments#action_12371295 ]
Kristian Waagan commented on DERBY-1133:
----------------------------------------
It is a bit unclear to me why we need to have two different suites.
Is it done to make it easier to keep the overview?
Questions:
1) Are there specific reasons why the exclude mechanisms of the test harness are not used?
Would it work to have only one suite, then add the (currently) two tests not supposed to be run under DerbyNetClient to 'suites/DerbyNetClient.exclude', with comments describing why they are excluded?
2) Is there a flag in the harness for excluding runs for JDK 1.5?
3) Should the jdbc40 suite be added to any other suites? (derbyall and derbynetclientmats)
Great work fixing up the jdbc4 suite :)
> 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
[jira] Closed: (DERBY-1133) Split jdbc4 tests so that the suite can
be run independently under the embedded and DerbyNetClients like other
Derby test suites
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas closed DERBY-1133.
--------------------------------
Resolution: Fixed
> 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: https://issues.apache.org/jira/browse/DERBY-1133
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.2.1.6
> Reporter: Rick Hillegas
> Assigned To: Rick Hillegas
> Fix For: 10.2.2.1
>
> Attachments: bug1133.diff, bug1133_3_cruft.diff, bug1133_rev2.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.
-
You can reply to this email to add a comment to the issue online.
[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
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1133?page=all ]
Rick Hillegas updated DERBY-1133:
---------------------------------
Attachment: bug1133_3_cruft.diff
Additional patch bug1133_3_cruft.diff addresses Olav's comments about the vacuous StartTestConnection test. Test removed:
D java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\TestConnection.java
D java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\StartTestConnection.java
M java\testing\org\apache\derbyTesting\functionTests\suites\jdbc40.runall
> 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, bug1133_3_cruft.diff, bug1133_rev2.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
[jira] Commented: (DERBY-1133) Split jdbc4 tests so that the suite
can be run independently under the embedded and DerbyNetClients like other
Derby test suites
Posted by "Olav Sandstaa (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1133?page=comments#action_12371408 ]
Olav Sandstaa commented on DERBY-1133:
--------------------------------------
Hi Rick, thanks for fixing up the jdbc4 suite to make it possible to run using the standard test frameworks.
Some minor comments to your patch:
1. I think the StartTestConnection.java test could be removed from the test suite. This test tested that the previously used metods for creating a connection to the database worked. With your change to get the connections using ij.startJBMS, this test basically runs connection.close.
2. The following files can be removed (if you do 1.):
jdbc4/StartTestConnection.java
jdbc4/TestConnection.java
3. A tiny comment: the files for the jdbc4 test code was basically TAB free before your check-in.....
> 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, bug1133_rev2.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
[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
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-1133:
---------------------------------
Fix Version/s: 10.2.2.1
> 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: https://issues.apache.org/jira/browse/DERBY-1133
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.2.1.6
> Reporter: Rick Hillegas
> Assigned To: Rick Hillegas
> Fix For: 10.2.2.1
>
> Attachments: bug1133.diff, bug1133_3_cruft.diff, bug1133_rev2.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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1133) Split jdbc4 tests so that the suite
can be run independently under the embedded and DerbyNetClients like other
Derby test suites
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1133?page=comments#action_12371317 ]
Rick Hillegas commented on DERBY-1133:
--------------------------------------
Committed the second patch at subversion revision 387640.
> 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, bug1133_rev2.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
[jira] Resolved: (DERBY-1133) Split jdbc4 tests so that the suite
can be run independently under the embedded and DerbyNetClients like other
Derby test suites
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1133?page=all ]
Rick Hillegas resolved DERBY-1133:
----------------------------------
Resolution: Fixed
> 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, bug1133_3_cruft.diff, bug1133_rev2.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
[jira] Commented: (DERBY-1133) Split jdbc4 tests so that the suite
can be run independently under the embedded and DerbyNetClients like other
Derby test suites
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1133?page=comments#action_12371455 ]
Rick Hillegas commented on DERBY-1133:
--------------------------------------
Committed patch bug1133_3_cruft.diff at subversion revision 387925.
> 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, bug1133_3_cruft.diff, bug1133_rev2.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
[jira] Commented: (DERBY-1133) Split jdbc4 tests so that the suite
can be run independently under the embedded and DerbyNetClients like other
Derby test suites
Posted by "Anurag Shekhar (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1133?page=comments#action_12371439 ]
Anurag Shekhar commented on DERBY-1133:
---------------------------------------
> 3) I agree that we want to wire jdbc40 into derbyall and derbynetclientmats once Anurag finishes work on DERBY-955.
I think we can add jdbc40 in derbyall and derbynetclientmats now. The number of failures are down to 8 with jdk1.6
> 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, bug1133_rev2.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
[jira] Assigned: (DERBY-1133) Split jdbc4 tests so that the suite
can be run independently under the embedded and DerbyNetClients like other
Derby test suites
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1133?page=all ]
Rick Hillegas reassigned DERBY-1133:
------------------------------------
Assign To: Rick Hillegas
> 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
>
> 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
[jira] Closed: (DERBY-1133) Split jdbc4 tests so that the suite can
be run independently under the embedded and DerbyNetClients like other
Derby test suites
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1133?page=all ]
Rick Hillegas closed DERBY-1133:
--------------------------------
> 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, bug1133_3_cruft.diff, bug1133_rev2.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
[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
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ 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