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] Created: (DERBY-3161) Test the Derby Replication functionality introduced in JIRA-2872
Date Tue, 30 Oct 2007 14:32:50 GMT
Test the Derby Replication functionality introduced in JIRA-2872
----------------------------------------------------------------

                 Key: DERBY-3161
                 URL: https://issues.apache.org/jira/browse/DERBY-3161
             Project: Derby
          Issue Type: Test
          Components: Test
            Reporter: Ole Solberg
            Assignee: Ole Solberg
            Priority: Minor


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.


Mime
View raw message