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 "Daniel John Debrunner (JIRA)" <de...@db.apache.org> on 2006/09/21 23:42:26 UTC
[jira] Resolved: (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
[ http://issues.apache.org/jira/browse/DERBY-1555?page=all ]
Daniel John Debrunner resolved DERBY-1555.
------------------------------------------
Fix Version/s: 10.2.1.0
10.3.0.0
Resolution: Cannot Reproduce
Changes have been made to store the configuration in a ThreadLocal and consistent access to that configuration.
> 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: http://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.0, 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira