Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Tue, 28 Feb 2012 13:53:46 +0000 (UTC)
From: "Myrna van Lunteren (Updated) (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <420141823.27993.1330437226911.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <432204892.36913.1313308947157.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (DERBY-5382) Convert existing harness recovery
 tests to JUnit tests
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Myrna van Lunteren updated DERBY-5382:
--------------------------------------

    Attachment: DERBY-5382_2.diff

Attaching a new patch which tries to address creating the database within the first forked test, to more closely resemble the original test case.

Because we're forking a new process, the only way I could think of doing this is by making a change to the default TestConfiguration to check for a system property specifying the database.

Please review.
                
> Convert existing harness recovery tests to JUnit tests
> ------------------------------------------------------
>
>                 Key: DERBY-5382
>                 URL: https://issues.apache.org/jira/browse/DERBY-5382
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>            Reporter: Siddharth Srivastava
>            Assignee: Siddharth Srivastava
>             Fix For: 10.9.0.0
>
>         Attachments: DERBY-5382.diff, DERBY-5382_2.diff, d5382.patch
>
>
> Existing harness recovery tests need to be converted to JUnit tests. A framework as designed in Derby-4249 can be used for this purpose.
> Tests to be converted:
> a) oc_rec1
> b) oc_rec2
> c) oc_rec3
> d) oc_rec4
> These recovery tests run in coordination. The test oc_rec1 creates a table, inserts and then deletes rows from it and commit it which is followed by a series of insertion of rows in the existing table in oc_rec2, oc_rec3 and oc_rec4. The tests oc_rec2 and oc_3 also create table and insert, delete, compress rows in it and leave the table thus produced in committed or uncommitted state which is tested by the next corresponding test (oc_rec3 for oc_rec2, oc_rec4 for oc_rec3) for recovery.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira