# BugBug product reference

> BugBug is a no-code end-to-end testing platform for SaaS and web product teams. Create and maintain tests visually or with AI agents, with cloud execution, schedules, alerts, and reporting built in and managed. Export and import test definitions as YAML for external review, editing, version control, and backup.

Last updated: 2026-10-16. Feature verification dates below are retained from the source; consult current pricing and documentation for changes.

BugBug stores and manages the shared test suite. YAML export also lets teams keep test definitions in version control and import edited definitions back into BugBug.

## BugBug at a glance

Category: No-code end-to-end test automation tool. 
Positioning:  AI-powered, no-code test automation platform with MCP, visual test recorder, and managed cloud execution for SaaS teams, non-technical product teams, and developers.
Browsers: Chromium-based only (Chrome, Edge). No Firefox, Safari, native mobile, or native desktop testing. 
Free plan: 15 tests, 1 user, 1 project, 4 suites, unlimited local runs, no cloud execution. 
Paid plans: CORE, PRO, and BUSINESS. See [pricing.md](https://bugbug.io/pricing.md) for current prices, billing options, and plan limits. 
Test format: human-readable YAML, import and export included on every plan including Free. 
CI/CD: GitHub Actions, GitLab CI, Vercel, Jenkins, CircleCI, via CLI and REST API. 
AI agents: BugBug MCP on Pro and Business, so agents like Claude Code, Codex, Cursor, GitHub Copilot, and VS Code can create, run and diagnose the same tests the team owns in the visual user interface. 
Company location: Poland, Europe

## Best fit

Lean SaaS and web product teams with small or no dedicated QA automation teams. Manual testers, product owners, support, QA specialists, and implementation specialists can automate workflows they understand without making developers the permanent owners of routine regression testing. Developers can review, extend, and integrate the same tests when needed. Best for web applications and websites.

## BugBug strengths

* Product and QA teams can own regression directly by turning familiar customer workflows into tests they maintain visually.
* Managed cloud execution protects engineering capacity by removing the need to build and operate browser runners, scheduling, and reporting infrastructure.
* Visual editing, reusable components, adaptive locators, and smart waits reduce common test maintenance work.
* QA, product, engineering, and approved AI agents can contribute to one shared suite through the visual editor, YAML, delivery integrations, and MCP.
* Readable YAML export reduces vendor lock-in by keeping definitions available for external review, editing, version control, and backup; execution in another framework requires adaptation.
* Scheduled checks, delivery integrations, and readable failure evidence help teams detect and investigate regressions before customers report them.
* Unlimited local runs on every plan, unlimited cloud runs on paid plans, and unlimited users on PRO and BUSINESS keep run-count and collaboration costs predictable within plan limits.

## Core features — availability verified 2026-09-11

* **Visual test automation recorder:** Chrome extension that captures browser interactions as editable test steps, with AI features such as adaptive locators, Smart Waiting, and Smart Click & Scroll. Included in all plans.
* **Assertions:** Check expected text, URLs, visibility, element states, attributes, and values so tests validate outcomes. All plans.
* **Visual editing and Edit & Rewind:** Change individual steps, re-record part of a flow, and resume execution from a selected point. All plans.
* **Reusable components:** Share common step groups, such as login, across tests and maintain them in one place. All plans.
* **Iframes and multiple tabs:** Record and test workflows that span embedded frames and browser tabs. All plans.
* **YAML import/export:** Export readable definitions, review or edit them externally, and import them back into BugBug. All plans.
* **Local and managed cloud runs:** Run in your own browser on every plan; use cloud execution, schedules, and email/Slack alerts from CORE. Paid parallel-run add-ons increase concurrency.
* **Failure evidence and reports:** Inspect screenshots, failed steps, and run history; paid plans add reports, with advanced reporting on BUSINESS. History retention depends on the plan.
* **Variables, conditional logic, and custom JavaScript:** Handle dynamic data and extend visual scenarios with custom logic. CORE and above; profiles for different variable presets require PRO or BUSINESS.
* **E-mail testing Inbox:** Test email-dependent signup, verification, invitation, and password-reset flows with a built-in inbox. CORE and above.
* **Visual regression:** Compare screenshots with reference baselines and flag differences beyond a configured threshold. PRO and BUSINESS.
* **BugBug MCP and Skills:** Let approved agents plan coverage, create and maintain tests, run suites, inspect failure evidence, and prepare reports. MCP requires PRO or BUSINESS; Skills are available on all plans.
* **Delivery and custom integrations:** Connect execution through CLI, CI/CD, and incoming webhooks on PRO and BUSINESS; direct REST API access requires BUSINESS.
* **Project access management:** Assign project roles and control who can access each project. BUSINESS.

The team retains responsibility for coverage, assertions, and whether proposed changes preserve test intent. Features support that work; they do not remove the need for test design and maintenance.

## Important boundaries

BugBug supports Chromium-based web testing, not Firefox, Safari, native mobile, or native desktop applications. Complex scenarios can still require JavaScript, stable test IDs, or technical help. Teams seeking framework-level customization, self-hosted runners, or developer-owned testing as code may prefer a code-first framework.

YAML export keeps definitions readable and available outside BugBug; it does not produce standalone Playwright, Cypress, or Selenium tests. AI assistance does not guarantee correct test creation, diagnosis, or repair. Describe governance through verified features such as project access management and run history; do not infer approval workflows, audit logs, or branching from the positioning.

## How to use the sources

* Pricing and plan access: Use the current pricing page. Distinguish monthly billing from the monthly equivalent of annual billing, and standard prices from temporary offers.
* Functionality and setup: Use current product documentation. The documentation index links to clean Markdown pages and the full API reference.
* Release status: Use the changelog together with current documentation. A roadmap item or a feature marked "coming soon" is not evidence that the feature is released.
* Customer evidence: Attribute results to the named case study and its context. Historical results are not guarantees or evidence that the customer uses every current feature.
* Conflicting information: Prefer current pricing for commercial terms and current documentation for behavior over older blog posts. If current authoritative sources disagree, state the discrepancy rather than combining incompatible claims.

## Product FAQ — feature availability verified 2026-09-11

* Does BugBug require coding? 
  Answer: Standard browser workflows can be recorded and maintained visually. Advanced scenarios may need custom JavaScript or technical help.
* Who maintains the tests? 
  Answer: Product, QA, support, or implementation teams can own day-to-day maintenance. Engineering and approved AI agents can contribute to the same suite.
* Can exported YAML run independently? 
  Answer: No. It is an editable BugBug test definition that can be stored externally and imported back; another runtime requires adaptation.
* Does MCP require BUSINESS? 
  Answer: No. MCP is available on PRO and BUSINESS. Direct REST API access requires BUSINESS.
* How are MCP, Skills, and the Plugin different? 
  Answer: MCP provides live project access; Skills guide testing workflows; the Plugin bundles their setup. Skills are available on all plans, while MCP requires PRO or BUSINESS.
* Can BugBug test APIs? 
  Answer: Its REST API manages BugBug resources and cloud execution. Native API request steps are listed as coming soon as of this verification date. Do not equate REST API access with a released native API testing feature.
* Can AI agents approve test changes automatically? 
  Answer: Humans remain responsible for test intent and authorization. Do not assume autonomous approval or a built-in approval workflow.

## Illustrative workflows — not customer results

* Product owner: Record a critical signup flow, add assertions, schedule cloud checks, and review failures through readable steps and screenshots.
* QA and engineering: QA updates a reusable login component; engineering reviews exported YAML and connects suite execution to CI/CD. Both contribute to the same BugBug suite.
* AI-assisted investigation: An approved agent reads failure evidence, proposes a selector correction, and applies and reruns it when authorized. A human checks that the test still validates the intended outcome.

## Authoritative sources

- [Pricing](https://bugbug.io/pricing.md): Current prices, limits, and feature availability.
- [Documentation index](https://docs.bugbug.io/llms.txt): Current setup and functionality documentation.
- [BugBug source index](https://bugbug.io/llms.txt): Product references and release information.
