Share this page

# Environments

This topic describes Environment entities that allow you to represent properties of the system being tested.

In this topic:

## Testing environments

Environment entities are generic entities that represent a resource, device, or venue. A common use of the Environment entity is to represent a testing environment upon which a defect was detected.

In addition to the Environment entity, you can also use Environment tags to further identify the environment that you are testing, such as a browser or OS version. Environment tags can be added to many entity types. For details, see Environment tags.

The following table describes when to use each type:

Type | When to use it
--- | ---
Environment entity | When you need to indicate the exact environment on which a test was run or a defect was detected. For example, if you want to analyze the root cause of a defect which was only detected in certain environments, you select the environments in the defect's Detected in Environment field. Note: Environments are not unique attributes in the calculation of Last runs. Runs with different environments do not result in separate Last runs.
Environment tags | When you need to analyze coverage based on the tag. For example, if you are analyzing coverage by a specific browser, you should choose the environment tag for that browser. In Grid view, you can filter the display by Environment tags. Note: Environment tags are one of the unique attributes of last runs. As a result, different environment tags generate separate Last runs. For details, see Last runs.

In many cases, it is a good practice to use both indicators. For example, if a defect was detected on environment Lab1 using the Firefox browser, Environment tags may describe the browser, but they will not provide other details such as the client setup. For this information, use the Environment entity and specify Detected in environment: Lab1.

Tip: Admins can define a business rule to auto-populate environment tags of the defect or manual run when a user selects an environment in the Detected in Environment field. For details, see Business rules.

Back to top

## Create environments

You create Environment entitles in the Release Management module. You can create an Environment entity for the current workspace, or for all workspaces in a shared space.

To define an environment:

1. In the Release Management module, select the Environments tab.

2. Perform one of the following:

   - Click + Environment to create an environment in your workspace.

   - Expand the + dropdown and select Shared Environment to create an environment for all workspaces in the shared space.

3. In the Add dialog box, provide a name and description.

4. Select other options to make your environment unique, such as Environment tags, type, and stage type. Click Add.

Tip: Instruct testers to select the environment in which the defect was detected, in the Detected in environments field. For details, see Additional defect details.

Back to top

See also:

- Releases
- Environment tags
- Additional defect details

https://admhelp.microfocus.com ALM Octane 8942
Tips to improve your search results... ALM Octane Help Center ALM Octane Help 23.4-24.3 All View Local Help Center View Online Help Center Version: