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-4085) Improve testing of the in-memory back end
Date Sat, 28 Mar 2009 21:42:50 GMT

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

Kristian Waagan commented on DERBY-4085:
----------------------------------------

The MOG test failed on a SPARC machine (daily testing). I'll check if it happens again, and
investigate.

> 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
>            Assignee: Kristian Waagan
>             Fix For: 10.6.0.0
>
>         Attachments: buildbreak.diff, derby-4085-1a-basic_tests.diff, derby-4085-1a-basic_tests.stat,
derby-4085-1b-basic_tests.diff, derby-4085-2a-mog_func_test.diff, derby-4085-2a-mog_func_test.stat,
derby-4085-3a-enable_in_suitesAll.diff
>
>
> 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