[
https://issues.apache.org/jira/browse/DERBY-4085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-4085:
--------------------------------------
Attachment: buildbreak.diff
Here's a patch that fixes the build break. Since BasicInMemoryDbTest uses
DriverManager, it must be compiled against java14compile.classpath. The problem
is only seen if jsr169compile.classpath points to JSR-169 + Foundation
libraries.
Committed revision 753279.
When this test is enabled as part of a suite, we should make sure it's not run
on Java ME. Or we should change the test so that it doesn't need DriverManager,
in which case it should run on Java ME too, and the change that I just
committed should be reverted.
> 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
> Attachments: buildbreak.diff, derby-4085-1a-basic_tests.diff,
> derby-4085-1a-basic_tests.stat, derby-4085-1b-basic_tests.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.
