Hi Frank,
[As a continuation of our IRC discussion]
The Jersey build process (which is executed by an internal Hudson
server) kicks off Jersey unit tests after each build and runs emma code
coverage [1]. The reports from emma allow us to measure the code
coverage of the unit tests and therefore improve the quality of the
project by knowing where we need to write more tests. Ideally i would
like to get the coverage of class, method, block and line to the 90% by
the time we reach 1.0.
Currently we are at:
class, % method, % block, % line, %
86% (239/277) 69% (1124/1622) 70% (19975/28518) 70% (4418.7/6288)
One big hole we have is coverage of the servlet container.
We are already running tests for the LW HTTP server and Grizzly in
process with unit tests, see:
com.sun.ws.rest.impl.container.{httpserver, grizzly}
I am guessing that we may be able to do something similar using Jetty
[2] in-process to boost the code-coverage of the Jersey servlet code.
Longer term it would be nice to move to a testing model whereby there is
unit test code using the client API, resources in another directory
and things could be tested different containers but that is longer term
thing...
Paul.
[1]
http://emma.sourceforge.net/
[2]
http://www.mortbay.org/
--
| ? + ? = To question
----------------\
Paul Sandoz
x38109
+33-4-76188109