You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Jayaram Subramanian (JIRA)" <ji...@apache.org> on 2011/07/20 19:16:58 UTC
[jira] [Assigned] (DERBY-5300) Change derby.tests.trace to print
the class as well as fixture name
[ https://issues.apache.org/jira/browse/DERBY-5300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jayaram Subramanian reassigned DERBY-5300:
------------------------------------------
Assignee: Jayaram Subramanian
> 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: derby-5300-1a-print_jdbc_client.diff
>
>
> 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