[
https://issues.apache.org/jira/browse/DERBY-3556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581636#action_12581636
]
Kathey Marsden commented on DERBY-3556:
---------------------------------------
With the patch the fixture name prints twice. e.g.
+ java -Xmx512M -Xms512M -Dderby.tests.trace=true
-DderbyTesting.oldReleasePath=C:/kmarsden/svnreleases/jars junit.textu
i.TestRunner org.apache.derbyTesting.functionTests.tests.lang.SimpleTest
.
testBasicOperations started.
testBasicOperations used 953 ms .
testBugFixes started.
testBugFixes used 6172 ms .
testBasicOperations started.
testBasicOperations used 2313 ms .
testBugFixes started.
testBugFixes used 6187 ms
Time: 53.266
I think it would be better to just continue to print the name once, but just
print it before the test runs, so we would still have the same output.
testBasicOperations used 953 ms .
but it would just print the name before the run and the "used x ms" after
the test runs. Then we would just have a pause before the used portion of the
line prints, or in the case of a hang of course it would never print, but we
would know what test it is on.
> change derby.tests.trace property to print the name of the test before it
> runs it
> ---------------------------------------------------------------------------------
>
> Key: DERBY-3556
> URL: https://issues.apache.org/jira/browse/DERBY-3556
> Project: Derby
> Issue Type: Improvement
> Components: Newcomer, Test
> Affects Versions: 10.5.0.0
> Reporter: Kathey Marsden
> Priority: Trivial
> Attachments: derby-3556.patch
>
>
> If a test hangs for some reason it is useful to know what test is running
> when the hang occurs. It would therefore be good if the derby.tests.trace
> property printed the test name before it ran the test instead of after.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
