Environments
Last updated
Last updated
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.
Go to Environments and click Add New Environment.
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.
Add your Variables.
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 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.
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.
Go to Environments and click on the environment you want the log for.
Click the View Audit Log button at the top of the edit screen
Go to Environments and click on Pipeline Stages tab
Open the three dot menu to the right of the Stage and click View Audit Log
