db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ole Solberg (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2667) Create more robust junit TestRunner for running derby tests
Date Thu, 07 Jun 2007 13:03:25 GMT

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

Ole Solberg updated DERBY-2667:
-------------------------------

    Attachment: JUnitMethodTrace_Extra.diff.txt
                JUnitMethodTrace.diff.txt

In the regression testing and also in more experimental testing I have felt a need for more
details in the JUnit test reports - e.g. to convince myself that a test was really executed.
I have done this by modifying 'java/testing/org/apache/derbyTesting/junit/BaseTestCase.java'
to print the test method name, and have also included a printout of the time (in ms.) used
by the test method.
I use "-Dderby.tests.trace=true" to turn this on.
  Attachement JUnitMethodTrace.diff.txt.

'java/testing/org/apache/derbyTesting/unitTests/junit/FormatableBitSetTest.java' currently
uses JUnit TestCase and would thus not give the desired extra information: The JUnitMethodTrace_Extra.diff.txt
patch changes that by using 'BaseTestCase'.
  Attachement JUnitMethodTrace_Extra.diff.txt 




Example output:
.
testSetCharacterStream used 200ms .
testGetAsciiStream used 664ms .
testGetCharacterStream used 638ms .
testGetCharacterStreamWithUnicode used 817ms .
testTriggersWithClobColumn used 2453ms .
testGetSubString used 431ms E.
testGetSubStringWithUnicode used 855ms .
testPositionString used 713ms .
testPositionStringWithUnicode used 739ms .
testPositionClob used 4204ms .
testPositionClobWithUnicode used 4832ms .
testSmallClobFields used 82ms .
testGetClobFromIntColumn used 302ms F.
testSetClobToIntColumn used 412ms F.
testRaisingOfExceptionsClob used 523ms F.
testSetClob used 1116ms .
testPositionAgressive used 9073ms .
testClobAfterClose used 587ms .
testLockingClob used 60695ms .
testLockingWithLongRowClob used 60178ms .
.
.
.

> Create more robust junit  TestRunner for running derby tests
> ------------------------------------------------------------
>
>                 Key: DERBY-2667
>                 URL: https://issues.apache.org/jira/browse/DERBY-2667
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.3.0.0
>            Reporter: Kathey Marsden
>            Priority: Minor
>         Attachments: JUnitMethodTrace.diff.txt, JUnitMethodTrace_Extra.diff.txt, MemRunner.java,
TimeRunner.java
>
>
> Provide a more full featured TestRunner for Derby testing.
> junit.textui.TestRunner is not very robust. It does not for example print the tests as
they run or print chained exceptions, create separate files for the full report and just failures.
  It would be great to have a standardized TestRunner that everyone uses.  Perhaps someone
already has one that they would like to contribute as a starter.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message