db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5382) Convert existing harness recovery tests to JUnit tests
Date Tue, 28 Feb 2012 20:07:46 GMT

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

Myrna van Lunteren commented on DERBY-5382:
-------------------------------------------

Thank you Kristian for reviewing the patch.

I committed the change with revision 1294805
This was the commit comment:
DERBY-5382; Convert existing harness recovery tests to JUnit tests
  Adjusting test to create the database in the first launched method.
  Modifying TestConfiguration to this end to look for a property
    'derby.tests.defaultDatabaseName'
  which can get passed on in a new BaseTestCase method
  ((assertLaunchedJUnitTestMethod(String, String)).

I wasn't familiar with the -m option either, that was part of Siddharth's original patch.
It was new with junit 3.8.2.
I found it hard to find information about this functionality, so I ran some experiments, and
it seems to me the -m option does *not* run the suite method, only the constructor.

                
> 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

        

Mime
View raw message