UI with row
This test step is used to locate rows within a table. Once the table is located through a With Row, other sub-steps can be added underneath to perform operations on the table fields (e.g. a UI Action or a UI Assert).
Usage
UI With Row always occurs as a sub-step under a UI On Screen step. Both steps are 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.
With Row Parameters
The screenshot below shows With Row parameters in use:
In this example, the table being located is an Account list view, and the row being located is the 6th row in the table.
The full parameter definitions are as follows:
- Connection Name: The Connection currently in use.
- Table Type: The type of table (Salesforce Table or Page Object Row). This will be Salesforce Table for any standard page, such as a list view, or Page Object Row for a Visualforce or non-Salesforce page
- Table: The name of the table. The dropdown will be autopopulated with a list of available tables on the current page (based on the On Screen parent step).
- Row Locator: The specific row of the table that is to be tested. This could be a Row Number (as in screenshot above) or a WHERE clause where the record is located based on defined criteria (e.g. AccountName = Provar Pic).
Example 1: Deleting from a list view with Row Number
In this example we will use UI With Row to locate a specific row in the ‘All Accounts’ list view. We will then use a UI Action step to delete the Account.
Step 1: Launch the Test Builder and navigate to the All Accounts list view.
Step 2: Right-click on the Del inline link of the 6th row (e.g. A01ProvarTest) and select Add To Test Case:
Step 3: Configure the draft test step as follows:
Note that Row Locator is Row Number = 6 and Interaction Type is set to Click.
Step 4: Click Add & Do to save the test step.
Step 5: Navigate to Provar Desktop to view the test step:
Note that the On Screen has been added as the parent of With Row, and With Row as the parent of the UI Action. This hierarchy has been generated automatically through the Test Builder.
Step 6: On the UI Action Test Step, set the Action to Click and Confirm. Then save the test case.
Example 2: Asserting in a related list with Row Filter
In this example we will use UI With Row to locate an activity with a specific subject in an Activity History related list. We will then use a UI Assert to check the ‘Assigned To’ field of that activity.
Step 1: Launch the Test Builder and navigate to view page of a specific Account (e.g. Dickenson plc), then scroll down to the Activity History related list:
Step 2: Right-click on the Assigned To value of any row (e.g. vikas wig) then select Add to Test Case:
Step 3: Configure the draft test step as follows:
Note that Row Locator is Subject = ‘Test Call, Interaction Type is Read/Assert and Expected Value is vikas wig.
Step 4: Click Add & Do to save the test step.
Step 5: Navigate to Provar Desktop to view the test step:
Note that the On Screen has been added as the parent of With Row, and With Row as the parent of the UI Action. This hierarchy has been generated automatically through the Test Builder.
Note also that Row Locator has been autopopulated with the filter condition of Subject = Test Call.
Step 6: Save the test case.
- 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
- Functions
- 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
- Reload Org Cache
- Reporting
- 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
- Using custom APIs
- Callable tests
- Data-driven testing
- Page objects
- Block locator strategies
- Introduction to XPaths
- Creating an XPath
- JavaScript locator support
- Label locator strategies
- Maintaining page objects
- Mapping non-Salesforce fields
- Page object operations
- ProvarX™
- Refresh and reselect field locators in Test Builder
- Using Java method annotations for custom objects
- Applications testing
- DevOps
- Introduction to test scheduling
- Apache Ant
- Configuration for Sending Emails via the Provar Command Line Interface
- Continuous integration
- AutoRABIT Salesforce DevOps in Provar Test
- Azure DevOps
- Running a Provar CI Task in Azure DevOps Pipelines
- 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
- CircleCI
- Copado
- Docker
- Flosum
- Gearset DevOps CI/CD
- GitHub Actions
- Integrating GitHub Actions CI to Run Provar 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
- Jenkins
- Execution Environment Security Configuration
- Provar Jenkins Plugin
- Parallel Execution
- Running Provar on Linux
- Reporting
- Salesforce DX
- Git
- Team foundation server
- Version control
- 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
- Performance Best Practices
- Testing best practices
- Troubleshooting
- Browsers
- Configurations and permissions
- Connections
- DevOps
- Error messages
- Administrator has blocked access to client
- JavascriptException: Javascript error
- macOS Big Sur Upgrade
- Resolving failed to create ChromeDriver error
- Resolving Jenkins license missing error
- Resolving metadata timeout errors
- Test execution fails – Firefox not installed
- Update to Opportunity field validation behaviour
- Licensing, installation and firewalls
- Memory
- Test Builder and test cases
- Release notes