> For the complete documentation index, see [llms.txt](https://docs.bugbug.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugbug.io/master.md).

# Documentation

Step into the BugBug documentation section, where you'll find complete resources on how to use our tool and how to start with test automation for your website.

BugBug is a modern no-code test automation tool for software testers, developers, or product managers in need of quick & reliable test automation.

You can create and maintain your tests in two ways:

* **Record them in the browser** with the AI-Assisted Test Recorder, which captures stable tests without XPath or CSS expertise.
* **Let your AI agent build them** through [BugBug MCP](/ai-testing/mcp.md). Describe a flow in Cursor, Claude Code, Codex, VS Code or ChatGPT, and the agent creates, runs and fixes the test in your BugBug project.

BugBug allows you to effortlessly create and run end-to-end and regression tests for web applications, marketplaces, e-commerce, landing pages, etc.

* Are you new to the concept of automated browser tests? Read our step-by-step[ tutorial for beginners](/in-depth-guides/beginners-tutorial-to-automation-testing.md).
* Are you a seasoned QA engineer? Learn more about BugBug [best practices](/best-practices.md) and advanced features such as [components](/editing-tests/components.md), [variables](/editing-tests/variables.md), and [waiting conditions](/preventing-failed-tests/waiting-conditions.md).
* Are you a developer working with an AI coding agent? See [how to use AI with BugBug](/ai-testing/how-to-use-ai-with-bugbug.md) to create, debug and maintain tests from your editor.
* Are you a CEO, CTO or project manager? See our [tech leader's guide to automation testing.](https://bugbug.io/blog/guides/tech-leaders-guide-to-automation-testing/)

![](https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FgyyeRURordhyJZ479wy1%2Fbugbug-docs-illustration.png?alt=media\&token=4f84ac81-35de-4c87-93e3-726ed153520c)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bugbug.io/master.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.