Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Message-ID: <2081347645.1137445100284.JavaMail.jira@ajax.apache.org>
Date: Mon, 16 Jan 2006 21:58:20 +0100 (CET)
From: "George Harley (JIRA)" <jira@apache.org>
To: harmony-dev@incubator.apache.org
Subject: [jira] Created: (HARMONY-31) Move peformance timing of unit tests
 into a decorator class.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Move peformance timing of unit tests into a decorator class.
------------------------------------------------------------

         Key: HARMONY-31
         URL: http://issues.apache.org/jira/browse/HARMONY-31
     Project: Harmony
        Type: Improvement
    Reporter: George Harley
 Assigned to: Geir Magnusson Jr 
    Priority: Minor


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.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira