Done deal - I also added IDEA's project files to the .gitignore file. Once that's merged, you have to make 2 changes to the build config to get those included in the build output:
- in "Goals and options", add cobertura:cobertura to the maven command - in "Post-build Actions", add "Publish Cobertura Coverage Report", and give it the path to the xml output. The path should be something like "**/stripes/target/site/cobertura/coverage.xml". If you're serious about ferreting out stuff that could be better tested (we're around 40% coverage now, so there's certainly room for improvement), there are two other changes I'd recommend: 1) Enable the "Stability auto update" in the "Advanced..." section of the coverage report - that will fail the build if someone chucks untested code into the project that causes the coverage metrics to drop. It will automatically ratchet up the coverage on each commit. 2) Install and add the "Coverage / Complexity Scatter Plot" plugin for Jenkins - it looks at both coverage and complexity so you can find higher risk code that's untested. That's pretty useful for people (like me) who are looking for ways to contribute. :-) Larry ------------------------------------------------------------------------------ _______________________________________________ Stripes-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-development
