[
https://issues.apache.org/jira/browse/DERBY-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568274#action_12568274
]
Daniel John Debrunner commented on DERBY-3163:
----------------------------------------------
Is there a write up that explains what the changes are? Several of the new
methods in TestConfiguration have no comments so I have no idea what their
purpose is.
The switch to a static decorate() method in some of the tests is confusing. Is
there some explanation for why this is required, is this a pattern required for
all tests?
> Derby JUnit test framework adaptions to run existing tests against replicated
> databases
> ---------------------------------------------------------------------------------------
>
> Key: DERBY-3163
> URL: https://issues.apache.org/jira/browse/DERBY-3163
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Affects Versions: 10.4.0.0
> Reporter: Ole Solberg
> Assignee: Ole Solberg
> Priority: Minor
> Attachments: derby-3163.1-v1.diff.txt, derby-3163.1-v2.diff.txt,
> derby-3163.1-v3.diff.txt, derby-3163.2-v1.diff.txt, derby-3163.2-v2.diff.txt,
> derby-3163.2-v3.diff.txt
>
>
> Extensions to run existing Apache Derby tests (old test harness tests
> ("derbyall" kind)
> and junit tests)
> This requires
> - Running existing tests against already started servers on "non-localhost"
> machines.
> - verificationclients checking slave vs. master.
> - ...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
