Adding a Connection

A Salesforce Connection is what connects Provar to the Salesforce environment in which Test Cases are to be created and run.

A Salesforce Connection generally consists of a Salesforce UsernamePassword and Security Token. This user must also have Modify All Data enabled on its profile to allow Provar to access the environment’s metadata.

Use the following links to navigate to the relevant section:

Note that Connections of other types can also be added. Refer to Adding a Database Connection and Adding a Messaging Connection for more information.

Adding a Salesforce Connection

To add a new Salesforce Connection:

Step 1: Navigate to the Connections Tab of Test Settings and click the ‘+’ icon:

Step 2: Provide a Connection Name. This should generally be the role name of the user you are connecting through, e.g. ‘AdminUser’:

Step 3: Set Connection Type to ‘Salesforce’, then choose ‘Normal Salesforce Connection’:

Step 4: Enter the Username, Password and Security Token, and specify the Environment type. This will control the Salesforce screen used to log in.

Note that you can also tick Enable Lightning Mode if you want to test in Lightning by default. Refer to Lightning Testing for more information.

Step 5: If your network uses a Proxy server, specify this information in the Proxy Settings section:

Step 6: If you use a custom or Mydomain URL to log into into Salesforce, specify this in Browser Login URL / Web base URL of the Advanced Settings section:

Step 7: If your organization uses Single Sign-On, specify this in Sign-on Connection / Identify Service URL.

Step 8: Tick Enable S-Controls or Enable Reports if you will be testing these features. This will instruct Provar to download the relevant metadata. (Note: ServiceMax organizations will always need to tick Enable S-Controls.)

Step 9: Click the ‘Test Connection’ button to validate the Connection details, then click the ‘OK’ button.

Adding a ‘Log-on As’ Connection

After the first Salesforce Connection has been added via an admin user with the Modify All Data permission, more Connections can be added to represent standard user roles, e.g. SalesUser or ServiceUser. This is useful for testing from the perspective of a specific user group with their particular permissions.

If additional Connections are added using a Log-on As Connection, passwords and security tokens for these users are not required. Using a Log-on As Connection is recommended for this reason.

To add a Log-on As Connection, repeat the steps Salesforce Connection steps above (refer to Adding a Salesforce Connection). The only exception is in Step 4:

In Basic Settings, click the toggle Use ‘Log-on As’ via an Admin Connection. In Log-on As Connection, specify the admin Connection previously added, then in Username enter the username of the new user:

Then repeat the other steps as defined above.

Adding a Communities Connection

To add a Connection to test as a Community user, start by creating a new Connection and adding a Connection Name. Refer to Steps 1 and 2 of Adding a Salesforce Connection above.

Then complete the following steps:

Step 3: Set Connection Type to ‘Salesforce’, then choose ‘Salesforce Communities Connection’.

Step 4: Specify whether the user is also an internal Salesforce user, or whether they are purely a Communities user.

If the user is an internal Salesforce user:

Use Log-on As to make the Connection:

Then specify the Community Name / ID. This can be found in the Site Name field of the Communities detail page within Salesforce, accessed via Setup > Build > Develop > Sites:

Finally, specify the the admin Connection to be used in Log-on As Connection, and the Salesforce username of the new Community user in Username:

If the user is not an internal Salesforce user:

Use Normal Log-in to make the Connection. Then enter a Username, Password and specify the Environment type. This will control the Salesforce screen used to log in.

If you are using a custom Community Login URL, specify it under Advanced Settings:

The Metadata Connection and Partner Connection should also be set to an admin Connection that has been previously added.

Step 5: Click the ‘Test Connection’ button to validate the Connection details, then click the ‘OK’ button.

Salesforce Portal Connection

To add a Connection to test as a Portal user, start by creating a new Connection and adding a Connection Name. Refer to Steps 1 and 2 of Adding a Salesforce Connection above.

Then complete the following steps:

Step 3: Set Connection Type to ‘Salesforce’, then choose ‘Salesforce Portals Connection’.

Step 4: Specify whether the user is also an internal Salesforce user, or whether they are purely a Portal user.

If the user is an internal Salesforce user:

Use Log-on As to make the Connection:

Then specify the Portal Name / ID. This can be found in the Portal ID field of the Portal detail page within Salesforce, accessed via Setup > Customize > Customer Portal > Customer Portal Settings:

Finally, specify the the admin Connection to be used in Log-on As Connection, and the Salesforce username of the new Portal user in Username:

If the user is not an internal Salesforce user:

Use Normal Log-in to make the Connection. Specify the Portal Name / ID (see above), then, as normal, enter the UsernamePassword and Environment type. This will control the Salesforce screen used to log in.

In Advanced Settings, the Metadata Connection and Partner Connection should also be set to an admin Connection that has been previously added.

Step 5: Click the ‘Test Connection’ button to validate the Connection details, then click the ‘OK’ button.

2017-05-12T11:34:44+00:00

Leave A Comment