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 "Kathey Marsden (JIRA)" <ji...@apache.org> on 2008/07/25 19:33:32 UTC

[jira] Updated: (DERBY-2505) Convert derbynet/testij.java to JUnit

     [ https://issues.apache.org/jira/browse/DERBY-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden updated DERBY-2505:
----------------------------------

    Component/s: Test

> Convert derbynet/testij.java to JUnit
> -------------------------------------
>
>                 Key: DERBY-2505
>                 URL: https://issues.apache.org/jira/browse/DERBY-2505
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>    Affects Versions: 10.3.1.4
>            Reporter: Andrew McIntyre
>            Assignee: Andrew McIntyre
>            Priority: Minor
>             Fix For: 10.3.1.4
>
>         Attachments: derby-2505-jarfix.diff, derby-2505-v1.diff
>
>
> In the process of converting this test, I realized we needed an way to run ij tests that would work with multiple connections. So, I made an IjTestCase that runs a script through ij's main method, redirects the output to a file, and then compares the file to a canon.
> Attaching a patch for this issue which does that. The test creates several databases during its run. Should the JUnit wrappers for ij tests be cleaning these up, or will these get cleaned up later automatically?

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