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] Updated: (DERBY-4085) Improve testing of the in-memory back end
Date Wed, 11 Mar 2009 12:23:50 GMT

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

Kristian Waagan updated DERBY-4085:
-----------------------------------

    Attachment: derby-4085-1a-basic_tests.stat
                derby-4085-1a-basic_tests.diff

Patch 1a adds a very simple boot test and the backup / modify / restore test. The tests haven't
been added to suites.All or the ant targets yet.
Patch ready for review.

I'm not sure if we should continue to connect to the databases manually, or if it should be
possible to add a decorator or set an option to use a specific subSubProtocol.

> Improve testing of the in-memory back end
> -----------------------------------------
>
>                 Key: DERBY-4085
>                 URL: https://issues.apache.org/jira/browse/DERBY-4085
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Test
>    Affects Versions: 10.5.0.0
>            Reporter: Kristian Waagan
>         Attachments: derby-4085-1a-basic_tests.diff, derby-4085-1a-basic_tests.stat
>
>
> The in-memory back end should be tested as part of the standard regression tests.
> The following is a good start:
>  o simple create / boot test
>  o create in-memory db, backup, restore with default storage engine, modify, restore
with createFrom into memory again
>  o add the functional test(s) written by Cheng
>  o more unit tests
> On a longer term, we should consider to add the possibility to run all or a subset of
the general regression tests with the in-memory back end.

-- 
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