[
https://issues.apache.org/jira/browse/DERBY-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-2667:
-----------------------------------
Attachment: derby-2667-WriteExceptionsToFileAsTheyHappen.diff
'derby-2667-WriteExceptionsToFileAsTheyHappen.diff' is a patch that makes
BaseTestCase also write the stack trace to file when an error occurs. The file
will be written to the same location as derby.log, and currently it will
overwrite any existing file.
I have only tested it lightly, but it seems to work fine for me. Is it
something we could consider adding?
The reason why I wrote it, is that it is sometimes very annoying to wait for
suites.All to finish when you get an error/failure on the first line of dots...
> 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.
