Provar Test Builder
The fastest way of building UI test cases in Provar is with the Test Builder.
The Test Builder, an Electron application, is an interactive tool for authoring and debugging UI test cases. The Test Builder captures fields and values on your Salesforce (and non-Salesforce) webpages and adds them to your test case as test steps. This allows you to build up test cases rapidly, authoring and debugging as you go.
The Test Builder also:
- Creates Page Objects and adds fields to it, if a field needs to be specially mapped (e.g. on a Visualforce page)
- Runs test cases for debugging, supporting breakpoints and forwards and backwards stepping
- Captures variables which are visible during and at the end of the test execution
Adding test steps with the Test Builder
The Test Builder is the fastest way of adding UI Test Steps to a test case.
To add UI test steps using the Test Builder, first launch the Test Builder. This can be done by clicking the Test Builder icon (
Once you have launched Test Builder and it has connected you to Salesforce, right-click on the element you want to perform an action on and select Add to Test Case.
Draft test steps
Once you have added the element to your test case, a draft test step will be created in the Test Builder. This allows you to add or amend information in the test step before it is added to the test case.
Provar will use its knowledge of your Org to default as much information as possible in the draft test step. For a standard Salesforce field on a standard layout, Provar will default the Main Page, Field Name and the Value, if a value exists.
Since this is only a draft test step, you can edit any information prior to saving, for example adding or amending the Value.
To save the test step, select Add or Add & Do. Add will just save the step without execution, whereas Add & Do will save the step and execute it simultaneously. Add & Do is generally recommended when you are building a test case. (If you press ENTER on your keyboard at this stage, it will perform the Add & Do action.)
- Provar Automation
- Installing Provar Automation
- Updating Provar Automation
- Using Provar Automation
- API Testing
- Behavior-Driven Development
- Creating and Importing Projects
- Creating Test Cases
- Custom Table Mapping
- Functions
- Debugging Tests
- Defining a Namespace Prefix on a Connection
- Defining Proxy Settings
- Environment Management
- Exporting Test Cases into a PDF
- Exporting Test Projects
- Override Auto-Retry for Test Step
- Managing Test Steps
- Namespace Org Testing
- NitroX
- Provar Desktop
- Provar Test Builder
- Refresh and Recompile
- Reintroduction of CLI License Check
- Reload Org Cache
- Reporting
- 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
- Using Custom APIs
- Callable Tests
- Data-Driven Testing
- Page Objects
- Block Locator Strategies
- Introduction to XPaths
- Creating an XPath
- JavaScript Locator Support
- Label Locator Strategies
- Maintaining Page Objects
- Mapping Non-Salesforce fields
- Page Object Operations
- ProvarX™
- Refresh and Reselect Field Locators in Test Builder
- Using Java Method Annotations for Custom Objects
- Applications Testing
- Provar Manager
- DevOps
- Introduction to Test Scheduling
- Apache Ant
- Configuration for Sending Emails via the Automation Command Line Interface
- Continuous Integration
- AutoRABIT Salesforce DevOps in Provar Test
- Azure DevOps
- Running a Provar CI Task in Azure DevOps Pipelines
- Configuring the Automation 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
- CircleCI
- Copado
- Docker
- Flosum
- Gearset DevOps CI/CD
- GitHub Actions
- Integrating GitHub Actions CI to Run Automation CI Task
- Remote Trigger in GitHub Actions
- Parameterization using Environment Variables in GitHub Actions
- Parallel Execution in GitHub Actions using Multiple build.xml Files
- Parallel Execution in GitHub Actions using Targets
- Parallel Execution in GitHub Actions using Test Plan
- Parallel Execution in GitHub Actions using Job Matrix
- GitLab Continuous Integration
- Travis CI
- Jenkins
- Execution Environment Security Configuration
- Provar Jenkins Plugin
- Parallel Execution
- Running Provar on Linux
- Reporting
- Salesforce DX
- Git
- Team Foundation Server
- Version Control
- Salesforce Testing
- Best Practices
- Troubleshooting
- Release Notes