From: John W. L. <Joh...@sa...> - 2011-04-12 12:51:38
|
That is almost certainly a case where the process is not being pointed to the cobertura.ser file that was created during instrumentation. Either the working directory of the process has to contain the cobertura.ser file, or the cobertura property has to be set that points to it. From: Fabien Bataille [mailto:fba...@gm...] Sent: Tuesday, April 12, 2011 8:42 AM To: cobertura-devel Subject: [Cobertura-devel] 100% coverage but not all lines found Hi all, I am getting 100% coverage when running a lots of automatic tests (~1500) on a big chunk of code. I found the following affirmation in the Cobertura FAQ "Another common problem is that the cobertura.ser file is deleted, but the previously instrumented classes are not also deleted. Any time you delete your coverage data file you should also deleted all instrumented classes." Does anyone have more information on that ? I understood that Cobertura is storing coverage data first in memory and then is flushing it to a file when the JVM stops. So what is the pb to keep already instrumented classes, as soon as the location of the cobertura.ser file does not change ? Is there dynamic information stored into these classes ? As my platform is very huge instrumenting all classes at each run will last more than 24 hours, so I managed to create a cache for the instrumented jars in order not re-instrumenting them, as the cobertura.ser is always generating at the same location, and deleted between each run. Thanks for your help ! Fabien |