|
From: Thomas L. <lo...@ne...> - 2009-02-03 14:51:10
|
Hi, I just got linked to CodeCover on my search for an code coverage tool for testing a big JEE application. Despite it is a quite big application we just started to establish automated testing routines. The biggest problem we have is to distinguish which parts of the code should be tested. The application is very stable in it's current release but with every update we are afraid of bringing in new bugs. It's not possible to test everything before a new release goes productive. So the following idea got into my mind. What if a code coverage tool can state how much of my _changed_ code I got tested. The changed code can be easily determined by an SVN difference (or other versioning systems). The tests could be done automatically or manually. If doing them manually one could see which code passages that where changed between two software releases got coverd by testing and keep on testing until every change got tested. First I want to know what you think about that idea. Do you think that it is a good idea to test only the differences between stable code and the new code? Do you think testing manually in combination with a code coverage tool makes sense? Can you make any suggestions of how to integrate that into CodeCover? regards, Thomas PS: Darf man hier auch auf Deutsch schreiben? -- Thomas Louis netzprofis GmbH & Co. KG Joseph-von-Fraunhofer-Str. 29 44227 Dortmund fon: +49-231-399802-70 fax: +49-231-399802-69 cell: +49-178-3464000 callto://hergaty mailto:lo...@ne... USt-IdNr. DE225365236 Amtsgericht Dortmund HRA 16304, Komplementärin: Gleis & Louis Verwaltungsgesellschaft mbH Amtsgericht Dortmund HRB 20179, Geschäftsführer: Marcel Gleis & Thomas Louis |