<< View previous version | view page history | view next version >>
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 importantly QuickBuild can collect the statistics data from those reports. This will help you to analyze the project [build statistics] later.
Following screenshot shows a typical Java project overview by adding some reports to QuickBuild:
Supported Reports
Following table lists all the reports supported in QuickBuild:
Java Category
Report Name | Version |
---|---|
[JUnit Report] | 3.8+ |
[TestNG Report] | 5.7 |
[Fidbugs Report] | |
[CheckStyle Report] | 4.1+ |
[EMMA Report] | 2.1+ |
[Cobertura Report] | |
[PMD Report] | 4.2.2 |
Ivy Dependency Report | |
.NET Category
Report Name | Version |
---|---|
[NUnit Report] | 2.0 |
[MBUnit Report] | 2.4+ |
Third-Party Reports
For reports not directly supported in QuickBuild, you can also create your own plugin setting 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.
Different Version Of The Reports
If versions of the reports you are using are different from the list above, you may need to customize them based on the existing setting. Sometimes, it may only need to change a few columns definitions.
Generic Step for Publishing Build Report
To publish a build report in QuickBuild, you just need two steps:
- Generate the build report by using Ant, Maven, NAnt, etc. When generating the build reports with those tools, the XML format should be used. QuickBuild only recognizes XML reports.
- Add a publish step for the specific report. For example, for JUnit, add a publish junit step, for TestNG, add a publish TestNG step.
That is all you need to do! Both the reports and the statistics data for the reports will be collected automatically, and you can [view them in QuickBuild] directly instead of generating external HTML report.