db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3834) Convert derbynet/runtimeinfo to JUnit
Date Thu, 14 Aug 2008 23:21:44 GMT

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

Myrna van Lunteren commented on DERBY-3834:

I ran the test, but the first time, it fails for me. 
If I run it again without cleaning up the dir, it passes.
Maybe some of the details regarding sessions and statements are different when you first create
a database...

So maybe you can wrap the test in a singleUseDecorator and adjust the expected output to what
it would be when there are no pre-existing databases.

Other comments:
- I'd like  it better if you could avoid using ExecProcUtil.execCmdDumpResults...
- There is a property, derby.tests.debug, which can be set if someone wants to debug a test.
I suggest you remove the boolean 'print' and instead, in the method 'print()' use org.apache.derbyTesting.junit.println'
rather than System.out.println.  That way, no change of the code is needed to debug the test.

> Convert derbynet/runtimeinfo to JUnit
> -------------------------------------
>                 Key: DERBY-3834
>                 URL: https://issues.apache.org/jira/browse/DERBY-3834
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>    Affects Versions:
>            Reporter: Erlend Birkenes
>            Assignee: Erlend Birkenes
>            Priority: Minor
>             Fix For:
>         Attachments: Derby-3834_1.diff

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message