copyright vincent massol 2006 all rights reserved panorama of quality features in maven2 vincent...

Copyright Vincent Massol 2006 – All rights reserved

Panorama of Quality Features in Maven2

Vincent Massol, 11 July 2006http://massol.net


Active Quality vs Passive Quality


Active quality = before the fact


Passive quality = after the fact


Both are required…… but moving to active is the

direction to take


… and Maven can do both٭!


Quality plugins

● Surefire– JUnit and TestNG– Cargo and other

container plugins● PMD● Checkstyle● Verifier● Clover

● Clirr● Cobertura● Jalopy● JDepend● JavaNCSS● JDiff

In Maven In Mojo

● DBUnit● Jardiff● JCoverage● FindBugs● Simian

In Mojo sandbox


Let’s review some plugins for…● Tests (unit, integration and

functional)● Best practices (Checkstyle, PMD,

etc)● Test Percentage Coverage● Binary compatibility


Common testing infrastructure for testing frameworks (JUnit,

TestNG, etc)


New forking strategies: once, never, always


New integration test phase and Cargo plugin for automating

J2EE application testing


Strategy for active checks

● Strategy– Fail the build upon test failure


Demo …


Checkstyle, PMD, Findbugs can fail the build (active) or

generate a report (passive)


Local Repo

Build ToolsModule

Module to be checked

build-tools.jar Depends onbuild-tools.jar

Best practices concept



● Strategy 1– Turn on all agreed checks at beginning of project

● Strategy 2– Activate some checks– Increase # of checks at each release


Demo …


Clover, Cobertura plugins can fail the build (active) or

generate reports (passive)


Module 1

Module 2

Module 3

Depends on

Local Repository

module1-clover.jar

module2-clover.jar

module3-clover.jar

Build

Dependency

Clover plugin for Functional testing


… and aggregates reports at each parent POM level



● Strategy– Check TPC at release– Set threshold to be this TPC– Fail the build when under this threshold– Repeat


Demo …


Clirr performs comparisons between releases to detect

binary compatibility changes


Can fail the build upon errror (active) or generate reports

(passive)



● Strategy– Fail the build upon violation– Add to exclude file when incompatibility wanted– Publish exclude file as part of release notes

● Warning: Currently missing fine-grained exclusions


Demo …


What’s missing? What’s the future?


Quality Dashboard


● Commits per day, who’s doing commits?● Who’s working on tests?● Who’s answering mailing lists?● Who’s applying patches?● Who’s writing documentation, blogging about it,

etc?=> Ability to jauge activity on the projects

Project Health DashboardProject Activity Dashboard

Questions

Me

copyright vincent massol 2006 all rights reserved panorama of quality features in maven2 vincent...

Documents