[
https://issues.apache.org/jira/browse/DERBY-5300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129474#comment-13129474
]
Kristian Waagan commented on DERBY-5300:
----------------------------------------
Changed code to agree with the Javadoc param comment with revision 1185465.
This should take care of the Jenkins warning posted to derby-dev.
> Change derby.tests.trace to print the class as well as fixture name
> -------------------------------------------------------------------
>
> Key: DERBY-5300
> URL: https://issues.apache.org/jira/browse/DERBY-5300
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Assignee: Jayaram Subramanian
> Priority: Trivial
> Fix For: 10.9.0.0
>
> Attachments: classinfixture-Oct132011.diff,
> classinfixture-oct15.diff, classinfixture-stat-oct132011.out,
> classinfixture-stat-oct15.txt, classinfixture_Aug182011.txt,
> derby-5300-1a-print_jdbc_client.diff, svnstat-classinfixture.txt
>
>
> I was thinking it would be good for the test output with
> -Dderby.tests.trace=true to have the class name as well as the fixture as I
> think if I had a nickel for every time I grepped for a fixture name to find
> out what class it is in, I would have a pretty big piggy bank.
> It could print the full class name, like this:
> org.apache.derbyTesting.functionTests.tests.lang.SimpleTest.testBasicOperations
> used 844 ms .
> or strip off the org.apache.derbyTesting.functionTests for less output like:
> tests.lang.SimpleTest.testBugFixes used 6265 ms .
> Any preferences?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
