View Source

h2. Introduction

Build reports are very important for detecting a project health. By adding your build reports to QuickBuild, the project health can be tracked very easily, and the most important thing is that QuickBuild can collect the statistics data from those reports. This will help you to analyze the project from [build statistics|3. Working with Statistics] later.

Following screenshot shows a typical Java project overview by adding some reports to QuickBuild:
!buildOverview.png!

h2. Supported Reports

Following table lists all the reports supported in QuickBuild:

h3. Java Category

|| Report Name || Version ||
| [JUnit Report|5.5 Adding JUnit Report] | 3.8\+ |
| [TestNG Report] | 5.7 |
| [CheckStyle Report|5.1 Adding CheckStyle Report] | |
| [EMMA Report|5.2 Adding EMMA Report] | |
| [PMD Report|5.7 Adding PMD Report] | |
| [Ivy Dependency Report|5.4 Adding Ivy Dependency Report] | |

h3. .NET Category

|| Report Name || Version ||
| [NUnit Report|5.6 Adding NUnit Report] | 2.0 |
| [MBUnit Report|5.7 Adding MBUnit Report] | 2.4\+ |

h3. Third-Party Reports

For reports not directly supported in QuickBuild, you can also [create your own plugin setting|8. Customize The Build Report] of the plugin com.pmease.quickbuild.plugin.report.generic to publish your particular reports, or you can create your own plugin to meet your requirements.