Bugmole documentation

Bugmole explores your app like a first-time visitor, turns what it finds into tests, runs them across browsers and devices, and shows what broke and why. Use it from the dashboard with nothing to install, from the bugmole CLI, or from an AI agent through Bugmole MCP.

What Bugmole does

• Explores your app from its URL, or your repository from the CLI, and maps its pages, forms and journeys.
• Turns what it finds into tests you can read, run and keep.
• Runs them on Chrome, Firefox, Safari, Edge and emulated phones at once, in Bugmole Cloud or on your own machines.
• Keeps every run with screenshots, logs, traces and an AI explanation of anything that failed, and flags flaky tests.
• Reports to GitHub, GitLab, Slack, Microsoft Teams and CI, and works with AI agents through Bugmole MCP.

What Bugmole tests

Bugmole tests web apps and mobile apps (Android and iOS). Data and AI projects, such as notebooks, pipelines and models, are out of scope. Each app is one project: an app on the internet is identified by its domain, and an app you run locally by its git repository and the app's folder in it. See Plans and limits.

Start here

1. Getting started — explore your app from the dashboard, or install the CLI.
   • Using the dashboard — what Overview, Tests, Runs and Issues are for.
2. CLI reference — learn the main commands.
3. Bugmole MCP — connect an agent to the framework.
   • Use Bugmole from your AI assistant — the hosted connector and the Bugmole skill.
4. Configuration — configure the runtime, your own AI model, MCP, and browser execution.
5. Sample tests — see what a Bugmole flow looks like, and how it compares with the same journey written by hand in Playwright, Cypress, and Selenium.
6. Discover and debug — explore an app from its URL, and find out why a run failed.
   • Credentials — sign in with passwords from your own vault, without pasting them anywhere.
   • How Bugmole finds what to test — where tests and test cases come from, what counts as covered, and where gaps remain.
7. GitHub App integration — link QA findings to GitHub issues.
8. Changelog — what changed in each release.

Bugmole is designed to keep the execution boundary explicit: local project workers run the app and tests, while the hosted dashboard and Bugmole's servers coordinate authorized project runs and display evidence.