# Running tests

When we are ready with our test suite we can run the tests. Click on **Run..** item in the main menu (or press **F6**).

![Run tests menu item](/files/-Lh_4MS0_BVJ9fXnADzm)

You get **Run reports** modal window

![Run reports modal window](/files/-Lh_4isNh4JBLSb0YVQK)

By default Puppetry runs tests in headless mode, meaning it launches Chromium in background. You can make to run the tests in Chrome browser with **Run in browser** switch:

![Chmonim options](/files/-Lh_57y6IMojqXU2vGKg)

This opens an input for [Chromium command line options](https://peter.sh/experiments/chromium-command-line-switches/)

&#x20;The modal window also allows you to select a [target environment](https://docs.puppetry.app/template):

![Selecting target environment](/files/-Lh_F9wkSHAae-ZuBKyV)

Finally we can select which suites we are going to run

After pressing **Run** button Puppetry opens panel **Test report** with test results. When test ran successfully we get a page like that:

![Successful test run ](/files/-Lh_Huv9P4Ovol73bklZ)

If we click on Open directory with generated screenshots link we can see generated folder named after the test case where we can find the screenshot:

![Generated screenshot](/files/-LhLfspmHAqA5yqYGgzv)

However if test failed the page look as follows:

![Errored test run](/files/-Lh_HxTy-iF-xQh72dOr)

If the error message doesn't clarify the failure enough, you can click on **Error details** link:

![Test run error details](/files/-Lh_HzwhzekG3ElMNu6M)


---

# 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://docs.puppetry.app/master/running-tests.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.
