Documentation

Looking for something in particular?

Refresh and Reselect Field Locators in Test Builder

We’ve made it easier to manage field locators directly within Test Builder. 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. 

Repairing locators


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. 

Review Provar on G2
Documentation library

Trying to raise a case with our support team?

We use cookies to better understand how our website is used so we can tailor content for you. For more information about the different cookies we use please take a look at our Privacy Policy.

Scroll to Top