Trying to determinate the best way to implement Continuous integration at our shop, and specifically, which information we must generate after nightly builds, I’ve discovered QALab, an opensource project that “collects and consolidates data from several QA tools and keeps track of them overtime, allowing developers, architects and project managers alike to be presented with a trend of the QA statistics of their project”

It collects data from the following tools:

  • Checkstyle: code style validation and design checks. QALab keeps track of number of violations per file and overall.
  • PMD: Code checks (possible bugs, dead code, sub-optimal code, etc). QALab keeps track of number of violations per file and overall.
  • PMD CPD: Duplicate code (always a bad idea) detection. QALab keeps track of number of the overall number of duplicated lines.
  • FindBugs: fantastic tool to detect potential bugs (really!). QALab keeps track of number of violations per file and overall.
  • Cobertura: Coverage tool. QALab keeps track of percentage of branch and line coverage.
  • Simian: excellent duplicate code detection (non-open source). QALab keeps track of number of the overall number of duplicated lines.

(Via The Server Side)