Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <2889687.1196338543263.JavaMail.jira@brutus>
Date: Thu, 29 Nov 2007 04:15:43 -0800 (PST)
From: "Ole Solberg (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-3161) Test the Derby Replication
 functionality introduced in DERBY-2872
In-Reply-To: <28795831.1193754770715.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-3161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ole Solberg updated DERBY-3161:
-------------------------------

    Attachment: ReplicationTestDesignSpec_0.22.html

Update ReplicationTestDesignSpec to match replication_funcspec_v7.html / DERBY-2872

> Test the Derby Replication functionality introduced in DERBY-2872
> -----------------------------------------------------------------
>
>                 Key: DERBY-3161
>                 URL: https://issues.apache.org/jira/browse/DERBY-3161
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>    Affects Versions: 10.4.0.0
>            Reporter: Ole Solberg
>            Assignee: Ole Solberg
>            Priority: Minor
>         Attachments: README.framework, README.properties, README.runningTests, README.testReplication, ReplicationTestDesignSpec.html, ReplicationTestDesignSpec_0.22.html
>
>
> This will be the top level JIRA for testing of the Derby Replication functionality [DERBY-2872].
> The tests will initially be developed using the "Proof of Concept" code submitted on DERBY-2872. 
> The "Proof of Concept" code is being published in parallel with the code committed on trunk. 
> The committed code will initially *not* allow execution of the replication functionality. 
> When the replication functionality is enabled on trunk the tests should be ready for use on trunk.
> For testing the replication functionality we will need 
> * a framework to 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,
>  - ...
> * 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.
>  - ...
> * to create new replication specific tests
>  -  Functional Testing (replication commands)
>   - Single Operation Tests: input variation, legal/illegal syntax/semantics. 
>   - Negative testing
>   - Operation Sequences
>   - Concurrency Semantics
>   - Application Profiles (# of master/slave servers, # of databases per master/slave,..)
>   - Provocative Operation Sequences and Operation Concurrency
>  - Non-Functional Testing
>   - Performance
>   - Stress, Resource Control
>   - Volume
>   - Scalability
>   - Resource Leakage
>   - Authentication
>   - Authorization
>   - ....

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.