The configuration of the reports is done in the <exporters> sections of your project pom.xml:
Since Squash-TA framework v1.6.0, a HTML report is available.
To activate the HTML report in your project use "org.squashtest.ta.commons.exporter.html.HtmlSuiteResultExporter" as value for the implementation attribute.
@since Squash-TA framework 1.7.0 there is a simpler solution to activate the html report:
At the end of the execution (run or test-list) the HTML report (squash-ta-report.html) is available, by default, in the directory: 'my.squash.ta.project/target/SquashTA/html-reports'. Here are some screen capture of this report ( For a full sample see attach file: Execution report - execution-report-test-sample.pdf )
Test suite summary:
Target Initialisation summary: (@since Squash-TA framework 1.7.0)
Test script result:
To activate the surefire report in your project use "org.squashtest.ta.commons.exporter.surefire.SurefireSuiteResultExporter" as value for the implementation attribute. Two properties are available for this exporter:
@since Squash-TA framework 1.7.0 there is a simpler solution to activate the surefire report:
Execution reports are created in the 'my.squash.ta.project/target/SquashTA/surefire-reports'. The target directory is created during the execution.
The test cases execution with the used maven configuration provides surefire reports. There is one surefire report per ecosystem. Since Squash-TA framework v1.6.0 more details are given concerning the executed instructions. ( See full example in attach file: TEST-tests.F01.ScriptsTA.Set4.xml)
A surefire report is an 'xml' file which contains the results of the ecosystem TA-scripts execution. The first result of the listing is always the result of the ecosystem setup (setup.ta) even if the file doesn't exist. The last result of the listing is always the result of the ecosystem teardown (teardown.ta) even if the file doesn't exist.
Three kind of results are possible:
Inside the target directory, there are also attached documents produced by TA-scripts to make easier diagnosis when an error occurs (snapshots, diff-reports, detailed logged...).