Adding a Salesforce 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 Username, Password and Security Token. This user must also have certain permissions to allow Provar to connect to your org and automatically understand your Salesforce configuration. Refer to Granting Org Permissions to Provar for more information.
Connections of other types can also be added. Refer to Database Testing Setup for more information.
Adding a Salesforce connection
Step 1: Navigate to the Connections tab of test settings and click the plus sign 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: Steps 5-8 are only needed for advanced connection setup.
Step 5: If your network uses a Proxy server, specify this information in the Proxy Settings section.
Provar will attempt to detect proxy settings automatically and globally instead of from a connection. If you are on version 220.127.116.11 or prior, refer to Defining Proxy Settings for more information on how to update your proxy settings.
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. 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.
- General information
- Licensing Provar
- Provar trial guide and extensions
- Using Provar
- API testing
- Behavior-driven development
- Creating and importing projects
- Creating test cases
- Custom table mapping
- Debugging tests
- Defining a namespace prefix on a connection
- Defining proxy settings
- Environment management
- Exporting test cases into a PDF
- Exporting test projects
- Managing test steps
- Namespace org testing
- Provar desktop
- Provar Test Builder
- Refresh and Recompile
- Reload Org Cache
- Running tests
- Searching Provar with find usages
- Secrets management and encryption
- Setup and teardown test cases
- Tags and Service Level Agreements (SLAs)
- Test cycles
- Test plans
- Testing browser options
- Tooltip testing
- Using the Test Palette
- Test Palette introduction
- Control test steps
- List compare
- Read test step
- String test steps
- UI Test Steps
- Using custom APIs
- Callable tests
- Data-driven testing
- Page objects
- Applications testing
- Database testing
- Document testing
- Email testing
- Mobile testing
- OrchestraCMS Testing
- Salesforce CPQ testing
- ServiceMax testing
- Skuid testing
- Vlocity testing
- Webservices testing
- Introduction to test scheduling
- Apache Ant
- Configuration for sending emails via the Provar Command Line Interface (CLI)
- Continuous integration
- Azure DevOps
- Running a Provar CI task in Azure DevOps
- Configuring the Provar secrets password in Microsoft Azure Pipelines
- Parallel execution in Microsoft Azure Pipelines using multiple build.xml files
- Parallel execution in Microsoft Azure Pipelines using targets
- Parallel execution in Microsoft Azure Pipelines using Test Plans
- Bitbucket Pipelines
- Circle CI
- GitLab CI
- Travis CI
- Parallel Execution
- Running Provar on Linux
- Salesforce DX
- Team foundation server
- Version control
- Zephyr Cloud and Server (Beta)
- Salesforce testing
- Adding a Salesforce connection
- Assert Page Error Messages on Add/Edit Product
- Internationalization support
- List and table testing
- Salesforce Release Updates
- Salesforce Lightning Testing
- Salesforce Lightning Web Component (LWC) locator support
- Service Cloud console testing
- Visualforce Testing
- Testing best practices
- Configurations and permissions
- Error messages
- Licensing, installation and firewalls
- Test Builder and test cases
- Release notes