Axolotl

AI that tests your code before you merge it.

Point it at a PR. It reads the diff, analyzes the code, generates tests,
opens a real browser, clicks through your app, and tells you if it's safe to ship.

Axolotl testing a live app — clicking buttons, checking responses, capturing evidence.

The Problem

You open a PR. You eyeball the diff. You run the existing test suite — it passes. You merge.

Two hours later, production breaks. The tests didn't cover the actual user flow that changed.

Axolotl fixes this. It reads your code changes, figures out what should be tested, and actually tests it — in a real browser, against your real app.

See Every Step

1. Sign In One-click Google sign in. Only used for future update notifications — no usage data is collected. Watch full video →

2. Configure Set your Anthropic API key and You.com API key for web search. We recommend Claude Sonnet 4.6 (1M) — all browser testing is optimized for Sonnet. Watch full video →

3. Start a QA Session Pick your source: a PR number, uncommitted changes, or specific files. Or just type in the chat box. Watch full video →

4. Code Analysis Tree-sitter AST parsing + ripgrep pattern search. Axolotl understands your code structure before writing any tests. Watch full video →

5. Web Search & Test Cases Searches for testing best practices specific to your tech stack, then generates targeted test cases. Watch full video →

6. Plan & Log Injection Review the test plan. On approval, Axolotl injects temporary log markers to capture behavioral evidence. Watch full video →

7. End-to-End Testing Real browser. Real clicks. Real screenshots. Monitors frontend UI and backend output simultaneously. Watch full video →

8. Report & Memory Evidence-backed verdict with pass/fail per test case. Axolotl remembers your project setup for next time. Watch full video →

Quick Start

1. Clone & Install

git clone https://github.com/Axolotl-QA/Axolotl.git
cd Axolotl
npm install
npm run build:webview
npm run dev

Press F5 to launch the Extension Development Host.

2. Configure

3. Run

--source=pr --pr=123              ← test a pull request
--source=uncommitted              ← test your working changes
--source=files @src/auth.ts       ← test specific files

Or just describe what you want tested in the chat box.

Why Axolotl

Key Features

Zero test maintenance — tests are generated on-the-fly from your actual code changes. No test suite to maintain.

Evidence-driven verdicts — every result is backed by screenshots, console logs, and injected behavioral markers. Not just pass/fail.

Human-in-the-loop — you review the test plan, approve each phase, and decide what to do with the results.

Persistent memory — Axolotl remembers how to install deps, start your dev server, and run your app across sessions via axolotl.md.

Web-informed — searches the internet for testing best practices relevant to your specific tech stack before generating test cases.

Multi-language analysis — tree-sitter powered AST parsing for JavaScript, TypeScript, Python, Rust, Go, C/C++, C#, Ruby, Java, PHP, Swift, and Kotlin.

Contributing

We'd love your help. See the Contributing Guide for details.

git clone https://github.com/Axolotl-QA/Axolotl.git
cd Axolotl
npm install
npm run dev            # watch mode
npm run build:webview  # build UI
# F5 to launch

License

Apache 2.0 — see LICENSE.

Built on Cline. Extended for automated QA.