[
https://issues.apache.org/jira/browse/DERBY-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ole Solberg updated DERBY-3162:
-------------------------------
Attachment: derby-3162.3-v4.stat.txt
derby-3162.3-v4.diff.txt
Patch 3162.3-v4 for testing replication:
- Added tests for checking replication command behaviour in
different states of replication.
(ReplicationRun_Local_StateTest_part*)
- Added 'ReplicationSuite.suite()' at end of .../suites/All.java.
That is, the replication test will be run as part of suites.All.
- replication tests now uses 'SecurityManagerSetup.noSecurityManager()'.
- changed replication test trace output to use Utils.DEBUG().
Can be turned on by '-Dderby.tests.repltrace=true'.
> Create a framework for replication tests
> ----------------------------------------
>
> Key: DERBY-3162
> URL: https://issues.apache.org/jira/browse/DERBY-3162
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Affects Versions: 10.4.0.0
> Reporter: Ole Solberg
> Assignee: Ole Solberg
> Priority: Minor
> Attachments: derby-3162.1-v1.diff.txt, derby-3162.2-v2.diff.txt,
> derby-3162.2-v2.stat.txt, derby-3162.3-v1.diff.txt, derby-3162.3-v1.stat.txt,
> derby-3162.3-v2.diff.txt, derby-3162.3-v2.stat.txt, derby-3162.3-v3.diff.txt,
> derby-3162.3-v3.stat.txt, derby-3162.3-v4.diff.txt, derby-3162.3-v4.stat.txt
>
>
> Handle
> - starting and stopping Derby servers to have the master and slave
> replication roles,
> - doing administrative commands like startreplication, startslave,
> stopreplication, failover,
> - performing consistency checks on the slave vs. the master,
> - running load clients against master and slave in the various states of
> replication,
> - provoking error situations on master and slave, and network,
> - ...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
