From: John W. L. <Joh...@sa...> - 2012-07-27 18:33:30
|
It should be the same size. Remember that an integer is the same size in memory (or on disk) whether it is a big number or a large number. The timestamp should be updated. I am almost certain that is true since you mention seeing the lock file. What does your report look like? John From: *** From Sakthivel Kumar*** [mailto:nsa...@gm...] Sent: Friday, July 27, 2012 2:28 PM To: John W. Lewis Cc: cob...@li... Subject: My orignial cobertura.ser is not getting updated after server shut down and seeing "cobertura.ser.Lock" for a second. John: Thanks for your valuable inputs and time. As you mentioned i copied the cobertura.ser file to the same location my your application produces the cobertura.ser file. As soon as is finished testing and server shut down, i see "cobertura.ser.Lock" getting created for a second and vanishes. The orignial cobertura.ser is not getting updated. Still same size after testing is done. I have caputred the logs after shutting down my server. Below is the logs. Please take a look and let me know why original cobertura.ser file is not getting updated after server shut down and why there is a "cobertura.ser.Lock" getting created for a second and vanishes. Lib is getting loaded from PegJniKit interface The java.vendor property is Sun Microsystems Inc. The os.name<http://os.name> property is Windows XP The java.version property is 1.6.0_29 Is Java 2 Platform? true The java library path is: . Windows SUN's virtual machine loaded 13:12:37:913 >> Loading HP QuickTest Professional Java Support (version 11.0.0.0) (SUN 1.6.0_29) 13:12:38:273 >> ========= Mercury Interactive Class Loaders ========= 13:12:38:273 >> com.mercury.ftjadin.infra.CSClassLoaderJava2@12884e0<mailto:com.mercury.ftjadin.infra.CSClassLoaderJava2@12884e0> on top of sun.misc.Launcher$AppClassLoader@f4a24a<mailto:sun.misc.Launcher$AppClassLoader@f4a24a> 13:12:38:273 >> ========================================= Flushing results... Flushing results done Cobertura: Loaded information on 404 classes. Cobertura: Saved information on 404 classes. 13:20:33:712 >> DEBUG >> Releasing all waiters. There are 0 waiters active. RPC Name : \pipe\RPCQReads5_1343412758304 In DATA_HANDLE_TYPE_SERVER_bind Reached the end of function Thanks Sakthi. On Fri, Jul 27, 2012 at 10:33 AM, John W. Lewis <Joh...@sa...<mailto:Joh...@sa...>> wrote: The instrumentation produces a cobertura.ser file. That same file should be used during your testing. One way of doing this is to copy the cobertura.ser file to the same location where your application produces the cobertura.ser file. From: *** From Sakthivel Kumar*** [mailto:nsa...@gm...<mailto:nsa...@gm...>] Sent: Wednesday, July 25, 2012 6:50 PM To: cob...@li...<mailto:cob...@li...> Subject: [Cobertura-devel] My percentage code coverage as 100%. Not sure why cobertura.ser file is not properly created and this file size is very small. Hello cobertura Group. Good evening. When i tried to generate code coverage using Cobertura tool, i see my percentage code coverage as 100% in my report. Before running my tests, i delete the existing cobertura.ser file and after running test each time, i can see a latest cobertura.ser file is getting generated. The cobertura.ser file generated is small in size less than 200 KB. And i am using this latest cobertura.ser file to generate coverage report. I did not know what is causing to give 100% code coverage report. But i expect to see the size of cobertura.ser file generated should be bigger. Below is the steps how i did my code coverage. a) Instrumented my EAR files and deployed to server b) Accessed my application in the server c) latest cobertura.ser file got generated. 4) Picked up the latest cobertura.ser file and used in my report coverage build to generate reports. In the reports directory, when i checked the index.html i can see 100% code coverage. Is there any other steps i am missing.? Please take a look and help me. I appreciate your help. Thanks Sakthivel nsa...@gm...<mailto:nsa...@gm...> -- Thanks and Best Regards Sakthivel Kumar nsa...@gm...<mailto:nsa...@gm...> |