Skip to main content

Environment Automation

note

Check out the the recipes section for a step by step tutorial using the Tracetest CLI here.

note

Check out the the recipes section for a step by step tutorial using a Bash Script here.

Resource Definition​

The Tracetest Web UI provides several options for maintaining Resource Definitions for Tracetest constructs.

Tracing Backend​

When you are in your tracing environment for your org, in Settings, under the Tracing Backend tab, you will find the link to the Resource Definition modal:

Resource Definition

Clicking on the Resource Definition link will open the modal:

Resource Definition Modal

The YAML definition is in the left panel, where you can rename, download or copy the YAML file.

On the right are the automate commands for applying this resource in the CLI.

Trace Polling​

Similarly, on the Trace Polling tab, you will find the Resource Definition link for each polling profile in the trace:

Trace Polling Resource Definition

Selecting the Definition link will open the Resource Definition modal:

Trace Polling Resource Definition Modal

Demo​

On the Demo tab, you will find link to work with resource definitions, as well:

Demo Resource Definition

Analyzer​

On the Analyzer tab, click on Resource Definition:

Analyzer Resource Definition

The analyzer modal shows one single action.

Analyzer Resource Definition Modal

Test Runner​

On the Test Runner tab, click on Resource Definition:

Test Runner Resource Definition

Test Runner Resource Definition Modal

Variable Sets​

In the navigation panel on the left of the screen, click on Variable Sets.

This will open the modal for the Variable Set's resource definition:

Resource Definition Modal

Provisioning Environments​

Tracetest allows the creation of an environment from the CLI and provisioning it with any type of resource.

The resources that can be provisioned in an environment are:

  • analyzer
  • config
  • datastore
  • demo
  • environment
  • environmenttoken
  • invite
  • pollingprofile
  • test
  • testrunner
  • testsuite
  • variableset

Use this feature to quickly spin up new environments for integration testing or CI builds.

note

You can find code examples here. These files are in a folder called “/resources”.

environment.yaml
type: Environment
spec:
  name: my-demo-env
  description: My env desc
  resources: ./resources # this is a folder

The apply command for creating this environment:

Terminal
tracetest apply environment -f ./path/to/environment.yaml

You will now see the created environment and all resources from the resources folder in the Tracetest Web UI.

Environments

Environment Tests

CI Environments​

Environments can be created in an automation/CI pipeline without user interaction.

These environments can be generated for PRs or feature branches, when merging code, when deploying code to QA, staging, or beyond.

Role Access​

An automated environment can only be accessed by an admin or owner role. As a member role you will see a Send Request button when accessing the environment link.

request access

The admin and owner can grant access via an email they recieve after the request is clicked.

grant access email