You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Dan Fabulich (JIRA)" <ji...@codehaus.org> on 2007/12/10 18:48:57 UTC

[jira] Closed: (SUREFIRE-393) Measure test coverage for surefire, including ITs

     [ http://jira.codehaus.org/browse/SUREFIRE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Fabulich closed SUREFIRE-393.
---------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.4)

Measured coverage by hand; results available here: 

http://docs.codehaus.org/download/attachments/35422245/surefire-clover-2007-12-10.zip

> Measure test coverage for surefire, including ITs
> -------------------------------------------------
>
>                 Key: SUREFIRE-393
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-393
>             Project: Maven Surefire
>          Issue Type: Sub-task
>            Reporter: Dan Fabulich
>
> I've written a bunch of new integration tests for Surefire.  It's getting tested, at least somewhat.  But what's still not getting tested?  We'd need to set up some kind of tool that could instrument the classes while allowing out-of-proc tests (the integration tests) to run against them, and then look at the coverage to see where we are.
> I'm not sure how to do that right now.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira