Help Center/ CodeArts Build/ User Guide/ Configuring a Build Task/ Configuring Build Actions/ Generating a Unit Test Report
Updated on 2026-07-29 GMT+08:00
View PDF
Share

Generating a Unit Test Report

The Unit Test Report action generates a visualized report by parsing the unit test result file that you have generated. (This action is available only on the GUI.)

Currently, this action is only available in the ME-Riyadh region.

A unit test file cannot exceed 10 MB in size.

Prerequisites

Before running the Unit Test Report action, ensure that the test result file has been generated and the file framework is supported by CodeArts Build.

Build on GUI

Add Unit Test Report, when configuring build actions. Set the parameters according to Table 1.
Table 1 Parameters for generating the unit test report

Parameter

Description

Action Name

Assign a custom name to the build action. The name can contain:

  • Letters, digits, hyphens (-), underscores (_), commas (,), semicolons (;), colons (:), periods (.), slashes (/), and parentheses.
  • 1 to 128 characters.

Test Report Path

Specify the storage location for the test coverage report. Use a relative path from the project's root directory. For example, target/surefire-reports/TEST*.xml. Wildcard characters (* and **) can be used in the path for multi-level directory matching.

Release Test Coverage Report

You can configure whether to release a unit test coverage report as part of your build process. These reports provide visibility into which portions of the codebase are exercised by unit tests and which remain untested.

  • Yes: Release the test coverage report.

    When enabled, you must configure the following parameters:

    • Test Coverage Report Format: Select the format for the test coverage report. Currently, only JaCoCo-generated reports are supported.
    • Target Test Coverage Report Path: Provide a relative path from the project root. For example, **/site/jacoco. Wildcard characters (* and **) can be used in the path for multi-level directory matching.
  • No: Do not release the test coverage report.

Continue After Failure

Specify whether to proceed after the current action fails by setting the parameter to either Yes or No.