the first thing that people complain about maven and cobertura is when they generate the project site their tests always run twice... how do i make them run just once...
to which i always reply: run them twice or you'll miss concurrency related bugs 2008/9/25 Edelson, Justin <[EMAIL PROTECTED]> > I agree that tests should be able to be run any number of times. And in > fact "mvn clean test test test test" works fine. It's "mvn > cobertura:cobertura" which doesn't - and that only runs tests once. > > Justin > > ------------------------------ > *From:* Stephen Connolly [mailto:[EMAIL PROTECTED] > *Sent:* Thu 9/25/2008 3:09 AM > *To:* user@mojo.codehaus.org > *Subject:* Re: [mojo-user] test pass normally, but fail under cobertura > > I have seen tests fail under cobertura when: > > 1. Tests have timeouts > > 2. Tests make incorrect assumptions about how the JVM memory model and > synchronization work (or don't) > > This second one is why I always say run your tests twice ;-) > > 2008/9/25 Edelson, Justin <[EMAIL PROTECTED]> > >> I've been struggling for the past 2 days with a set of Spring-based >> integration tests that pass when run normally (i.e. mvn test), but fail when >> run using the cobertura plugin. >> >> I recognize this is a shot in the dark, but if anyone has any ideas on >> things I can try, I'd appreciate it. >> >> Specifically, I'd be interested in any differences in the classpath >> between a normal test run and the cobertura test run. >> >> Thanks, >> Justin >> > >
