Mapping credentials by using an environment file
You can map the variables referenced in the test to secrets configured in the security group by using an environment file, so that HCL DevOps Test Hub (Test Hub) can resolve the secret values at run time.
Before you begin
You must have completed the following tasks:
- Ensured that you are assigned a role as a Project Owner or Tester in the project. See Managing access to the server projects.
- Ensured that your project contains test assets.
- Read and understood the information in Edit branch overview and Create or select an Edit branch.
About this task
Procedure
-
Log in to Test Hub.
The Projects page of the initial team space is displayed.
-
Click to open the project that contains the Salesforce
application.
The Overview page of the project is displayed.
-
Click .
The Test Editor page and the test navigator panel are displayed.
-
Click the Action Menu icon
and
select Environment, or right-click the application folder
in the test navigator panel and select .
The Edit branch dialog is displayed.If the Edit branch dialog is not displayed, then go to step 6. -
Select your action to either select an existing Edit branch or create
an Edit branch:
- Perform the following steps to select an existing Edit
branch:
- Select Use an existing edit branch.
- Select an Edit branch from the Select
branch list if Edit branches already
exist for your repository.Note:A warning message is displayed if the Edit branch, you selected is behind the source branch. To update the selected edit branch and maintain synchronization with the source branch, you can select the Update branch option when switching checkbox.
- Click Ok.
- Perform the following steps to create the Edit branch:
- Select Create new edit branch.
- Enter a name for the Edit branch in the Branch Name field.
- Click Save.
- Perform the following steps to select an existing Edit
branch:
-
In the Create Environment dialog, configure the
following environment details:
- Select a target application from the Application drop-down list. For example, Mysecrets.
- Enter a unique name for your environment in the Name field. For example, SFEnv.dte.yaml.
-
Click Done.
The new environment file is created and displayed in Test Editor.
-
Perform the following steps to add specific variables in the
Variables section:
- Click the Save icon to save the environment details.
-
From the Environment list at the top right of the
Test Editor page, select the required environment.
For example, SFLenv .
The selected environment enables Test Hub to resolve the secret references from the configured security group.