# Environments

Testery is an **environment-aware** testing platform. This means Testery supports running the same tests or different subsets of tests against different environments.

This is useful for situations where you want to run different sets of tests against different environments. 

For example, you may want to run your important tests on every commit to your development environment, full regression against your QA environment, and smoke tests against your production environment.

### Add a New Test Environment

1. Go to **Environments** and click **Add New Environment**.
2. Enter the **Name, Key**, **Environment URL, Pipeline Stage and Maximum Parallel Test Runs** for your environment. If you don't have any Pipeline Stages configured, you can leave that blank for now.
3. Add your **Variables**.

### Maximum Parallel Test Runs

This value sets the maximum number of test runs that can use this environment at once. If multiple test runs are kicked off against this environment, they will be queued until the environment is clear for more tests as test runs complete. Enter `0` if you do not want to limit this environment.

### Variables

**Variables** are key value pairs that get passed into the tests as standard environment variables. They can be added or modified when creating the environment or even when starting a test run from the API or CLIE. Be sure to check the **Encrypted** check box for any parameters that should be stored securely.

### Audit Trail

Testery provides a 90 day audit trail of changes to the variables on both Environments and Pipelines.  This will contain the time, user, and changed variables.  Any encrypted variables will not be shown in the audit log.\
  

<figure><img src="https://4041872331-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MK0kYmwONk3GqQ8OhVA%2Fuploads%2Fgit-blob-646532f0e11ba788303aa52722e479d90b63387b%2FScreenshot%202024-05-15%20170100.png?alt=media" alt=""><figcaption><p>Example of the Audit Log for an Environment</p></figcaption></figure>

#### To view the audit log for an Environment

1. Go to **Environments** and click on the environment you want the log for.
2. Click the **View Audit Log** button at the top of the edit screen

<figure><img src="https://4041872331-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MK0kYmwONk3GqQ8OhVA%2Fuploads%2Fgit-blob-f2b64614d4027ff2c15e94e1cc9aa7f9b7f13aaa%2FScreenshot%202024-05-15%20170135.png?alt=media" alt=""><figcaption><p>When editing an environment, you have the option to view the Audit Log using the button shown.</p></figcaption></figure>

#### To view the audit log for an Pipeline Stage

1. Go to **Environments** and click on **Pipeline Stages** tab
2. Open the three dot menu to the right of the Stage and click **View Audit Log**

<figure><img src="https://4041872331-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MK0kYmwONk3GqQ8OhVA%2Fuploads%2Fgit-blob-96cd8f076395966b3c94cac25f4956f8560583da%2FScreenshot%202024-05-15%20170119.png?alt=media" alt=""><figcaption><p>Click the "View Audit Log" button on the Environment to see your Audit Log</p></figcaption></figure>


---

# 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.testery.io/get-to-know-testery/set-up-your-test-environments.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.