db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-1555) API for configuration information in Derby's JUnit tests should through instance methods of the base classes, not static methods and static fields
Date Tue, 20 Mar 2007 23:39:32 GMT

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

Daniel John Debrunner closed DERBY-1555.
----------------------------------------


> API for configuration information in Derby's JUnit tests should through instance methods
of the base classes, not static methods and static fields
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1555
>                 URL: https://issues.apache.org/jira/browse/DERBY-1555
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>            Reporter: Daniel John Debrunner
>         Assigned To: Daniel John Debrunner
>             Fix For: 10.2.1.6, 10.3.0.0
>
>         Attachments: derby-1555-removecomment.diff
>
>
> The heavy use of static state information in the existing Derby (non-Junit) harness was
a major mistake, it should not be repeated in the Junit model.
> It should be changed before too many tests are written.
> A static configuration will limit the ability for the tests to be flexible and have different
instances running with different configurations,
> a instance based scheme will be more flexible.
> This change will just change the api, the current implementation of  a single static
configuration will remain but be hidden within the base-classes.

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


Mime
View raw message