> 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/creating-tests.md).

# Creating Tests

- [Your first test](https://docs.bugbug.io/creating-tests/recording-the-tests.md): Learn the basics of creating your first automated test with BugBug. The process is very simple and doesn't require any coding knowledge. See how easy it is to run your first test.
- [Independent tests](https://docs.bugbug.io/creating-tests/independent-tests.md): Learn why independent tests are crucial for end-to-end testing process. A good practice in automation testing is that every test is completely independent of other tests.
- [Duplicating tests](https://docs.bugbug.io/creating-tests/duplicating-tests.md): See how to duplicate your tests with BugBug without a need to create them from scratch.
- [New test from here](https://docs.bugbug.io/creating-tests/new-test-from-here.md): See how to avoid recording the same test steps multiple times. With BugBug you can duplicate them so that only part of the steps is copied over.


---

# 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/creating-tests.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.