Looking for something in particular?

Visualforce Testing

Visualforce testing is a little different from standard Salesforce layout testing. While standard Salesforce screens such as page layouts, have a rigidly defined format and behavior, Visualforce is more customizable. As such, Provar needs the tester to be more involved in defining the Visualforce page under test.

This page describes some new concepts relating to Visualforce pages, such as Visualforce field locators and Page Objects. These concepts can also be extended to testing other pages, such as external website pages.

Page objects

When you first start testing a Visualforce page, Provar will create a Page Object to store all relevant information for that Visualforce page, including fields. Each time you test a new field on the same Visualforce page, it will add this field to the Page Object.

Page Objects are a popular design pattern in test automation. You may already be familiar with them if you have used a Selenium framework for test automation.

The Page Object is a centralized container for all information related to a specific Visualforce page. If changes happen to the page in the future and this information needs to be updated, you will only need to update a single Page Object instead of every Test Step related to this page. This helps to reduce test maintenance.

Note: Page Objects are also used when testing non-Salesforce pages, such as a standard webpage.

When you map a Visualforce field using the Test Builder, a new Page Object will be created automatically where needed. This can be seen under the Page Structure section:

If the Test Builder ever suggests a New Page when you know a Page Object already exists, you can click on the New Page dropdown to select an existing Page Object instead.

Mapping Visualforce fields

When mapping Visualforce fields, it is best to use a Visualforce locator. This is a specific locator generated by Provar, which is anchored to the APEX page definition. We recommend using this option where available.

To map a Visualforce field, right-click on your target field and select ‘Add to Test Case.’

When the draft Test Step appears:

Provide a name for the Page Object (or accept the default).

Provide a Field Name (or accept the default).

Set the Field Locator type to Visualforce if it has not been defaulted

Specify the Interaction Type and Value

Then click Add or Add & Do to save the Test Step.

Mapping existing fields

Once you have mapped a Visualforce field, Provar will record this in the relevant Page Object for future reference.

To map the same field in another Test Step, follow the same process as above of right-clicking on the target field and selecting Add to Test Case.

When the draft Test Step appears, note that Provar already recognizes that this field exists in your Page Object. (If this has not occurred, and your Page Object shows as New Page, click on this dropdown and select the Existing Page option.)

Once you have done this, complete the other Test Step details as usual and click Add or Add & Do to save the test step.

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