Automatically smoke test every release
Ito runs on every release, maps the changes to user journeys, and tests for any regressions. No test cases to write. No suite to maintain.
How it works.
Set up once: connect your repo and add any plain-English instructions about what matters most to your team. From there, every smoke test runs automatically.
Ito understands the release
When ready to release, Ito reads the full release, along with the PR descriptions of related issues. Ito builds a full picture of what the change were intended to do, not only which files were touched.
Ito builds a smoke test plan
Ito decides what to test in three ways:
- The changes themselves. The diffs and PR descriptions, with no setup required. Ito reads all the code and issues.
- Your priorities. Instructions set at the repo, user, or organization level for what matters most: security, accessibility, mobile usability, performance, whatever your team prioritizes.
- What Ito has learned. Which bugs your team fixes, which you close as won't fix, and the feedback you give on past plans. Ito uses that signal to weight what it tests on future PRs, so teams that ship auth-heavy changes get sharper auth coverage over time. The plans get more accurate the more you use it.
Tests run every release
You configure when you want trigger Ito, then tests begin executing. You can watch the plan and its progress as Ito searches for regressions. If you want Ito to cover something more, you can ask for additional tests.
How it works.
Set up once: connect your repo and add any plain-English instructions about what matters most to your team. From there, every smoke test runs automatically.
Ito understands the release
When ready to release, Ito reads the full release, along with the PR descriptions of related issues. Ito builds a full picture of what the change were intended to do, not only which files were touched.
Ito builds a smoke test plan
Ito decides what to test in three ways:
- The changes themselves. The diffs and PR descriptions, with no setup required. Ito reads all the code and issues.
- Your priorities. Instructions set at the repo, user, or organization level for what matters most: security, accessibility, mobile usability, performance, whatever your team prioritizes.
- What Ito has learned. Which bugs your team fixes, which you close as won't fix, and the feedback you give on past plans. Ito uses that signal to weight what it tests on future PRs, so teams that ship auth-heavy changes get sharper auth coverage over time. The plans get more accurate the more you use it.
Tests run every release
You configure when you want trigger Ito, then tests begin executing. You can watch the plan and its progress as Ito searches for regressions. If you want Ito to cover something more, you can ask for additional tests.
"Ito saves my team by smoke testing every release. It always catches something"
"We have Ito on autopilot then do auto-cleanup from the issues it finds on release. It paid for itself in the second month by catching a major regression."
Questions teams ask before using Ito.
Common questions from engineering managers, senior engineers, and QA leads.
Your first PR tested within 60 minutes.
Connect your repo and Ito starts testing pull requests right away. Each PR includes a full QA report with video, screenshots, and failure details directly in the PR.
no credit card required