Docs

Accessing Test Results via API

Every test execution in RobusTest generates a result record. You can retrieve the full detail of a result programmatically — including logs, network capture, and AppVitals data.

Overview

A result represents the outcome of a single test case run during a job. Results are grouped by instance (a device execution within a job) and by run (an Automation test suite execution).

Getting Result IDs for a Test Case

Each test case can have multiple result records — one per attempt across different job runs or devices. Use the following endpoint to retrieve all results for a given test case:

GET /v3/testcase/:testcaseID/results

Returns an array of result records for the test case. Each record contains an _id field — this is the result ID used in all subsequent result API calls.

The test case ID is available in the RobusTest job report UI, or by calling:

GET /v3/job/:jobID/testcases

Getting a Result

GET /v3/testresult/:id

Returns the result record including status, start/end times, device information, and test case name.

AppVitals

Get AppVitals data:

GET /v3/result/:id/appvitals

See AppVitals Android Metrics Reference and AppVitals iOS Metrics Reference for the full metrics reference.

Network Capture (HAR)

If network capture was enabled during the test, you can retrieve the HAR file:

View network traffic:

GET /v3/result/:id/mitmproxy

Download as HAR file:

GET /v3/result/:id/mitmproxy/download

Test Session Logs

During a live test session, you can access logs in real time:

Device log:

GET /v3/testsession/:id/devicelog

All logs for session:

GET /v3/testsession/:id/logs

Appium log:

GET /v3/testsession/:id/appiumlog