...
Environments are collections of variables that can be referenced within fields of your responder or action suite, as well as your test configurationsyour test configuration.You can use environment variables to specify endpoints, database table names, connection properties, such as login credentials, etc. The names of variables will be substituted with the assigned values in the active environment. By switching which environment is the "active" environment, you can dynamically switch the environment-specific values at runtime.Environments can also be used to switch virtual asset modes. For example, assume you configured a responder to forward traffic to an external endpoint. By using an environment variable for the endpoint (instead of a fixed value), you can easily redirect message forwarding to different endpoints. This allows .pva files to act like proxies; one environment can point to a real asset while another points to a virtual asset.
Environments are automatically defined when you generate a Parasoft asset from a definition, such as WSDL, but you can also manually define environments as described below.
...
Creating and switching environments is done through the Environments branch of the
test suite's suite’s Test Case Explorer or Responder suite's Virtual Asset Explorer node.
The Environments branch is created by default when a new test suite or Responder suite is created.
...
To add a new environment:
...