Ito is an automated QA tool for pull requests, helping engineering teams catch regressions and usability issues without manual test scripts.
Ito is an automated QA product that audits pull requests with code-aware agents. It focuses on runtime behavior in a real browser so teams can catch regressions and usability issues without maintaining manual test scripts.
The product is aimed at fast-moving engineering teams that want coverage on every PR. Ito reads the diff and PR context, builds targeted test plans, runs the app in an isolated container, and posts evidence such as video, screenshots, repro steps, and bug details back to GitHub.
Ito reads the full PR diff and description, then builds a test plan around what the change is likely to affect. Teams can also add plain-English instructions for what matters most, such as security, accessibility, or performance.
Each PR runs in a clean, single-use container built from the change itself. Ito executes the application in a real browser against the actual code, rather than a mock or snapshot.
The agents work through sign-in, navigation, form submission, backend calls, and other app flows that the PR touches. The source emphasizes runtime behavior, including timing, state, and integration paths that static review cannot observe.
Ito records each run and posts results back to the PR and dashboard. Evidence can include video, screenshots, reproduction steps, and the exact lines of code responsible for a failure.
The system can run happy-path, edge-case, adversarial, logic, accessibility, mobile, and UX checks depending on what changed. The plan is weighted by the diff, the PR description, repo-level guidance, and learning from prior runs.
The product runs as a GitHub check and does not block merges by default, with per-repo configuration available. It is designed to fit into PR review rather than replace it.
Use Ito when a team wants automated coverage on each PR without writing and maintaining a separate test suite for every flow. The product is built to infer what changed from the diff and run the relevant checks automatically.
Use Ito for applications where runtime behavior matters more than static review, such as authentication, state changes, redirects, or backend calls that can fail only when the app runs.
Use Ito when reviewers need concrete evidence in the pull request, including a video clip, screenshots, and reproduction steps tied to the failure. That makes triage faster than a plain pass/fail signal.
Use Ito when teams want the test plan to reflect project priorities like accessibility, performance, mobile usability, or security. Those priorities can be supplied in plain English and applied across PRs.
Use Ito for GitHub-based review workflows where checks should run automatically but not necessarily block every merge by default. The product is designed to appear in the PR comment and GitHub check flow.
Ito replaces the manual regression layer of QA. It is designed for teams that want automated checks on pull requests while keeping strategic QA, exploratory testing, and release planning with people.
Ito runs your actual product in a real browser and exercises user flows end to end. The source describes this as behavioral testing rather than source-code-only analysis.
The pricing page says the team can get its first results in less than 60 minutes, and the FAQ says setup is about 60 minutes from install to the first PR tested. An admin on the GitHub organization can set it up to run on PRs.
When Ito finds a bug, it posts a GitHub comment on the PR with a video clip of the failure, repro steps, and the affected flow. The pricing page also says video and screenshots are posted directly in GitHub PRs.
Ito supports web apps and HTTP APIs today. The FAQ says native mobile is on the roadmap.
