Execution Reports

The Execution Reports section provides a centralized dashboard covering all of your automated test executions. It allows you to monitor active testing, track failure occurrences across environments, and review detailed test performance metadata.

These reports help QA teams maintain full visibility into their automation pipelines to quickly identify unstable runs or failing test suites.

Execution Reports Dashboard


The Execution Trend Graph

The dynamic trend chart visualizes your test runs over hours, days, or weeks.

It displays execution histories categorized across:

  • GitHub Check Runs
  • Scheduled Executions
  • Test Suites
  • Individual Test Cases

Using the trend graph helps development teams:

  • Identify overall test execution frequencies.
  • Detect sudden spikes in system-wide automation failures following a new deployment.
  • Monitor the cumulative health of your automation architecture daily.

Managing Failed Tests

On the right side of the primary dashboard, the Failed Tests panel highlights your most recent broken test cases.

Each failed entry displays the following metadata:

  • Test Case Name: The specific script or scenario that failed.
  • Suite Name: The parent suite where the test resides.
  • Time of Failure: The precise timestamp of the run.
  • Failure Reason: An automated error description highlighting exactly why the step failed.
  • Environment: Where it executed (e.g., LOCAL or CLOUD).
  • Test Type: The platform classification (e.g., WEB, API, MOBILE).

Investigating Failures

  • Click Show More to expand detailed failure breakdown metrics.
  • Click View Logs to instantly inspect the underlying terminal logs.

This focused panel allows for rapid pipeline debugging without having to navigate through full-length test reports.


Filtering and Exporting

Robonito provides robust dashboard filters to narrow your report data for focused analysis:

  • Status: Filter executions by Passed, Failed, or In Progress.
  • Environment: Isolate metrics mapped from Local or Cloud execution servers.
  • Execution Type: Narrow reports down by a single Test Case, an entire Suite, or a Schedule.

Downloading Reports

You can click the Download button to export execution logs or comprehensive .csv spreadsheets securely for use outside of the Robonito platform.


Deep Dive: Execution Details

Clicking into any specific execution entry opens highly detailed debugging information, including:

  • Exact step-by-step test timelines.
  • Pass/fail assertion data result comparisons.
  • In-depth UI failure messages, network snapshots, and DOM traces.
  • Comprehensive system logs.

Understanding Failure Examples

In the event of a test failure, Robonito explicitly highlights the error directly in the UI. For example:

Visual assertion FAILED. Check diff and actual image.

This output indicates that:

  1. A visual DOM mismatch occurred during execution.
  2. An unexpected UI change was detected.
  3. The recorded visual assertion failed.

From here, teams can deeply inspect the generated logs alongside the saved diagnostic screenshots to exactly determine the core root cause of the UI breakdown.