db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Houx Zhang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-5084) convert ijConnName.sql to a ScriptTest junit test
Date Sat, 19 Mar 2011 14:20:29 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008775#comment-13008775

Houx Zhang commented on DERBY-5084:

Thanks very much, Kathey. Your advice is helpful.

ScriptTestCase(String script, boolean useSystemProperties) constructor can work as you advised.
With setting it true, the System Properties are set up OK.

However, my junit test case can not pass, while the harness.RunTest can pass. I have attached
the file "ijConnName-1.tmp", which is created by harness.RunTest, and the file "ijConnName-1.out",
created by my junit test case. In the file "ijConnName-1.out", we can see, 

show connections;
CONNECTION0* - 	jdbc:derby:wombat
CONNONE - 	jdbc:derby:wombat

A connection with the name "CONNECTION0" has been created before the testing. Maybe it's the
connection created in BaseJDBCTestCase, however, I have tried to override the setup() method
to close the connection, but it can not work, too.

How can I go ahead? I doubt this .sql is not fit to converted into a junit test case, in other
word, harness is it's only way to work. 

Comments are welcome. Thanks!

> convert ijConnName.sql to a ScriptTest junit test
> -------------------------------------------------
>                 Key: DERBY-5084
>                 URL: https://issues.apache.org/jira/browse/DERBY-5084
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>            Reporter: Myrna van Lunteren
>            Priority: Trivial
>              Labels: derby_triage10_8
>         Attachments: DERBY-5084.patch
> In DERBY-3089 it is mentioned that tools/ijConnName.sql should get converted to a junit
test, probably using ScriptTest.
> Making a separate issue so that that issue can be closed.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message