> 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/recording-tests-steps.md). # Recording tests steps - [Test automation recorder](https://docs.bugbug.io/recording-tests-steps/bugbug-ai-test-recorder.md): 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. - [Recording clicks](https://docs.bugbug.io/recording-tests-steps/recording-clicks.md): See how recording clicks work. By default, when you record a test, BugBug records all your clicks. You don't need to activate any recording mode. - [Recording hover](https://docs.bugbug.io/recording-tests-steps/recording-hover.md): BugBug won't record hover events automatically. There is no reliable way of automatically detecting that something changed on the page because of cursor movement. - [Recording keyboard typing](https://docs.bugbug.io/recording-tests-steps/recording-keyboard-typing.md): See how to record keyboard typing with BugBug. During the recording, BugBug will automatically record everything you type in the text fields. You don't need to activate anything. - [Recording assertions](https://docs.bugbug.io/recording-tests-steps/recording-assertions.md): Learn what an assertion is and how to use it during recording your test with BugBug. Use assertions to check if your page behaves as it should, without interacting with it. - [Recording drag & drop](https://docs.bugbug.io/recording-tests-steps/recording-drag-and-drop.md) - [Record from here](https://docs.bugbug.io/recording-tests-steps/record-from-here.md): Read about Record from here feature. BugBug allows you to start recording from any step in your test. No need to record from scratch every time. - [Re-recording steps](https://docs.bugbug.io/recording-tests-steps/re-recording-steps.md): See how easy it is to re-record test steps with BugBug. If your test failed and you need to fix it, it's way faster to record the steps "from here" rather than edit them manually. - [Recording pop-up window actions](https://docs.bugbug.io/recording-tests-steps/recording-pop-up-window-actions.md) - [Using keyboard shortcuts](https://docs.bugbug.io/recording-tests-steps/using-keyboard-shortcuts.md) - [Test automation recorder FAQ](https://docs.bugbug.io/recording-tests-steps/ai-test-recorder-faq.md) - [How BugBug AI works](https://docs.bugbug.io/recording-tests-steps/how-bugbug-ai-works.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 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/recording-tests-steps.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.