db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ole Solberg (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:57:50 GMT

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

Ole Solberg commented on DERBY-3163:
------------------------------------

Thank you for looking into this Kristian!

The patch is not ready for commit as you suspected.

I think the best approach would be to get derby-2807-v1.diff.txt (in DERBY-2807) committed
first, which would give a smaller and cleaner patch for DERBY-3163.


The System.out.printlns are not supposed to be there, they are leftovers from my initial testing
against the replication "Proof of concept" code.


> 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