Ito

Ito is an AI code review tool that runs your app on every pull request to catch runtime bugs before merge. It helps engineering teams verify behavior with evidence such as video, logs, screenshots, and reproduction steps.

Monitorización y Logs IA Testing y QA Herramientas IA Dev

Visitar Sitio Web

AI code review that runs your app on every pull request

Ito is an execution-based code review tool that tests a real build of your application on every pull request. It uses the PR diff and description to decide what to exercise, then runs affected user flows in a browser-like environment to surface regressions and runtime bugs before merge.

It is built for engineering teams that want automated runtime verification instead of manual PR testing or brittle test scripts. Findings are posted back into GitHub with evidence such as video, logs, screenshots, reproduction steps, and the lines of code tied to the issue.

Core capabilities

PR-aware test planning

Ito reads the diff and PR description to build a test plan around the user journeys the change could affect, rather than relying on a fixed suite.

Containerized app execution

For each PR, Ito builds and runs a single-use copy of the app from source so it can test the real running application and backend behavior.

Runtime evidence in pull requests

When a failure is found, Ito posts supporting evidence directly in the PR, including video, screenshots, logs, reproduction steps, and severity context.

Automatic re-run after fixes

After a developer pushes a fix, Ito can re-run the relevant checks to confirm the issue is resolved before the change is merged.

Plain-English control over coverage

Teams can add instructions at the repo, user, or organization level to prioritize, de-prioritize, or skip specific flows without writing test code.

Release and smoke-test triggers

In addition to PR testing, Ito can run smoke tests on a schedule, from GitHub workflows, or on demand for release validation.

Ways teams use Ito

Verify every pull request before merge
Use Ito to check that changes did not break the flows they touch, with results attached to the PR so reviewers can make a merge decision with runtime evidence.
Replace manual regression checks
Teams that currently spend time clicking through core flows on every PR can automate that repetitive verification while keeping humans focused on exploratory testing and release planning.
Run smoke tests before release
Trigger Ito on a nightly, release-based, or on-demand cadence to catch regressions across a broader surface area before shipping.
Exercise full-app bug bashes automatically
Use Ito to run a wide sweep of critical flows on demand for deeper release testing, without assembling the whole team for manual clicking.
Support QA for agent-written code
Teams shipping a high volume of AI-generated or rapidly changing code can use Ito as a runtime check that validates behavior rather than only reading the diff.

Pros and Cons

Pros

Runs the actual app and backend code instead of only analyzing the source diff.
Posts findings directly in GitHub PRs with evidence that helps triage issues quickly.
Does not require teams to write or maintain their own test scripts.
Can be guided with plain-English instructions for repository- or team-level priorities.
Supports multiple workflows, including PR checks, smoke tests, and on-demand release validation.

Cons

Setup and results are focused on web apps and APIs; native mobile is described as being on the roadmap.
Reviews can take from about 30 minutes to 2 hours depending on change complexity and codebase size.
The platform is designed to complement, not replace, human QA work such as exploratory testing and release planning.

FAQ

Does Ito write or maintain test cases for you?

No. The product is positioned as scriptless, so teams do not need to write or maintain a traditional test suite. You can add plain-English instructions to guide coverage, but that is optional.

What does Ito return when it finds a problem?

Ito posts a GitHub comment on the pull request with the failing lines of code, severity, evidence for the issue, reproduction steps, and other runtime details such as video or screenshots.

How is Ito different from Playwright or Cypress?

Playwright and Cypress require engineers to create and maintain test scripts. Ito instead generates and runs checks from the app and PR context, aiming to adapt as the UI changes without a brittle selector-based suite.

What kinds of applications can Ito test?

The source says Ito supports web apps and APIs, and describes it as framework agnostic. Native mobile support is mentioned as being on the roadmap.

How quickly can a team get started?

The site says teams can connect a GitHub repository and begin testing within about 60 minutes, with first PR results typically available after setup.

Quick Facts

Category: Developer Tool
Primary use: AI code review and runtime PR testing
Platform focus: GitHub pull requests
Supported targets: Web apps and APIs
Site: ito.ai
Pricing signal: Paid plans available, with a Pro plan and an open-source free option for qualified projects