Hello,
I was wondering if someone could help me fix my surefire + cobertura
config. I only want one unit tests to run ONE time, but when I add the
cobertura-maven-plugin to the reporting section, it seems to trigger another
surefire:test phase. Any help?
Here is my current config:
build
As far as I am aware this is a known issue with no resolution.
Perhaps we can get the cobertura plugin to expose a report-only goal
and always do instrumentation for the tests. That was the approach I
used to use with ant.
On Tue, Mar 25, 2008 at 12:13 PM, Brian Relph [EMAIL PROTECTED] wrote:
beware. we have had tests that pass when instrumented with cobertura,
but fail when run normally. this is at least one reason why what you
are trying to do is a bad thing
- Stephen
Sent from my iPod
On 25 Mar 2008, at 16:13, Brian Relph [EMAIL PROTECTED] wrote:
Hello,
I was wondering if
Can you provide details for one or two of them? I'd like to know what
to look out for in the future.
Wayne
On 3/25/08, Stephen Connolly [EMAIL PROTECTED] wrote:
beware. we have had tests that pass when instrumented with cobertura,
but fail when run normally. this is at least one reason why
1. Tests that verify multiple thread behaviour. as cobertura will
effectively synchronize the threads in order to record the code
coverage.
2. Tests that verify performance.
3. One system had a bug whereby the server we were communicating with
would read the message header from the stream
And while ANT lets you make that mistake, I would encourage you to run the
tests twice and you will have greater assurance that your code is correct if
it passes instrumented and uninstrumented.
(Better assurance still is to run with BEA, IBM and Sun's JVMs on both
single core and multi-core
Ok; understood. So the correct course of action is to prominently
document why it is a bad idea to run tests solely on instrumented
code; I've seen this question come up once or twice. Unfortunately
this isn't the list to discuss that, is it?
On Tue, Mar 25, 2008 at 3:05 PM, Stephen Connolly
