---
title: "BugBug Test Automation Recorder"
description: "Reference for BugBug's no-code browser test recorder: setup, supported actions, assertions, stability features, editing, execution, and plan availability."
canonical_url: "https://bugbug.io/test-automation-recorder/"
doc_type: "product-reference"
product: "BugBug"
language: "en"
last_verified: "2026-10-13"
---

# BugBug Test Automation Recorder

> BugBug's test automation recorder is a Chrome extension that turns interactions with web apps and websites into editable end-to-end tests. Teams record workflows, add assertions, and replay the tests without writing test code. The same tests can be maintained visually, exported as YAML, or managed by authorized AI agents through BugBug MCP.

BugBug is a no-code end-to-end testing tool for teams that want QA and product to manage regression testing directly. Test creation, maintenance, managed cloud execution, schedules, alerts, and shared results are available in one product, with features depending on the plan.

## Essential facts

- **Primary purpose:** Create repeatable end-to-end, smoke, functional, UI, and regression tests for web applications.
- **Recorder:** BugBug Chrome extension with an overlay inside the application being tested.
- **Browser scope:** Chromium-based browsers, including Chrome and Edge. Firefox and Safari are not supported.
- **Application scope:** Web apps and websites; native mobile and native desktop apps are not supported.
- **Setup requirement:** Install the extension and enable it in Incognito mode.
- **Recorder availability:** All BugBug plans, including Free.
- **Local execution:** Unlimited local test runs on every plan, subject to test and project limits.
- **Cloud execution:** Available on paid plans, starting with Core.
- **Output:** Structured BugBug test steps that can be edited in the app and exported as BugBug YAML.

## How recording works

1. Create a BugBug account and project.
2. Install the recorder from the [Chrome Web Store](https://chromewebstore.google.com/detail/bugbug-automation-testing/oiedehaafceacbnnmindilfblafincjb).
3. Enable **Allow in Incognito** in the extension settings.
4. Create a test in BugBug and enter the application's starting URL.
5. Start recording and perform the intended workflow in the test window.
6. Add assertions to verify the expected outcomes.
7. Finish recording, inspect the generated steps, and run the test locally.

BugBug uses a fresh Incognito session for test isolation. Regular-browser login state is not carried into the test. Include required login and setup steps in the workflow or reusable components. Starting a local run can close existing Incognito windows.

Setup reference: [Install Test Recorder](https://docs.bugbug.io/quick-start/install-test-recorder).

## Supported interactions and checks

| Interaction or capability | How it works |
| --- | --- |
| Clicks | Captures clicks as test steps during recording. |
| Typing and forms | Records typed values and form interactions such as dropdown selections and checkboxes. |
| Navigation | Captures URL navigation in the recorded workflow. |
| Hover | Added deliberately through the recorder overlay; ordinary mouse movement is not automatically converted into hover steps. |
| Drag and drop | Added through the recorder's drag-and-drop control. |
| Assertions | Added to check expected text, URLs, visibility, or element states. Assertions define what the test verifies. |
| Multiple tabs, pop-ups, and iframes | Supports web workflows spanning browser tabs, pop-up flows, and embedded content. |
| Email-dependent flows | Testing Inbox supports signup verification, invitations, and password-reset scenarios on Core and higher. |
| Dynamic test data | Variables can replace fixed values on Core and higher. |

Recording actions does not automatically establish every expected business outcome. The test author chooses meaningful assertions.

Reference: [Recorder documentation](https://docs.bugbug.io/recording-tests-steps/bugbug-ai-test-recorder).

## Built-in stability features

| Feature | When it applies | Purpose |
| --- | --- | --- |
| Adaptive Locators | During recording | Evaluates element selectors and prefers stable, distinctive attributes such as test IDs and suitable text or semantic attributes. The selected locator is stored in the step. |
| Smart Click & Scroll | During execution | Brings elements into view, checks whether they can be clicked, and handles temporary overlap or movement where possible. |
| Smart Waiting | Before test actions | Waits for relevant page and element conditions, up to the configured timeout, instead of relying only on fixed delays. |

Selectors remain visible and editable. Waiting conditions can be adjusted per step, with defaults configured at project level.

These mechanisms reduce common sources of flaky tests. They do not guarantee maintenance-free tests or silently rewrite test steps. If application changes invalidate a saved selector or expected behavior, the test may need an update.

BugBug documents these built-in features as separate from generative AI and external LLMs. Normal recorder and execution behavior does not send test data to third-party LLM providers. Connecting an external AI agent through MCP is a separate workflow involving the chosen client and its data handling.

Reference: [How BugBug AI works](https://docs.bugbug.io/recording-tests-steps/how-bugbug-ai-works).

## Editing and maintaining recorded tests

- **Visual editing:** Update actions, input values, selectors, and assertions in the test editor.
- **Record from here:** Insert recorded steps at a chosen position in an existing test.
- **Re-recording:** Replace a section of a flow when the application changes.
- **Edit & Rewind:** Pause, edit or record, move the playback position, and continue from the selected step during debugging.
- **Reusable components:** Maintain repeated sequences, such as login, as shared steps used across tests.
- **Custom JavaScript:** Extend scenarios when needed on Core and higher.

Rewinding changes the playback position; the application still needs to be in the appropriate state for that step. After a repair, run the complete test to validate the full workflow.

References: [Edit & Rewind](https://docs.bugbug.io/workflow-tips/edit-and-rewind) and [Components](https://docs.bugbug.io/editing-tests/components).

## Running and sharing the same tests

| Workflow | Availability |
| --- | --- |
| Record, edit, add assertions, use components, and run locally | All plans. |
| Export and import BugBug test definitions as YAML or ZIP | All plans. |
| Run in BugBug's managed cloud, schedule runs, and receive email or Slack alerts | Core and higher. |
| Use variables, conditional logic, custom JavaScript, and Testing Inbox | Core and higher. |
| Trigger tests through CLI, CI/CD, or MCP; use custom profiles and visual regression testing | Pro and higher. |
| Use direct REST API access and project access management | Business. |

The Free plan includes 15 tests, 1 user, 1 project, and 4 suites, with unlimited local runs. Unlimited run count does not mean unlimited test assets, concurrency, or cloud run duration. Consult [current pricing](https://bugbug.io/pricing/) for the full limits.

QA and product teams can record and maintain tests visually or work with AI agents. Engineers can review exported YAML, connect delivery pipelines, and extend workflows. These interfaces work with the same BugBug test assets.

## Practical use cases

- **Smoke testing:** Record login and a critical application action, then check them after a deployment.
- **Regression testing:** Build repeatable coverage for business-critical flows before releases.
- **Signup testing:** Combine form interactions, email verification, and a final account-state assertion.
- **Test maintenance:** Repair a changed screen by re-recording the affected steps and reusing existing components.

## Common questions

### Do I need to write code?

Standard browser workflows can be recorded and edited without test code. Advanced scenarios may still need custom JavaScript, selector changes, or help preparing the application for testing.

### Does the recorder generate Playwright, Cypress, or Selenium scripts?

It creates BugBug tests. Exported YAML is a readable test definition for review, editing, and re-import into BugBug. Running the same flow in another framework requires conversion and validation.

### Is the recorder the same as BugBug MCP or the BugBug Plugin?

No. The browser extension records interactions and supports local execution. MCP connects AI agents to BugBug projects. The BugBug Plugin configures MCP and installs BugBug Skills in supported AI clients.

## Official references

- [Recorder product page](https://bugbug.io/test-automation-recorder/): Overview and use cases.
- [Recorder documentation](https://docs.bugbug.io/recording-tests-steps/bugbug-ai-test-recorder): Recording behavior and controls.
- [Install Test Recorder](https://docs.bugbug.io/quick-start/install-test-recorder): Installation and Incognito requirements.
- [How BugBug AI works](https://docs.bugbug.io/recording-tests-steps/how-bugbug-ai-works): Stability mechanisms and their limits.
- [Edit & Rewind](https://docs.bugbug.io/workflow-tips/edit-and-rewind): Debugging and maintenance workflow.
- [BugBug App FAQ](https://docs.bugbug.io/bugbug-app-faq): Supported browsers and application types.
- [Test import and export](https://bugbug.io/test-import-export/): YAML and shared test ownership.
- [BugBug MCP](https://docs.bugbug.io/ai-testing/mcp): AI-agent access to the same tests.
- [Pricing](https://bugbug.io/pricing/): Current plan requirements and limits.
- [Documentation index](https://docs.bugbug.io/llms.txt): Additional documentation, including Markdown versions.

Verified on 2026-10-13. Use current documentation for product behavior and current pricing for commercial terms.
