Docs

Reading Job Reports

Overview

After an automation job completes, RobusTest generates a comprehensive Job Report that gives you full visibility into what happened during the run — from overall pass/fail counts to individual test step screenshots and device logs.

Section Purpose
Dashboard High-level job summary, status, timing, and device usage
Test Cases Full list of test cases with results, filterable by status, tags, and groups
Classes / Devices Results organised by test class or device
Timeline Chronological view of job execution across devices
Test Case Detail Per-attempt breakdown with screenshots and logs

Job Dashboard

The Dashboard is the first view when you open a job report. It gives you an at-a-glance summary of the entire run.

Summary

Field Description
Status Overall job status — Pass, Fail, Error, or Running
Total / Pass / Fail / Error Counts of test cases by result
Duration Total time taken for the job to complete
Devices Used List of devices the job ran on
Run Settings The Run Settings profile applied to this job

Highlights

Key metrics surfaced at the top of the dashboard — quickly identifies the most important outcomes without needing to scroll through all test cases.

History Chart

Displays pass/fail trends across previous runs of the same job. Useful for spotting regressions or improvements across builds.

Test Cases

The Test Cases view lists every test case in the job with its result. You can filter the list by:

  • Status — Pass, Fail, Error, Skip
  • Tags — Custom tags applied via Run Settings analysis rules
  • Groups — Test groups defined in your test suite

Each row shows the test case name, status, device, and duration. Click a test case to open its detailed view.

Classes

Available for Espresso and XCUITest jobs. Groups test cases by their test class, making it easy to see which classes have the most failures.

Devices

Shows results broken down by device — useful when the same test case is run across multiple devices to identify device-specific failures.

Timeline

A chronological view of how the job executed across all devices and instances. Helps you understand parallelism, device preparation time, and where time was spent during the run.

Test Case Detail

Clicking on a test case opens the detailed view for that test case. If the test case was retried, each attempt is shown separately.

For each attempt, the following tabs are available:

Screenshots

A step-by-step screenshot sequence captured during test execution. Use the slideshow controls to play through the screenshots automatically or navigate manually using previous/next buttons.

App Vitals

App-level health metrics collected per test case during execution — CPU, memory, network, energy, disk I/O, and frame rendering data. Available when App Vitals is enabled in the Run Setting for Espresso and XCUITest jobs.

See App Vitals for how to enable and use it.

Device Log

The device logcat output captured during the test case attempt. Useful for diagnosing crashes or unexpected app behaviour that isn't visible in the test output alone.

Framework Log

The output from the test framework (Espresso, XCUITest, or Appium) during execution. Contains step-level pass/fail results and any framework-level errors.

ANR Log

The Application Not Responding log, captured if the app stopped responding during the test. Available for Android only.

Network Logs

Network traffic recorded during the test case attempt.

Diagnostics Log

Detailed diagnostics output. Available for iOS XCUITest jobs.

Crash Logs

Crash reports captured if the app crashed during the test. Available for iOS jobs.

Error Info

Structured error details when a test case fails or errors — includes error type, message, and context to help identify the root cause quickly.

Log Bug

Log a bug directly into your configured bug tracker from within the test case detail, without leaving the report.

Filtering and Navigation Tips

  • Use the status filter on the Test Cases view to focus only on failures
  • Use tags to group failures by category (e.g. network errors, crashes)
  • Use the History Chart on the Dashboard to compare this run against previous runs
  • Use the Devices tab to isolate failures that only occur on specific devices or OS versions

See Also: