db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jayaram Subramanian (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5300) Change derby.tests.trace to print the class as well as fixture name
Date Sat, 20 Aug 2011 03:13:30 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jayaram Subramanian updated DERBY-5300:
---------------------------------------

    Issue & fix info: [Newcomer, Patch Available]  (was: [Newcomer])

> 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

        

Mime
View raw message