db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "CodeCoverageWithEMMA" by MohamedNufail
Date Thu, 19 Jul 2012 05:48:56 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The "CodeCoverageWithEMMA" page has been changed by MohamedNufail:
http://wiki.apache.org/db-derby/CodeCoverageWithEMMA?action=diff&rev1=7&rev2=8

Comment:
Mention EMMA's limitation with thrown exceptions

  
  During the testruns, data on coverage is written to a file named coverage.ec, also located
in the directory with the test logs. After the tests are finished, reports are produced using
the data located in the coverage.em and coverage.ec files and linked to your source code (if
you compiled with debug=true). The reports are named coverage.txt, coverage.xml and coverage.html,
and all contain the same information.
  
+ {{{#!wiki note
+ '''Note'''
+ 
+ EMMA marks a block as covered, only if that block exits normally. Thus if a block terminates
due to a thrown exception, it is not marked as covered. [[http://emma.sourceforge.net/faq.html#q.blockcoverage]].
+ So, although coverage report indicates a block of code as uncovered, it might have been
invoked.
+ }}}
+ 
  = Ant Targets =
  || '''ant target''' || '''Comments''' ||
  || `emma-all` || Instruments the Derby jar files with EMMA and runs `junit-all` automatically
setting the classpath to the jar files instrumented with EMMA. When the tests are finished,
a code coverage report is produced in three copies (txt, html and xml) in the directory where
the test logs are placed. ||

Mime
View raw message