[
https://issues.apache.org/jira/browse/DERBY-5300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097107#comment-13097107
]
Kristian Waagan commented on DERBY-5300:
----------------------------------------
I think we have no choice but to hardcode the most common class prefix if we
want to shorten the output.
However, you should make sure the prefix exists before trying to replace it,
for instance by using String.startsWith(COMMON_CLASS_PREFIX).
There's already a reference to the current configuration in runBare, you could
consider writing a new (non-static) method to print the trace string.
> 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
> Attachments: 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
