Skip to main content

Test Run Details

Click into any test run to see rich execution metadata, build/app context, suite change analysis, and failed tests with issue creation actions.

Test Run Details

Metadata Section

Each test run displays key context in a two-column layout. Some fields are always visible while others appear only when data is available:

FieldDetails
BranchGit branch name (always shown)
StartedTimestamp of test execution (always shown)
CommitShort SHA (first 7 chars), links to the commit in your repository when a repository URL is available (shown when available)
EnvironmentTest environment, e.g. staging, production (shown when available)
DurationTotal execution time (always shown)
ToolTest framework name and version, e.g. "Playwright 1.40" (shown when available)

Build and App Info

When provided by the reporter or CI environment, the Build and App Info panel appears with:

FieldDetails
Build NameCI workflow or build identifier
Build NumberBuild/run number from CI
Build LinkDirect URL to the CI pipeline run
ReporterReporter/tool that generated the test payload
AppApplication name under test
VersionApplication version under test
Test TypeRun type tag, e.g. unit, integration, e2e

Results Summary

View aggregate statistics:

  • Number of passed tests
  • Number of failed tests
  • Number of skipped tests
  • Number of flaky tests (when present)
  • Number of pending tests (when present)

Test Suite Changes

Test Run Details includes a Test Suite Changes summary card that compares the run against the previous run on the same branch.

  • Highlights added and removed tests
  • Shows net/percentage change
  • Supports first-run and no-change states
  • Opens a detailed modal for added/removed test inspection

See the dedicated guide: Test Suite Changes.

Release Linking

Associate test runs with Jira release versions using the "Manage" action in the Release section. This helps track quality per release cycle.

Failed Tests List

All failed tests are listed with:

  • Test name
  • Error message preview
  • "Create Issue" button for each failure