db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3163) Derby JUnit test framework adaptions to run existing tests against replicated databases
Date Mon, 12 Nov 2007 13:03:52 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541766
] 

Kristian Waagan commented on DERBY-3163:
----------------------------------------

I had a look at 'derby-3163.1-v1.diff.txt', and saw that there are quite some lines commented
out and comments indicating more changes have to be done before the test framework is ready
for the task. Also, are the System.out.printlns supposed to be in there?

Is the patch intended for commit?
Can you say something about what has to be done to push this issue to completion?


thanks,

> 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.2-v1.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.


Mime
View raw message