[
https://issues.apache.org/jira/browse/DERBY-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629276#action_12629276
]
Knut Anders Hatlen commented on DERBY-1764:
-------------------------------------------
Perhaps DatabasePropertyTestSetup is better. And it probably needs to have
staticProperties=true so that it reboots the engine and reads the properties.
Also change System.getProperties() -> new Properties() in embeddedSuite(). (Or
perhaps we can skip setting the properties in that method since we've already
set them in suite().)
> Rewrite stress.multi as a JUnit test
> ------------------------------------
>
> Key: DERBY-1764
> URL: https://issues.apache.org/jira/browse/DERBY-1764
> Project: Derby
> Issue Type: Test
> Components: Test
> Reporter: Knut Anders Hatlen
> Assignee: Erlend Birkenes
> Attachments: derby-1764-3a-whitespace_changes.diff,
> derby-1764-derby.log, DERBY-1764-Review.diff, DERBY-1764-V1.diff,
> DERBY-1764-V2.diff, DERBY-1764_4.diff, DERBY-1764_5.diff, DERBY-1764_6.diff,
> derby-1764_use_System_PropertySetup_diff.txt
>
>
> Currently, stress.multi consists of a number of sql scripts that are run in
> ij. It often fails with cryptic error messages, and since it uses ij, there
> is often no stack trace. It would be very useful to rewrite the test in JUnit
> so that we can get better error messages and stack traces when it fails.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
