In my experience you have:
* a 40% chance of the failure being a bad test
* a 40% chance of the failure being a bug in your production code
* a 20% chance of the failure being a side-effect of instrumentation
which invalidates the test
If you and all the developers in your team cannot explai
Thank you for pointing out to that discussion. Even though I don't agree
completely - if running the coverage tool Cobertura changes the status of
your tests, I'd say that in most likelihood the problem should be cobertura
and not your code or your test - I might live with running the cobertura
go
http://maven.40175.n5.nabble.com/Cobertura-and-Surefire-td3338334.html
On 26 September 2011 15:46, Miguel Almeida wrote:
> I am using the cobertura plugin to create test coverage reports, and
> surefire-report for test reports. See [1] for my maven 3 configuration on
> the top-tier of a multi-mod
I am using the cobertura plugin to create test coverage reports, and
surefire-report for test reports. See [1] for my maven 3 configuration on
the top-tier of a multi-module project.
The goals I am running are:
Surefire: surefire-report:report
Cobertura: cobertura:cobertura
Is it possible to run
