we've had tests that pass when run with cobertura and fail without. so
I always recommend running twice. additionally we've had tests that
pass normally, but fail with cobertura. in both cases the root cause
analysis was a bug in our code. run them twice and if either run fails
you likely have a bug
(the exception is sometimes a cobertura test can validly fail without
the root cause being a bug. for example, performance tests, or tests
that try to force a particular synchronization scenario)
Sent from my iPod
On 1 Aug 2008, at 20:23, "Blake Martin" <[EMAIL PROTECTED]> wrote:
Currently, our tests are the longest-running part of our Maven
lifecycle and
we'd like to have Cobertura fail if a test case fails so that
Surefire isn't
needed.
Is it possible to have Cobertura fail when a test fails? Normally,
it only
fails if one of its conditions aren't met (e.g., line coverage).
Would there be any ramifications, or is this a sane idea?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
