> 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/troubleshooting/prohibited-behaviors.md).

# Prohibited behaviors

Things to avoid while recording and running BugBug tests locally: minimizing the test window, switching desktops on macOS, and other browser extensions such as password managers that change the page.

{% hint style="success" %}
[Read how to prepare your app for automated testing and avoid common pitfalls.](https://docs.bugbug.io/best-practices.md#how-to-prepare-your-app-for-testing)
{% endhint %}

## You cannot minimize the test window

Don't minimize the window that is running a local test. Chrome puts a minimized window into standby mode and stops running JavaScript in it, so the **test stops** with a message that the window has been minimized or lost focus.

On macOS, also don't switch to another desktop (Space) while the test is running. It has the same effect.

If you want to run tests without disrupting your work, [run them in the cloud](https://docs.bugbug.io/running-tests/in-cloud-on-server.md).

<figure><img src="https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2Fg6ozQFnZjNaceU72ujfi%2FProjekt%20bez%20tytu%C5%82u.png?alt=media&amp;token=831ea469-6935-4a9e-9843-44efe24f54bc" alt=""><figcaption></figcaption></figure>

## New windows open as tabs

BugBug records and runs each test in a single browser window. When your app opens a new window, for example with *window\.open()* or a 3rd party login popup, BugBug always opens it as a new tab in the same window and switches the test context to it. This works for any number of windows.

Learn more in [Recording pop-up window actions](https://docs.bugbug.io/recording-tests-steps/recording-pop-up-window-actions.md) and [Tabs & iframes](https://docs.bugbug.io/editing-tests/tabs-and-iframes.md).

## Other browser extensions can change the page

Password managers, spelling checkers and similar extensions add their own elements to the page and fill in fields. During recording this can end up in your selectors and steps. The test can then fail in the cloud, or for another person who runs it locally without that extension.

BugBug shows the warning **BugBug detected conflicting extensions** when it notices one of these: 1Password, LastPass, Bitwarden, Dashlane, Keeper, NordPass, Proton Pass, Grammarly or Jam. Other extensions can cause the same problem without a warning.

To make sure your tests run correctly, before you record or edit a test:

* disable other extensions, completely or only in incognito mode, or
* create a separate Chrome profile without other extensions and use BugBug there.

<figure><img src="https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FofOak3Rce90kDiahRVUZ%2FLastPassLogoShadow.png?alt=media&amp;token=6c7a6695-528c-42cb-96f3-4a3ef7840b5a" alt=""><figcaption><p>Turning off an extension, here LastPass, in incognito mode</p></figcaption></figure>


---

# 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/troubleshooting/prohibited-behaviors.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.
