[
https://issues.apache.org/jira/browse/DERBY-5300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-5300:
-----------------------------------
Attachment: derby-5300-1a-print_jdbc_client.diff
I'd prefer a shorter version, such that the lines stays below 80 chars in most
cases (looks better in terminal windows with default size).
Additionally, I'd like to see a hint telling me if the test ran with the
embedded or the client driver (something along the lines added by the attached
patch 1a):
(emb)testGetStreamsExceptionOnClose used 663 ms F.
(emb)testSetMaxFieldSizeLarge used 317 ms .
(net)testInsertData used 21 ms .
(net)testBinaryStreamProcessing used 18 ms .
I chose 'emb' and 'net' because their lengths are equal, but maybe some find
'net' a bit confusing due to the old DB2 driver? Could also do '(E)' and '(C)'
or something.
Ideally, I'd like to see this hint in the error/failure report as well, but I'm
not sure if that can be done easily enough to be worth the effort (?).
> 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
> 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
