# 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**).
You get **Run Tests** modal window
Learn more about **"interactive mode"** option in [Interactive mode](https://docs.puppetry.app/v/3.0.0/running-tests/interactive-mode)
Learn more about **"update comparison images"** option in [CSS Regression Testing](https://docs.puppetry.app/v/3.0.0/testing-techniques/css-regression-testing)
### Selecting Staging Environment
The modal window allows you to select a [target environment](https://docs.puppetry.app/template):
###
### Browser Options
We can use **Browser options** tab to adjust the runner
On this panel we can select a browser to run the tests:
Available options are:
[**Headless Chromium**](https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md) allows running [Chromium](https://en.wikipedia.org/wiki/Chromium_\(web_browser\)) in a headless/server environment. In this mode the test will run considerably faster.
[**Chromium**](https://en.wikipedia.org/wiki/Chromium_\(web_browser\)) is an open-source web browser, which is used as basis for Google Chrome browser. Puppetry downloads and uses a specific version of Chromium so its API is guaranteed to work out of the box.
[Google Chrome](https://www.google.com/chrome/) is a cross-platform web browser developed by Google.
[**Mozilla Firefox**](https://www.mozilla.org/en-US/firefox/) is a free and open-source web browser developed by the Mozilla Foundation.
**Connect to Chrome** - connecting to a running instance of Chrome
Browser-specific options:
* **DevTools** - enables Chrome DevTools in the browser
* **incognito window** - runs the tests in [private session](https://support.google.com/chrome/answer/7440301)
* **maximized** - maximizes the browser window
* **fullscreen** - switches the browser in fullscreen mode
* **ignore HTTPs errors** - tolerates HTTPs errors like invalid certificate
Besides you can manually provide any [Chromium command line options](https://peter.sh/experiments/chromium-command-line-switches/) in the textbox below.
You can also specify location of Chrome extension. Learn more [here](https://docs.puppetry.app/v/3.0.0/testing-techniques/testing-chrome-extensions)
### Connecting to Chrome
There are some cases when we need to connect to a ruining instance of chrome instead of starting a new one. For example to bypass reCaptcha we can solve it manually in Chrome and then run the tests on it.
In order to connect we need to start Chrome in command-line with remote-debugging-port parameter.
{% tabs %}
{% tab title="Windows" %}
```
start chrome.exe –remote-debugging-port=9222 --user-data-dir=remote-profile
```
{% endtab %}
{% tab title="macOS" %}
```
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222 --no-first-run --no-default-browser-check --user-data-dir=$(mktemp -d -t 'chrome-remote_data_dir')
```
{% endtab %}
{% tab title="Linix" %}
```bash
google-chrome --remote-debugging-port=9222
```
{% endtab %}
{% endtabs %}
Next we navigate in the started browser to `http://127.0.0.1:9222/json/version`. On the page we can see a JSON object.
We shell copy the value of `webSocketDebuggerUrl` property. Open **Run Tests** modal window (F6), switch to **Browser options** tab and paste the saved value into **WS Endpoint** input.
Now we can press **Run**.
### Running tests
As we press Run button the tests are sent to Jest and we have to wait for [Test Report](https://docs.puppetry.app/v/3.0.0/test-reports)
