Skip to content
Testsigma DOCS
Login Book a demo

Troubleshooting

Troubleshooting Common Issues in Salesforce Testing

While testing applications built on Salesforce, you might face challenges that do not occur in traditional web applications. This is because security controls, session policies, and authentication rules are tightly enforced on the platform. As a result, executions may fail unexpectedly unless configurations are aligned correctly. This document discusses the most common issues faced while executing tests on Salesforce applications and provides actionable steps to resolve them quickly.

Authorization Failure

Section titled “Authorization Failure”

Symptoms:

Section titled “Symptoms:”

Auth Failure

Possible Causes:

Section titled “Possible Causes:”
  • ClientId and Secret are incorrect.
  • Environment might be wrong (e.g., production vs. development).
  • Callback URL is incorrect.

Steps to Resolve

Section titled “Steps to Resolve”

1. Verify ClientId and Secret:

  • Double check the ClientId and Secret provided by the service and ensure there are no typos.

  • Regenerate the ClientId and Secret if necessary.

2. Check Environment Settings:

  • Ensure the correct Environment is selected (development, staging, production).

  • Confirm your application’s configuration.

3. Check Callback URL:

  • Ensure the Callback URL matches the service provider’s settings and check if there are typos.

  • Ensure your server is configured to handle the callback request.

4. Additional Notes:

  • Ensure the application’s permissions and scopes are set correctly while creating a connected app.

  • Check network & firewall settings for blocks on the authorization endpoint.

For more information, refer to the documentation on creating a connected application.

Login NLP is Not Working

Section titled “Login NLP is Not Working”

Symptoms:

Section titled “Symptoms:”

Users can sync metadata but the login step fails.

Possible Causes:

Section titled “Possible Causes:”
  • Salesforce Access Token and Refresh Token might have expired.
  • The same connected app is being used by multiple users simultaneously.
  • Users might have changed the connected app configuration in the Salesforce org.

Steps to Resolve

Section titled “Steps to Resolve”

1. Re-authenticate Salesforce Connection:

  • Try to authenticate the Salesforce connection again and obtain a new Access Token and Refresh Token.

2. Verify Connected App Settings:

  • Check the connected app configuration in Salesforce and ensure all settings are correct.

3. Best Practices:

  • Use different connections for different testing environments to avoid conflicts.

MFA Challenge

Section titled “MFA Challenge”

Symptoms:

Section titled “Symptoms:”

Users can sync metadata but encounter an MFA challenge during the process.

Possible Causes:

Section titled “Possible Causes:”
  • Salesforce org configuration needs verification.

Steps to Resolve

Section titled “Steps to Resolve”

1. Disable Org Level MFA Configurations:

  • Disable the Require multi-factor authentication (MFA) for all direct UI logins to your Salesforce org setting. Disable MFA Config

2. Disable User Level MFA Configurations:

  • Ensure that user-level MFA settings follow the required configuration. If not, adjust them accordingly by navigating to Account > Settings > Advanced User Settings > User Details > Profile

    MFA APIs

    API Only User

3. Best Practices:

Waive MFA for Exempt Users:

  • Ask customers to enable Waive Multi-Factor Authentication for Exempt Users in Salesforce. Waive MFA

Create a Permission Set for Automation Users:

  • Create a new permission set specifically for automation users.

  • Assign this permission set to users who are performing Salesforce authentication.

Execution Fails on Labs

Section titled “Execution Fails on Labs”
Salesforce Execution Fails on Labs error banner

Cause:

Section titled “Cause:”

The execution fails when the session is generated from a different machine but the execution is done on a different browser or environment, such as when a lab is selected. This mismatch results in Salesforce treating the session as invalid, leading to execution failure.

Steps to Resolve

Section titled “Steps to Resolve”

1. Verify User Privileges

Ensure the user executing the test has the same privileges as the System Administrator:

  • Navigate to Setup > Quick Finder > Users.

  • Click on the relevant user.

  • In the User Detail section, check the Profile and compare it with the System Admin profile.

User Profile Settings

2. Execute via Local Agent

  • Run the test case on a local agent.

  • If the test executes successfully, the issue is related to Labs session handling.

3. Update Session Settings (if issue is Labs-specific)

Navigate to Setup > Quick Finder > Session Settings and configure as follows:

  • Disable: Lock sessions to the IP address from which they originated

  • Enable: Lock sessions to the domain in which they were first used

  • Enable: Force relogin after Login-As-User

Session Security Levels

MFA Dialog Appears During Execution

Section titled “MFA Dialog Appears During Execution”

Cause:

Section titled “Cause:”

Salesforce enforces Multi-Factor Authentication for users logging in from untrusted devices or sessions. When tests are executed via Labs or agents, the sessions are considered untrusted, triggering the MFA Dialog.

Steps to Resolve

Section titled “Steps to Resolve”

Navigate to Setup > Quick Finder > Session Settings > Session Security Levels.

Update the following options:

  • Remove: Multi-Factor Authentication (MFA) requirement
  • Ensure: Passwordless Login is enabled
  • Ensure: Username & Password login is enabled

Session Settings