[ http://issues.apache.org/jira/browse/DERBY-949?page=all ]

Myrna van Lunteren updated DERBY-949:
-------------------------------------

    Attachment: DERBY-993_2006_03_19.stat
                DERBY-993_2006_03_19.diff

Refreshed patch (DERBY-993_2006_03_19.* ) after implementing patch v2 for 
DERBY-1058 the failure for HoldabilityTest.java (junit) 
went away for embedded, but I noticed with networkserver & db2jcc that I had 
used a different user and password
than what was being done in RunTest.java...Resulting in a 'schema does not 
exist' error in this test. 
So I corrected TestUtil.getConnection() for that framework.
Note, that test still failed for me with DerbyNet, I reported that in a comment 
to DERBY-1058.

I double checked all the references to TestUtil.getConnection, and only 
ShutdownDatabase ran with DerbyNet before, and shutdown
was not needing a schema, which is why no other tests failed.


> Clean up tests to use common method to get connections
> ------------------------------------------------------
>
>          Key: DERBY-949
>          URL: http://issues.apache.org/jira/browse/DERBY-949
>      Project: Derby
>         Type: Test
>   Components: Test
>     Versions: 10.2.0.0
>     Reporter: Deepa Remesh
>     Assignee: Myrna van Lunteren
>     Priority: Minor
>      Fix For: 10.2.0.0
>  Attachments: DERBY-949_2006_03_11.diff, DERBY-949_2006_03_11.stat, 
> DERBY-949_2006_03_13.diff, DERBY-949_2006_03_15.diff, 
> DERBY-993_2006_03_19.diff, DERBY-993_2006_03_19.stat
>
> Currently some tests have code to check the environment and get connection 
> using DriverManager/DataSource. This logic has been moved to 
> TestUtil.getConnection method. Cleanup tests to use this method. List of 
> tests:
> store/TestDurabilityProperty.java
> store/backupRestore1.java
> store/OnlineBackup tests
> lang/logStream.java
> lang/closed.java
> Also, add comment to ij.startJBMS method mentioning TestUtil.getConnection 
> method. See https://issues.apache.org/jira/browse/DERBY-907#action_12365954

-- 
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

Reply via email to