Skip to main content
Proton v5

Run details

The run details show what happened in each step, the log, the evidence and, for a failure, the diagnosis. You can open them from the group in the Automation Center, from a dataset's runs, from Log search, or from a shared link.

The details have three tabs: Timeline, Results, and Error (the last one only for a run that failed or was stopped).

Header​

  • The status, the automation, the end reason (business failure, technical failure, environment failure, stopped, didn't reach the runner, runner lost; see the Glossary), the environment, and the run id.
  • Start, End (or "In progress"), Duration, User, and Runner.
  • Technical details:
    • the Correlation ID, to find the run from another system's log, through Log search;
    • the Code version: the system, the branch, and the commit of each repository, with a link to the commit. The commit is recorded by Proton Runner starting with version 5.0.8.

Timeline​

The steps in order, with the duration and status of each one. The summary shows the total number of steps, the count per status, the success rate, and the total duration.

  • Filter by status and search for a component. Expand All opens every step.
  • Each open step shows the expected result (from the component and from this dataset), the recorded Output Parameters, and the step's Screenshots.
  • Input Parameters shows the values the run used, including the ones adjusted when it was launched. Encrypted values are masked.
  • The screen refreshes on its own while the run is in progress.

Stop the run​

Stop run interrupts the run in progress: the step that was running is marked as stopped, and the following ones as No Run. Proton asks the runner to end the automation process. This cannot be undone.

Validation​

With the Quality module, on a run from a test group, Add Validation records the QA sign-off: Approved or Rejected, with remarks (required to reject) and an attachment. Show Validation shows the history of status changes and the comments. The validation also appears in the run list and in the report.

Results​

Log​

The run log, line by line, grouped by step:

  • the chips show how many warnings, errors, and critical entries there are; the filter shows All, Warnings and errors, or Errors only;
  • Search the log looks for a piece of text;
  • copy the lines shown or download the whole log;
  • runner lines (project setup, and the start and end of the automation) appear outside the steps.

Beyond 10,000 lines, the rest stays in the run's log file, which you can download.

Where it failed and attachments​

  • Where It Failed? points to the step that failed.
  • Attachments holds the run's screenshots, videos, and files, with a filter by type and a viewer for images, videos, PDFs, and text. Download All downloads everything in a zip.

Share and report​

  • Share copies the run's link.
  • Report generates the run's PDF: the information, the summary, each component with its parameters and screenshots, the validation, and the log.
  • Export All downloads a zip with the log and the attachments.

Error​

Failure diagnosis​

With the AI module, Diagnose with AI analyzes the failure: it cross-checks the screenshot, the log, the steps, what changed since the last time it passed, and similar failures, and returns:

  • the cause (environment, test data, screen change, slowness, application defect, runner or machine, automation script, or unidentified cause) and the confidence;
  • Why the AI thinks so, with the evidence and links to it;
  • What to do: run again in the group, open a bug in Jira, or copy a notice for the team.

Each diagnosis uses AI credits, and the button shows how many.

Afterwards, confirm the cause: Yes, it was or It was something else (choosing the right cause). Later analyses of the same step take the confirmation into account. Without the AI module, you can record the cause by hand.

Failure evidence​

With or without AI, the tab shows similar failures (the same error in other runs), the causes already confirmed for the step, and the evidence: the step's screenshot, the end of the log, the exception (to copy or download), the dataset's latest runs, and what changed since the last time it passed.

Jira and Xray​

  • Jira bug: open a bug with the run report, or link a bug that already exists. Only available with the Jira integration and after the run finishes. See Jira.
  • Xray: the run's Test Execution, Test, and Test Plan, when the group publishes to Xray or Zephyr. See Xray and Zephyr.

Rerun​

Every rerun creates a new run:

  • automatically, with Re-run on execution failure when the run is launched;
  • from the diagnosis, with Run again in the group;
  • from the failure drawer, in the group.

Permissions​

Viewing the details requires viewing runs. Stopping requires run permission in the Automation Center; validation has its own permissions; opening a bug requires creating Jira bugs.