Reports

The following reports will be generated at the end of your test run: In the build/reports directory you'll find 3 sub-directories:

• geb
• spock
• tests

The test framework will overwrite previously run reports, so the build/reports content only reflect the last run. This is important to understand, if you want to capture the report for later reporting. In the pipeline we currently archive the build/reports directory after every run, so you can go back in Jenkins and review the results for a build.

If you interrupt a test run, no reports will be generated.

Geb Reports

The sub-directories show the type of test (e.g. chromeTest, ieTest etc.) and in these sub-directories you'll find the captured HTML of the page under test and a screen image for each of the tests you have executed.

Tests Reports

The sub-directories show the type of test (e.g. chromeTest, ieTest etc.) and in these sub-directories you'll find the full test report starting with index.html. This full report is captured in the pipeline and view-able in Jenkins for each build. This is the most commonly used report.

Spock Reports

By default, the report creator generates a HTML report for each Specification, as well as a summary of all Specifications that have been run (index.html). The advantage of this report is that it aligns more to the actually specifications and Gherkin statements from the business, making this report something that is easy to share.

Last but not least

The last "report" that gets generated can be found in test-results. The sub-directories show the type of test (e.g. chromeTest, ieTest etc.) and in these sub-directories you'll find the test results in the standard XUnit XML format.

It’s designed for the Jenkins continuous build system, but will probably work for anything else that understands an XUnit-formatted XML representation of test results.