We've made some progress already in
3.5 with 325 tests today from 276 tests in 3.4 (excluding to-be-released
publisher tests). One tool to help identify areas needing more testing
is eclemma. It only takes a few minutes to install and instrument tests
for running with eclemma. Here is a snapshot of the test coverage as of
Of course a coverage tool only tells
you that the code executed, not that it produced a correct result. Still,
we can't be testing correctness of code that's not being run at all in
our tests, so this coverage information is useful data.
Pascal Rapicault/Ottawa/IBM@IBMCA Sent by: p2-dev-bounces@xxxxxxxxxxx
09/12/2008 04:00 PM
Please respond to
P2 developer discussions <p2-dev@xxxxxxxxxxx>
[p2-dev] Next week is test authoring
One of our 3.5 theme is robustness. As a team we will
be taking next week to focus on writing unit tests.
Please join us in this effort to make p2 more dependable.
p2-dev mailing list