Refresh and reselect field locators in Test Builder
We’ve made it easier to manage field locators directly within Test Builder. Using Provar version 2.2.1 (and subsequent versions) you can refresh locators to repair a broken locator in just a few clicks. You can also change them to a different type of locator based on your preference.
Notes: This feature is designed to help you test custom Salesforce components and non-Salesforce applications. Since Provar is designed to natively adapt to Salesforce and is metadata-driven, you do not need to use this feature for standard Salesforce components/functionality.
Who does this impact?
Provar users who would like to change and/or fix a broken locator directly within the Test Builder.
Why is this important?
This feature is designed to address these challenges:
- Sometimes, a field locator may stop working when existing tests are run against a new application release due to technical changes. This is often due to changes in how the web page source is structured.
- You can also use this feature to change the locator type if you feel Provar has not selected your preferred one by default.
If I use the same field more than once in a test, do I need to manually repair the field locator for every test step that interacts with that field?
No. if you repair a broken field locator in one test step, this will repair all of the test steps that use the same mapping locator. The same field mapping information for a page object is stored and shared across those steps.
How can I use this feature?
We now offer a simple click-to-fix solution. You can access this feature while adding a new test step or editing an existing test step to repair a broken locator or to change a locator on demand.
If you find a test step failing due to a broken locator, Provar can help suggest a new locator to fix the test step.
Step 1: Navigate to the Test Builder and right-click the test step you want to edit.
Step 2: Select Edit the Test Step from the drop-down menu.
Step 3: Click the Edit button next to Field Details. The Field Locator field will now appear.
Step 4: In the application you are testing, right-click the target element for the current test step you are editing and select Refresh Field Locators from the drop-down menu. Provar will recalculate the new, recommended locator and an alternate set of locators. You can view the full list of updated locators in the Field Locator drop-down menu by clicking the caret icon.
Step 5: Select your preferred option from the drop-down menu. You can optionally edit the field parameters.
Step 6: Click Save & Do to save your changes.
Changing locators on demand
You can change field locators while adding a new test step or editing an existing one.
Step 1: Right-click the field and select Add to Test Case. (You can skip this step if editing an existing test step. If you are editing an existing test step, navigate to the Test Builder and right-click the test step you want to edit. Select Edit the Test Step from the drop-down menu.
Step 2: Click the Edit button next to Field Details. The Field Locator field will now appear.
Step 3: Click the caret icon above the Field Locator field to view the available field locator options. You can populate additional options if you only see one locator in the drop-down menu. In the application you are testing, right-click the target element for the current test step you are editing and select Refresh Field Locators from the drop-down menu. Provar will recalculate the new, recommended locator and an alternate set of locators. You can view the full list of updated locators in the Field Locator drop-down menu by clicking the caret icon.
Step 4: Select your preferred option from the drop-down menu. You can optionally edit the field parameters.
Step 5: Click Save & Do to save your changes.
- 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
- 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
- Provar desktop
- Provar Test Builder
- Refresh and Recompile
- Reintroduction of CLI license Check
- 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
- Generate Test Case
- List compare
- Page Object Cleaner
- Read test step
- String test steps
- UI Test Steps
- Using custom APIs
- Callable tests
- Data-driven testing
- Page objects
- Block locator strategies
- Introduction to XPaths
- Creating an XPath
- Label locator strategies
- Maintaining page objects
- Mapping non-Salesforce fields
- Page object operations
- Refresh and reselect field locators in Test Builder
- Using Java method annotations for custom objects
- Applications testing
- Database testing
- Document testing
- Email testing
- Mobile testing
- OrchestraCMS Testing
- Guide in Salesforce CPQ Testing in Provar
- Guide in ServiceMax Testing
- Skuid Testing
- Vlocity API Testing
- Webservices testing
- 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
- 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
- Execution Environment Security Configuration
- Provar Jenkins Plugin
- Parallel Execution
- Running Provar on Linux
- Salesforce DX
- Team Foundation Server
- Version control
- Provar Automation trial guide and extensions
- 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
- Salesforce console testing
- Visualforce Testing
- Provar Manager
- Best Practices
- Configurations and permissions
- Error messages
- Licensing, installation and firewalls
- Test Builder and test cases
- Release Notes