Environments

Testing environments help ensure that the software works in a variety of scenarios. How to add them in ATM?

Testing environment provide a controlled and isolated space for software testing, allowing to simulate real-world scenarios and perform a variety of tests. It helps with identifying and fixing bugs - all of these efforts result in quality and an improvement in user experience.

Usually, there are at least 3 environments: testing, staging and production. Each one of them requires software testing - the same test cases may be tested in 3 different environments.

In ATM, admins can add and configure testing environments in the app. To do so, the users have to access the Testing Hub, and go into Environments tab.

Currently, Environments are shared by every Testing Setup created in ATM.

1. To add the environment, click Create a new one button.

1. In the new window, add a name, description and URL (this is optional). Click Add button.

1. The new environment will be added to the list in the tab.

   1. Its details can be edited directly on the list.

   2. Status column informs whether the environment is enabled. By default, it will be set as active, but it can be disabled by clicking the More options menu (three dots).

      1. Disabled environment equals the disability of options in custom fields - the value will remain in the work items, however it will not be available for selection in picker-fields.

ATM Environment

Configured Environments will be viewed in the multi-select ATM Environment custom field. The values of ATM Environment can be set on Test Executions work type and will be copied as a read-only field in Test Case Execution custom object, in a selected Test Execution.

This custom field can be used in a JQL search, to filter through testing items and e.g. only get items assigned a 'Production' environment.

Test Environment = production

Tips: This custom field can be added to Card layout on the project board. This way, the users have information about the environments for test executions. The custom field can be used in Quick filters on the project board. The users can divide your work items according to the testing environments and get a clearer picture of the workload.