harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Hindess (JIRA)" <j...@apache.org>
Subject [jira] Closed: (HARMONY-31) Move peformance timing of unit tests into a decorator class.
Date Thu, 18 Jun 2009 09:59:07 GMT

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

Mark Hindess closed HARMONY-31.

I don't recall any howls of protest so I'm closing this one.

> Move peformance timing of unit tests into a decorator class.
> ------------------------------------------------------------
>                 Key: HARMONY-31
>                 URL: https://issues.apache.org/jira/browse/HARMONY-31
>             Project: Harmony
>          Issue Type: Improvement
>          Components: Classlib
>            Reporter: George Harley
>            Assignee: Geir Magnusson Jr
>            Priority: Minor
>         Attachments: PerfDecorator.java
> There has been some low-level discussion on the dev mailing list recently about the inclusion
of performance-related logging code near the top of a unit test class inheritance hierarchy
(see com.openintel.drl.security.test.PerformanceTest in the HARMONY-16 contribution). This
particular issue suggests an alternative way of adding in timing code but without making it
the responsibility of the unit tests themselves and without the need to introduce a class
in the inheritance hierarchy. 
> The basic approach is to exploit the junit.extensions.TestDecorator type in the JUnit
API to add in timing behaviour before and after each test method runs. This will be demonstrated
with some simple sample code. 

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

View raw message