[
https://issues.apache.org/jira/browse/DERBY-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erlend Birkenes updated DERBY-1764:
-----------------------------------
Attachment: DERBY-1764_4.diff
Version 4.
1. StressTest50x59 now only do the embedded run.
2. Had to change the whole way errors was handled so that the derby.log is
copied to the fail directory on failure. I think failures are handled much
better now. The first Exception in a fixture is thrown for BaseTestCase and
JUnit to deal with instead of messing around with the TestResult . Because of
the threads other exceptions can happen after this, but they are discarded and
not reported as failures by JUnit (They can be found in the log of course). So
now there is only one failure per fixture, where before there could be many and
that didn't make much sense.
-Erlend
> 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
>
>
> 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.
