![]() |
![]() |
Time-to-fix is an important build stability metrics that tells how long it takes a team to react to a broken build by fixing it .Parabuild provides an instant snapshot chart and a trend chart for time-to-fix. By looking at these charts we can see if the team can improve its performance:

For quick access to the test summary, Parabuild shows an overview of the tests that run as a part of the build:

Parabuild parses XML logs produced by PMD, a static code analysis tool for Java, and produces a formatted report showing problem classes and a statistics chart. The growing number of found violations tells that a team may have to spend a bit of time to address the reported issues:

Parabuild parses XML logs produced by Checkstyle, a static code analysis tool for Java, and produces a formatted report showing problem classes and a statistics chart:

Parabuild analyzes PHPUnit logs in XML format. Easy-to-use Web user interface allows quickly configuring the log:

Once the log is configured, Parabuild shows formatted output on its build log page:

... and provides provides per-build, daily and monthly NUnit statistics charts.
Parabuild analyzes NUnit logs in XML format. Easy-to-use Web user interface allows quickly configuring the log:

Once the log is configured, Parabuild shows formatted output on its build log page:

.. and provides provides per-build, daily and monthly NUnit statistics charts.
Parabuild analyzes CppUnit logs in XML format. The logs are usually produced as part of a Continuous Integration cycle or during a scheduled build. Configuration of the location of the log is performed through Parabuild's Web user interface:

Parabuild shows CppUnit on the build results page:

Statistics charts for CppUnit are provided.
As number of tests grows, small percentages of failed tests becomes hard to see on statistics charts. Parabuild provides logarithmic scale for test charts. This allows to emphasize trends for broken tests.


| « New features in build and release management |