Looking for something in particular?

UI On Screen

This test step is used to navigate to a specific screen for UI testing. Test steps of this kind should have additional sub-steps underneath to perform actions on the page, such as a UI Action or UI Assert.


UI On Screen is generally a parent step for operations such as UI Action and UI Assert. (When testing a table, UI With Row will also be added underneath UI On Screen to locate the element within the table.)

Many page types can be handled using UI On Screen, including standard Salesforce, Visualforce, and non-Salesforce pages.

This step is generally added automatically when using the Test Builder. This is recommended as the fastest way to add this kind of test step, although it is also possible to use drag-and-drop from the Test Palette.


Since UI On Screen test steps are generally created from the Test Builder, you do not need to know how to populate these fields from scratch. However, describing all the available parameters for editing and debugging purposes is valid.

In the example above, the screen being located is the New screen of the Contact object.

The full parameters are defined as follows.

Screen parameters

  • Connection Name: The Connection is currently in use.
  • Screen Type: The type of page. This will be a Salesforce Page for any standard Salesforce pages, such as an Account view screen or Page Object (Selenium) for Visualforce or non-Salesforce pages).
  • Object / Action: The Salesforce Object and the operation that the page performs in Salesforce (e.g., New, Edit, Clone).
  • Record Type: The record type of the Object where relevant. (In Salesforce, different page layouts can be assigned based on Record Type).

Note that these options will vary if the screen is not a standard Salesforce page-specific URL the test should navigate to if Navigate is specified as Always Navigate.

Option Parameters

Navigate indicates whether Automation should navigate directly to this page. This is generally defaulted to Don’t Navigate so the test is guided by its preceding Test Steps. An exception is at the beginning of a test when the first On Screen test step defaults to Always Navigate.

It is also possible to set Navigate to Only if the address doesn’t match or Only if the address doesn’t match (excluding query params). These options indicate that Automation should navigate directly to the page only if the URL does not match the information provided in the Screen Parameters of the test step. The additional option (excluding query params) will ignore any query parameters in the URL when evaluating whether the address matches.

Other Option Parameters

  • Window: Use this to change the window in focus. Defaults to Stay on the currently focused window. Choosing Select main window will move focus to the main parent window and execute the next test step in the parent window. Selecting the most recently opened window will switch back to the most recent window if multiple windows exist.
  • Window Size: Determines the size of the browser window to run the test in. Subsequent test steps will be executed on this browser window size. Defaults to Default. Choosing Maximize will maximize the browser window as soon as the test step is executed.
  • Close Window: Indicates whether Automation should close the window after performing sub-steps.

Navigating directly to an object using the Object ID

You can directly navigate to an object (Account, Case, Lead, Opportunity, etc.) with the help of the UI On Screen test step type. To navigate to a specific object you need a unique Object ID, such as a Salesforce ID.

The example below illustrates how you can navigate directly to the Account View screen using the Account Object ID.

Step 1: Create a test case invoking the Salesforce connection.

Step 2: Drag the UI On Screen test step type from the Test Palette to your test case. 

Step 3: Ensure the navigation option is Always Navigate or Only if the address doesn’t match.

Step 4: Enter the Object ID; an example is shown in the screenshot below.

Note: You can parameterize the Object ID by passing the variable in the Object ID using a data-driven approach.

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