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 "Kristian Waagan (JIRA)" <ji...@apache.org> on 2007/05/24 12:30:16 UTC

[jira] Closed: (DERBY-1122) Improve base JUnit testing classes

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

Kristian Waagan closed DERBY-1122.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 10.3.0.0

The state of the JUnit base classes has reached an acceptable maturity level. I'm closing this issue, because I think issues related to the JUnit test classes are better tracked by separate Jiras.

> Improve base JUnit testing classes
> ----------------------------------
>
>                 Key: DERBY-1122
>                 URL: https://issues.apache.org/jira/browse/DERBY-1122
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>    Affects Versions: 10.3.0.0
>            Reporter: Kristian Waagan
>            Priority: Minor
>             Fix For: 10.3.0.0
>
>
> This is a placeholder issue for keeping track of improvements and bugs for base JUnit testing classes.
> The first submission is very minimalistic and will need to be extended.
> There are currently 4 base classes, all located in '...derbyTesting.functionTests.util':
> JDBCClient
> TestConfiguration
> BaseTestCase
> BaseJDBCTestCase

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