Stefano Maestri [
http://community.jboss.org/people/maeste] created the discussion
"TestSuite - Coverage"
To view the discussion, visit:
http://community.jboss.org/message/573329#573329
--------------------------------------------------------------
Hi all,
From a coverage point of view our test suite is quite good. The
question is how much coverage is our target, but much more important which package/module
should have top priority in terms of test coverage.
ant cobertura
generate the coverage report into reports/cobertura/html/index.html. Please have a look to
get an idea of current status.
As you can see there we have a good coverage in our implementations, while we are not
testing a lot in an abstract way (using interfaces from javax) instead of stress the real
implementation. It's a choice of course: it makes test more readable and much more
linked to real implementation. Of course a more abstract tests would verify that we are
providing correctly what the specs require. Of course the TCK is doing that for us, so we
can leave tests stressing our own implementation safely.
Anyway in both cases, IMHO we should fine tune cobertura report to exclude from the
reports classes and interface we are not stressing for a choice, and maybe (I'm not
sure it's possible, I'm verifying) also method/classes that doesn't make sense
to stress. I'm thinking about for example to pojo geteer and setter that is dropping
down the finale coverage percentage wrongly.
let me know your thought and eventually the priority you would assign to not-well covered
packages.
best regards
S.
--------------------------------------------------------------
Reply to this message by going to Community
[
http://community.jboss.org/message/573329#573329]
Start a new discussion in IronJacamar Development at Community
[
http://community.jboss.org/choose-container!input.jspa?contentType=1&...]