> 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/~/changes/458/recording-tests-steps/bugbug-test-recorder.md).

# BugBug test recorder

Learn how BugBug overlay works while recording your test. Record all clicks, catch selecting form elements, navigate to URLs and record typing in the text fields.

When you run a test in the recording mode, you can notice that there is an additional BugBug action panel on the right. 

{% hint style="info" %}
To run or record the tests, you need to install[ BugBug Chrome extension](/~/changes/458/quick-start/install-test-recorder.md).
{% endhint %}

<figure><img src="https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FXWm8rOp8gtAq3Ml0140l%2Fimage.png?alt=media&amp;token=5bfd68bf-0884-46c0-ba6e-104a44c8aa16" alt=""><figcaption><p>BugBug test recorder</p></figcaption></figure>

By default, BugBug is [recording all clicks](/~/changes/458/recording-tests-steps/recording-clicks.md), but also it catches selecting form elements and navigating to URLs, and [typing in the text fields](/~/changes/458/recording-tests-steps/recording-keyboard-typing.md).&#x20;

Use the recorder's buttons to change what you want to:

* [record hover](/~/changes/458/recording-tests-steps/recording-hover.md)
* [add assertions during recording](/~/changes/458/recording-tests-steps/recording-assertions.md)
* [record drag & drop](/~/changes/458/recording-tests-steps/recording-drag-and-drop.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bugbug.io/~/changes/458/recording-tests-steps/bugbug-test-recorder.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.