[
https://issues.apache.org/jira/browse/DERBY-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572461#action_12572461
]
Kristian Waagan commented on DERBY-2667:
----------------------------------------
Well, maybe I misunderstood, but if you overwrite, it will be because you run
the test / suite again, won't it?
The naming logic of the failure folder seems to consist of something related
to connection / JDBCClient, the test class and the test method.
So as an example:
./Embedded_40/BlobClob4BlobTest/testBlobAfterClosingConnection/stacktrace.out
I just assumed there could be only one exception thrown for a single run (in
runBare), but maybe my comment above regarding overwriting was a bit confusing.
I haven't actually studied the logic for the failure folder naming, but maybe
someone else has some info?
But of course, appending to the file might still be a good thing to do, or
maybe a timestamp or something in the filename?
(if you tend to run the tests from the same location over and over again when
testing/debugging)
> Create more robust junit TestRunner for running derby tests
> ------------------------------------------------------------
>
> Key: DERBY-2667
> URL: https://issues.apache.org/jira/browse/DERBY-2667
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.3.1.4
> Reporter: Kathey Marsden
> Priority: Minor
> Attachments: derby-2667-WriteExceptionsToFileAsTheyHappen.diff,
> DERBY-2667_diff_02_06.txt, DERBY-2667_diff_02_15.txt,
> DERBY-2667_diff_02_21.txt, DERBY-2667_diff_2_19.txt,
> DERBY-2667_stat_02_06.txt, DERBY-2667_stat_02_15.txt,
> DERBY-2667_stat_02_19.txt, DERBY-2667_stat_02_21.txt,
> JUnitMethodTrace.diff.txt, JUnitMethodTrace_Extra.diff.txt, MemRunner.java,
> TimeRunner.java
>
>
> Provide a more full featured TestRunner for Derby testing.
> junit.textui.TestRunner is not very robust. It does not for example print the
> tests as they run or print chained exceptions, create separate files for the
> full report and just failures. It would be great to have a standardized
> TestRunner that everyone uses. Perhaps someone already has one that they
> would like to contribute as a starter.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
