# Testing

We recommend the [**@web/test-runner**](https://modern-web.dev/docs/test-runner/overview/) tool, if your project was created with the command `npm init @atomico` the test environment will be preconfigured, you can see this pre-configuration at <https://github.com/atomicojs/base/tree/2-started>.

{% content-ref url="testing/test-dom" %}
[test-dom](https://atomico.gitbook.io/doc/api/testing/test-dom)
{% endcontent-ref %}

{% content-ref url="testing/atomico-test-dom" %}
[atomico-test-dom](https://atomico.gitbook.io/doc/api/testing/atomico-test-dom)
{% endcontent-ref %}

{% content-ref url="testing/test-hooks" %}
[test-hooks](https://atomico.gitbook.io/doc/api/testing/test-hooks)
{% endcontent-ref %}

### Advanced (Documentation in progress)

To scale the test environment you can complement with tools such as:

1. [**Cypress**](https://www.cypress.io/): allows you to automate interactions and evaluate interactions of your interface.
2. [**Percy**](https://percy.io/): Allows you to evaluate the appearance changes of your component or application between versions.


---

# Agent Instructions: 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:

```
GET https://atomico.gitbook.io/doc/api/testing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.