Skip to main content
Test History with runs

Accessing Test History

To view a test’s history:
  1. Go to Test Suite in the sidebar
  2. Click on any test in the list
  3. You’ll see the History view by default
Or click the History icon in the Test Editor toolbar.

History Page Layout

The History page shows: Test Header:
  • Test name
  • Platform (Android or iOS)
  • Last run timestamp
  • Current status (Passed/Failed/Not Run)
Action Buttons:
  • Settings - Configure test options
  • Open Editor - Go to the Test Editor
  • Run - Execute the test now
Filters:
  • All Statuses - Filter by Passed/Failed/Running
  • Newest First - Sort by date (newest/oldest first)
  • Refresh - Reload the history list

Test Run List

Each test run shows:
  • Timestamp - When the test was executed
  • Status - Pass/Fail/Running indicator
  • Duration - How long the test took
  • Steps - Which steps passed / failed
Click a run row to open the full report for that run.

Test Configuration

  • Device used
  • Build version
  • Variables used
  • Environment settings

Analyzing Failures

When a test fails, the History view helps you debug:
  1. Check the status - See which step failed
  2. Review the report - Visual evidence of the failure
  3. Read logs - Look for error messages
  4. Compare with passing runs - What changed?
  5. Open Editor - Fix the issue and re-run

Sharing Results

You can share test results with your team:
  1. Click on a test run
  2. Copy the report link
  3. Share the link - anyone with access can view
  4. Results include logs and full details

Empty State

If a test hasn’t been executed yet, you’ll see:
“No test runs found” “This test hasn’t been executed yet.”
Click Run to execute the test for the first time.

Filtering & Sorting

By Status:
  • All Statuses
  • Passed only
  • Failed only
  • Running (in progress)
By Date:
  • Newest First (default)
  • Oldest First
Use these filters to quickly find specific test runs.

Best Practices

  1. Review failures immediately - Don’t let failed tests pile up
  2. Check logs for patterns - Recurring errors indicate systemic issues
  3. Keep a history - Don’t delete old runs, they’re useful for trends
  4. Share with team - Use URLs to discuss failures together

Next Steps


Need help? Contact [email protected]