[
https://issues.apache.org/jira/browse/DERBY-4085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan closed DERBY-4085.
----------------------------------
Resolution: Fixed
Closing this issue, as the initially planned work has been completed.
Testing can always be improved, and this work should continue outside of this
Jira. Note especially the issue logged to stabilize the MogTest.
> 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.1.1
> 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,
> derby-4085-4a-improved_assertion_reporting.diff,
> derby-4085-5a-report_seed_on_failure.diff, derby-4085-6a-fixed_seed.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.
