# Smoke Testing

## Automatic smoke test every night, every release, or on-demand.

Based on your trigger, Ito maps the application changes and tests for any regressions. No test cases to write. No suite to maintain.

Targeted test plans

Automate smoke testing →

Watch 2 min demo

## 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.

### Step 1: Ito understands the release

When ready to release, Ito reads the full changes, 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.

### Step 2: 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.

### Step 3: Tests run every time

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""
>
> VP Engineering

> ""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.""
>
> CTO / Founder

## Questions teams ask before using Ito.

Common questions from engineering managers, senior engineers, and QA leads.

**Q: How does Ito decide which regressions tests to run during the smoke test?**

A: Three ways, and all three work together. First, the actual code changes and relevant PR description: this is zero-shot and works with no setup. 

Second, instructions your team sets at the repo, user, or organization level to prioritize what matters most, like security, mobile usability, or accessibility. 

Third, what Ito learns over time from the bugs your team fixes or closes as won't fix and the feedback you give on test plans. The result is a plan targeted at the real risk surface of that change, personalized to your team and sharper with every run.

**Q: What do the smoke test plans look like?**

A: A full test plan tagged by category and visible in your dashboard and in GitHub. After execution, you get a complete report: tests run, issues found with severity classification, reproduction steps, video evidence, screenshots, and the specific lines of code responsible for each failure.

**Q: How are issues classified?**

A: When Ito finds a problem, it is classified independently by severity based on business impact (Critical, High, Medium, Low) and by whether it is attributable to the current release or pre-existing.

**Q: Can we control what Ito tests?**

A: Yes. Add plain-English instructions at the org or repo level to tell Ito which flows to prioritize, deprioritize, or skip on specific test types. You can ask Ito to run additional tests after a run completes.

**Q: What are the triggers for the smoke test?**

A: Ito is configurable so you can trigger smoke tests as you see fit. Ito tests every PR by default. Layer in smoke tests on timed cadence, based off a GitHub workflow, or on-demand triggers like Slack.

## 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.