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 pages, Visualforce pages 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 it is useful to describe all the available parameters for editing and debugging purposes.
In the example above, the screen being located is the New screen of the Contact object.
The full parameters are defined as follows.
- Connection Name: The Connection currently in use.
- Screen Type: The type of page. This will be 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 which 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 that the test should navigate to, if Navigate is specified as Always Navigate.
Navigate indicates whether Provar should navigate directly to this page. This is generally defaulted to Don’t Navigate, so that the test is guided by its preceding Test Steps. An exception is at the very beginning of a test, when the first On Screen test step will default 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 Provar 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 present in the URL when evaluating whether the address matches or not.
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. Choosing Select the most recently opened window will switch back to the most recent window if there are multiple windows.
- 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 is maximized as soon as the test step is executed.
- Close Window: Indicates whether Provar should close the window after sub-steps have been performed.
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 that the navigation option is set to either 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.
- General information
- Licensing Provar
- Provar trial guide and extensions
- Using Provar
- 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
- Managing test steps
- Namespace org testing
- Provar desktop
- Provar Test Builder
- Refresh and Recompile
- 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
- List compare
- 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
- Salesforce CPQ testing
- ServiceMax testing
- Skuid testing
- Vlocity testing
- Webservices testing
- Introduction to test scheduling
- Apache Ant
- Configuration for sending emails via the Provar Command Line Interface (CLI)
- Continuous integration
- Azure DevOps
- Running a Provar CI task in Azure DevOps
- Configuring the Provar 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
- GitHub Actions
- Running a Provar CI task in GitHub Actions
- 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 CI
- Travis CI
- Execution Environment Security Configuration
- Parallel Execution
- Running Provar on Linux
- Salesforce DX
- Team foundation server
- Version control
- Zephyr Cloud and Server
- Salesforce testing
- Adding a Salesforce connection
- Assert Page Error Messages on Add/Edit Product
- Dynamic Forms
- Internationalization support
- List and table testing
- Salesforce Release Updates
- Salesforce Lightning Testing
- Salesforce Lightning Web Component (LWC) locator support
- Salesforce console testing
- Visualforce Testing
- Testing best practices
- Configurations and permissions
- Error messages
- Licensing, installation and firewalls
- Test Builder and test cases
- Release notes