Skip to main content
A test run is a collection of AI-executed test cases that Ito runs against a specific commit in a pull request. Each time you open a PR or push a new commit, Ito automatically starts a new test run for that commit.

​
How a test run is triggered

1

You open or update a PR

When a pull request is opened or a new commit is pushed to an open PR, GitHub notifies Ito via a webhook.
2

Ito creates a test run

Ito creates a test run tied to the current commit SHA. The run starts in pending status while the AI agent prepares the test environment.
3

The AI agent executes test cases

The agent runs each test case, capturing a video recording and collecting results as it goes.
4

Results are published

When all test cases finish, results appear in the dashboard, and if PR comments are enabled, Ito posts a summary to your GitHub PR.
When you push a new commit while a run is still in progress, Ito automatically cancels the stale run and starts a fresh one. You always see results for your latest code.

​
Test run statuses

A run is marked passed or failed based only on test cases attributed to the current PR’s changes. Failures that appear to be pre-existing issues are surfaced as “additional findings” and do not affect the overall run status.

​
The PR list view

The dashboard home shows a table of all pull requests Ito has tested. Each row reflects the most recent test run for that PR.

​
Reading test result badges

The Test Results column shows up to three icons/emojis:
  • ✅ — test cases that passed.
  • ❌ — test cases that failed and are attributed to this PR’s changes.
  • ℹ️ — additional findings (pre-existing issues not related to your PR). The color of the icon/emoji is the color of the highest severity level among those findings.
If a run is still in progress, the column shows a Running… spinner instead.
Click any PR row to open the detail view and see individual test case results, video recordings, and code analysis.
  • Test Cases — what each test case inside a run contains
  • Severity Levels — how Ito classifies bugs by impact
  • PR Comments — the comment Ito posts to GitHub when a run completes
  • Repository — configure which repository’s PRs trigger runs