From: John W. L. <Joh...@sa...> - 2007-02-22 10:24:01
|
For webapps, you have to make sure the instrumented classes are loaded = by the web app server. So, make sure the instrumented classes are in = WEB-INF/classes. Cobertura can also instrument a war in place if you = would rather do that. It can also do jars in place. Cobertura.ser will need to be in the working directory of the web app = container. This is the bin directory for Tomcat. John=20 -----Original Message----- From: cob...@li... = [mailto:cob...@li...] On Behalf Of = ramirez Sent: Wednesday, February 21, 2007 7:30 AM To: cob...@li... Subject: Re: [Cobertura-devel] cobertura basics I tried to put the cobertura.ser virtually everywhere now, to no avail. = The project is a web application and not a standard application, maybe = that's the reason? Do you test web applications differently? JUnit tests = seem ok.=20 Theory is that when I access the instrumented class (the class in = \classes folder which has its equivalent in \instrumented folder) the = class will do its thing and then exit, and after that the cobertura.ser = gets updated. Right? Is there any debug option I could use to see what's right and = what's not? -- View this message in context: = http://www.nabble.com/cobertura-basics-tf3259962.html#a9079946 Sent from the cobertura-devel mailing list archive at Nabble.com. -------------------------------------------------------------------------= Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share = your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV _______________________________________________ Cobertura-devel mailing list Cob...@li... https://lists.sourceforge.net/lists/listinfo/cobertura-devel |