DO NOT REPLY [Bug 32722] New: - Test coverage analysis

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32722>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32722

           Summary: Test coverage analysis
           Product: Log4j
           Version: 1.3alpha
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Other
        AssignedTo: log4j-dev@logging.apache.org
        ReportedBy: carnold@houston.rr.com


The attach patch modifies tests/build.xml to add "coverageReport" target which
will use Clover (http://www.cenqua.com/clover) to generate a coverage report of
the log4j code exercised while running all tests.  To run this target,
clover.jar must be on the classpath.  ASF committers can check out a ASF
licensed Clover from the committers/donated-licenses/clover CVS module.

There were a few gotcha, the ASF licensed clover is restricted to a fixed set of
package hierarchies (org.apache, com.example, java) which does not cover the
package names used in the examples.  To work around this, the parentBuild target
was modified to call all dependencies of log4j's build target except build.examples.

PatternParserTest.test14 appears to be tempermental.  It will pass on a clean
build, but will fail at other times.  To work around this, I added a property
"test-haltonerror" which controls whether JUnit tests halt on error.  When doing
a coverage analysis, they do not fail on error.

A sample coverage report is currently available at
http://home.houston.rr.com/curta/coverage.tar.gz.  Untar and view
coverage/index.html to see coverage report.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org