> Am 16.09.2015 um 15:53 schrieb Jesse Glick <[email protected]>: > > On Wed, Sep 16, 2015 at 8:04 AM, Ullrich Hafner > <[email protected]> wrote: >> Did someone already manage it to start the Jenkins under Test with coverage >> monitoring (emma, cobertura, jacoco, etc.)? > > I have run JaCoCo during plugin tests. > >> Seems not so easy due to the Jenkins class loader. > > With `JenkinsRule`? Not an issue, all classes in the test root, plus > the plugin being tested and its stated dependencies, and core and its > modules and libraries, are in the Surefire classpath and so available > for processing by JaCoCo, just like in a unit test. The only classes > that might slip past are those in unrelated bundled plugins, or > plugins loaded via `@WithPlugins`, that would be loaded via a plugin > class loader, but surely you do not care about coverage of these. >
For unit tests and JenkinsRule integration tests I get the coverage working, too. But not yet for the acceptance tests: here Jenkins is started and loading the plain plug-ins from JENKINS_HOME. It would be interesting to see the coverage of these tests, too. I used this approach for manual testing of some enterprise applications… With emma you can enhance the classes of a packaged application (jar) and then start testing. During the manual tests the coverage data is incrementally written. After testing, you simply can create a report of these tests. Would be nice to get this for the acceptance tests, too. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/685AB1C7-FD16-4E0F-953F-715E7128E5A0%40gmail.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP using GPGMail
