# Bug Bashes

## Run a full bug bash for deep feature testing. Automatically.

A bug bash means pulling your whole team into a room for an afternoon to click through the app and hunt for bugs before a big feature release. Ito runs that same sweep on demand - exercising every critical flow in a real browser and reporting exactly what breaks, with video and reproduction steps.

Start a bug bash →

no credit card required

## How it works.

Point Ito at your app and the release you're about to ship. From there the whole bug bash runs automatically — no test cases to write, no suite to maintain.

### Step 1: Ito maps your app

Ito reads your codebase and the release, then builds a picture of the critical user journeys across your whole product — not just the files that changed — so the bug bash covers what actually matters to your users.

### Step 2: Ito builds the bug bash plan

Ito decides what to hammer in three ways:

- **The release itself.** The diffs and PR descriptions, so the flows most affected by this change get the hardest look.

- **Your priorities.** Plain-English instructions at the repo or org level for what matters most: security, accessibility, mobile usability, performance — whatever your team cares about.

- **What Ito has learned.** Which bugs your team fixes, which you close as won’t fix, and the feedback you give on past runs. The plan gets sharper every bug bash.

### Step 3: Ito runs the bug bash on demand

Trigger a bug bash before any release. Ito exercises every flow in parallel in a real browser while you watch it work. Each issue comes back classified by severity with video, screenshots, reproduction steps, and the exact lines of code responsible — and you can ask Ito to cover more anytime.

## Questions teams ask before their first bug bash.

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

**Q: How is an Ito bug bash different from testing each PR?**

A: Per-PR testing focuses on what a single change could break. A bug bash is a full sweep across a new feature's critical flows — the kind of thing teams normally schedule before a big release and staff with the whole engineering team. Ito runs that entire sweep on demand, in parallel, so you can do it as often as you ship.

**Q: How long does an automated bug bash take?**

A: Instead of blocking your team for an afternoon, Ito runs flows in parallel and reports as it goes. You watch the plan execute in real time and get a complete report when it finishes — typically in a fraction of the time a manual bug bash takes.

**Q: Can we control what the bug bash covers?**

A: Yes. Add plain-English instructions at the org or repo level to tell Ito which flows to prioritize, deprioritize, or skip. After a run completes you can ask Ito to cover more.

**Q: What do we get when the bug bash finishes?**

A: A complete report: every issue found, classified by severity (Critical, High, Medium, Low) and by whether it is attributable to the current release or pre-existing — each with reproduction steps, video evidence, screenshots, and the specific lines of code responsible.

## Replace your next bug bash with a single click.

Connect your repo and run a full bug bash across your app on demand — no scheduling, no war room, no test cases to write. Every issue comes back with video, screenshots, and the exact code responsible.

Get Started

no credit card required