Configuration on other CI tools

This document provides you with steps intended to reduce exposure of the credentials used in Test Case execution with other CI tools. If you are using Jenkins, please click here.

Step 1: Refer to Variable Set Syntax to retrieve the correct information based on your Connection type.

Step 2: In your CI tool, navigate to the “Secrets & Variables” section and create Secrets based on connection type.

Step 3: Modify the YML File to call the secrets as Environment Variables.

Known Issues

However, SF OAuth WebFlow connection only worked when Access Token and Refresh Token is kept in the .secrets file and supplying the Consumer Key and Client Secret as per suggested variables (case-sensitive).

• PROVAR_SF_ADMIN_CLIENTSECRET
• PROVAR_SF_ADMIN_CONSUMERKEY

Connection types currently not supported:

• UI Testing
• Database