> 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/quick-start/install-test-recorder.md).
# Install Test Recorder
Run and record your tests with BugBug Chrome Extension in incognito mode. See how easy is the process of setting up BugBug for your test automation.
### Why do you need the test recorder?
To run and record the tests, BugBug requires you to install a Chrome Extension-based [test automation recorder.](https://bugbug.io/test-automation-recorder/)
This extension must be installed and **enabled** **in** **Incognito** **mode**.
### Why does the extension require incognito mode?
Each test should run in complete isolation to ensure reliability and consistency. This means starting every test with a clean environment, free of cookies, cache, localStorage, and other session data.
To achieve this, BugBug executes tests in Incognito mode. Every test run begins by closing any existing Incognito session and opening a new window, guaranteeing a fresh, clean state each time.
### Install the extension
Go to [BugBug Extension on the Chrome Webstore](https://chrome.google.com/webstore/detail/bugbug-no-code-test-autom/oiedehaafceacbnnmindilfblafincjb/related) and install it.
### Enable the extension in Incognito mode
1. Go to extension settings by clicking the **"Go to extension settings"** button or use the link below
`chrome://extensions/?id=oiedehaafceacbnnmindilfblafincjb`
Scroll down, then enable the switch near **"Allow in Incognito"**
That's it! You're ready to run and record the tests now.
***
#### \[Opera Only] Allow access to search page results
The BugBug extension requires the 'Allow access to search page results' permission to function properly in Opera. When this option is disabled, Opera blocks access to sandboxed iframes, such as reCAPTCHA. Therefore, attaching to tabs containing these types of frames is not allowed.
{% hint style="info" %}
We take your privacy seriously. This permission is used solely for recording and running tests.\
We never collect, store, or share your search queries or personal data.
{% endhint %}
1. Go to extension settings by clicking the "Go to extension settings" button or use the link below
`chrome://extensions/?id=oiedehaafceacbnnmindilfblafincjb`
2. Scroll down, then enable the switch near "Allow access to search page results"
---
# 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/quick-start/install-test-recorder.md?ask=&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.
