db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4436) Refactor existing in-memory back end tests and add new tests for dropping database
Date Thu, 26 Nov 2009 12:53:39 GMT

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

Kristian Waagan commented on DERBY-4436:

The items above got addressed by patch 2b under DERBY-4428.

I'm not sure if DropWhileConnectingTest should be wired in to the suite yet, although it would
be good to run the test on a variety of machines / platforms. I'll reconsider test more and
reconsider when the access block mechanism is in place.

> Refactor existing in-memory back end tests and add new tests for dropping database
> ----------------------------------------------------------------------------------
>                 Key: DERBY-4436
>                 URL: https://issues.apache.org/jira/browse/DERBY-4436
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Test
>    Affects Versions:
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>             Fix For:
>         Attachments: derby-4436-1a-inmem_test_changes.diff, derby-4436-1a-inmem_test_changes.stat,
> To make it easier to write new in-memory back end tests, a class with a few convenience
methods would be helpful.
> I will add such a class, rewrite existing tests to use it (where appropriate) and finally
add some new tests for dropping in-memory databases.
> The tests will be disabled until the drop mechanism is implemented.

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

View raw message