Glad to hear you got things working. Just a note on Cobertura though; we are running our cove coverage for unit and container-based integration tests with Cobertura so it's not the tool per se. Could have been an issue with the version of Cobertura you were using or the configuration but if Emma is working for you and you are happy with it, I wouldn't switch.
Kalle On Fri, Mar 5, 2010 at 1:05 AM, Douglas Ferguson <[email protected]> wrote: > Actually switching to emma got things working.. > > I just start jetty from the base class of my selenium test. > I have a static field that prevents jetty from attempting to start twice. > > Seems to work great. > > D/ > > On Mar 4, 2010, at 11:23 PM, hanasaki wrote: > >> most of what I have found points to using emma to get code coverage in >> the integration phase using the failsafe plugin and embedded Jetty. >> >> -------- Original Message -------- >> Subject: cobertura & jetty >> From: Douglas Ferguson <[email protected]> >> To: Maven Users List <[email protected]> >> Date: 03/04/2010 10:43 PM >> >>> So I finally got jetty starting from my test case, but it doesn't >>> impact the code coverage. >>> >>> My BasePage class is at 0% which is confusing. >>> >>> The server is started from the test class which would make you think >>> would be using the instrumented classes and jetty would inherit the >>> same classpath. >>> >>> What am I missing? >>> >>> Douglas >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] For >>> additional commands, e-mail: [email protected] >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
