Help Center/ CodeArts Build/ API Reference/ APIs/ Build Reports/ Uploading a Unit Test Report

Updated on 2025-12-10 GMT+08:00

CLI Examples

View PDF

Uploading a Unit Test Report

This API is used to upload the unit test report of a specific build action by referencing its ID.

For details, see Calling APIs.

POST /v1/report/junit/report/upload

**Table 1** Query Parameters
Parameter	Mandatory	Type	Description
job_id	Yes	String	Definition Build task ID. It includes digits and letters. To obtain this ID, open the page for editing the build task in your browser, and copy the 32-character string at the end of the URL. Constraints N/A. Range The 32-character string sits at the end of the URL and includes digits and letters. Default Value N/A.
build_no	Yes	Integer	Definition The build number tracks each run of the build task. This parameter starts at 1, indicating the first build. It increments by 1 for every subsequent run. Constraints The value is a positive integer. Range Use only numbers that are 1 or greater. Default Value 1
node_id	Yes	String	Definition Build action ID. Use the value of node_id in the response body of the API that retrieves the full stages of a task. Constraints The value can contain a maximum of 32 characters. Digits, letters, and hyphens (-) are supported. Range N/A. Default Value N/A.

**Table 2** FormData parameters
Parameter	Mandatory	Type	Description
files	No	Array of files	Definition Uploaded unit test report files. Constraints N/A. Range N/A. Default Value N/A.

Status code: 200

**Table 3** Response body parameters
Parameter	Type	Description
status	String	Definition API response status. Range ● success: The API call is successful. ● fail: The API call failed.
error	Object	Definition Error message. Range N/A.
result	String	Definition Data returned after the API is successfully called. Range N/A.

POST https://{endpoint}/v1/report/junit/report/upload

Status code: 200

{
  "status" : "success"
}

Status Code	Description
200	OK

Parent Topic: Build Reports

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.