# AI test recorder FAQ
What is the AI-Assisted Test Recorder?
BugBug's [AI-Assisted Test Recorder](https://bugbug.io/ai-test-recorder/) is the Chrome extension that records your interactions and automatically applies three AI-powered capabilities to make tests stable from the first run:
* [Adaptive Locators](/preventing-failed-tests/selectors.md) — AI evaluates multiple selector strategies for each element and picks the most stable one. It prioritizes data-testid attributes, semantic roles, and visible text over fragile dynamic IDs or positional CSS.
* [Smart Click & Scroll](/preventing-failed-tests/smart-click.md) — AI mimics real user behavior when interacting with dynamic UIs, reducing failures caused by elements that appear only on hover or after scroll.
* [Smart Waiting](/preventing-failed-tests/waiting-conditions.md) — AI detects when a page or element isn't ready and waits appropriately — no manual sleep steps or timeout tuning required.
These features work automatically during recording. You don't configure them; you just click through your app as you normally would.
Does the AI recorder fix failed tests automatically?
Not automatically, but it significantly reduces why tests fail in the first place. Adaptive Locators choose stable selectors at recording time, and Smart Waiting eliminates the most common timing-related failures.
When a test does fail, BugBug gives you the tools to fix it quickly:
* [Edit & Rewind ](/workflow-tips/edit-and-rewind.md)— re-record from any specific step without starting over.
* [Record from here](/recording-tests-steps/record-from-here.md) — add missing steps (like a forgotten hover) at the exact point of failure.
* [Screenshots](/debugging-tests/screenshots.md) — captured at each failed step so you can see what BugBug saw.
Are the AI features available on all plans, including the Free plan?
Yes. The [AI-Assisted Test Recorder](https://bugbug.io/ai-test-recorder/) — including Adaptive Locators, Smart Click & Scroll, and Smart Waiting — is available on all plans, including Free. These features are part of the core recording experience, not a paid add-on.
Features that require a paid plan are cloud test runs, parallel execution, scheduling, and advanced reporting.
\
See full plan comparison: [bugbug.io/pricing](https://bugbug.io/pricing/)
How does BugBug handle dynamic UIs and pages that change frequently?
Dynamic UIs are one of the most common causes of broken tests in other tools. BugBug's AI recorder addresses this at three levels:
* **Adaptive Locators** avoid brittle CSS class names and dynamic IDs — the selectors it generates are much less likely to break when your UI is updated.
* **Smart Click** handles elements that only appear on hover, after animations, or inside modals — it mimics real user behavior rather than blindly targeting a DOM coordinate.
* **Smart Waiting** detects when the page is still loading or an element isn't yet interactive, and waits accordingly instead of failing immediately.
\
For highly dynamic content (live lists, search results, real-time data), you may still want to use [variables](https://docs.bugbug.io/editing-tests/variables) or [conditional logic](https://docs.bugbug.io/editing-tests/actions) for the most reliable results.
Does BugBug generate tests automatically from a URL or description?
Not currently. BugBug's AI assists and stabilizes the recording process — it doesn't generate test steps from a prompt or crawl your app autonomously. You record tests by interacting with your application yourself, and the AI works in the background to make those recorded steps stable and reliable.
This is a deliberate design choice: you stay in control of what gets tested, and every step is transparent and auditable by your team.
\
If fully autonomous AI test generation is a priority, we recommend checking out our [roadmap](https://bugbug.io/contact/) or contacting support to share your use case.
Will using BugBug's AI features send my app's data to a third-party AI provider?
BugBug's infrastructure is hosted in the EU (Gdańsk, Poland) and access to the database is strictly limited to the BugBug application. The AI capabilities in the test recorder (Adaptive Locators, Smart Click & Scroll, Smart Waiting) operate within BugBug's own infrastructure — your app's content and test data are not passed to external LLM providers as part of normal recording or test execution.
\
For more on data security, see: [How secure is BugBug?](https://docs.bugbug.io/bugbug-app-faq) and [How is data from recorded test runs stored?](https://docs.bugbug.io/bugbug-app-faq)
How is BugBug different from AI testing tools like Momentic or KaneAI?
Most AI testing tools in 2026 fall into two camps: fully autonomous agents (Momentic, KaneAI, QA Wolf) that generate tests without any human input and typically cost $40K–$250K/year, or code-based tools (Playwright + Claude Code) that require developer fluency.
BugBug sits in neither camp. It's designed for the 20–150 person SaaS team where nobody or a few people owns QA full-time:
* **You stay in control** — AI assists the recording, but you define what gets tested. Tests are auditable step-by-step, not black-box generated.
* **No Playwright required** — non-technical team members (QA, PMs, product owners) can record, run, and read tests without writing code.
* **Flat, transparent pricing** — BugBug's plans don't hide pricing behind "contact sales." You pay a flat subscription; AI features are included, not billed per-agent-session or per-AI-call.
* **Human-on-the-loop** — BugBug's AI augments your judgment rather than replacing it. You confirm, edit, and own the test steps.
\
Learn more: [BugBug pricing](https://bugbug.io/pricing/)
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.bugbug.io/recording-tests-steps/ai-test-recorder-faq.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.