UI action
Usage
It is best to add this kind of test step through the Test Builder, by mapping the element and selecting an Interaction Type such as Click or Set. 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.
Sample test case
The screenshot below shows a test case with various UI Action Test Steps:
In the test step highlighted above, a value is being set of Provar Pic in the Account Name field. The parent UI On Screen test step shows us that this is happening on the Account ‘New’ screen.
Above the current Test Step, several other UI Action Test Steps can be seen setting values in other fields: ‘Active’, SLA, SLA Serial Number and SLA Expiration Date. Immediately after the current Test Step, another UI Action clicks Save on the record.
Parameters
Since UI Action test steps are generally created and populated through the Test Builder, the user does 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.
The full UI Action parameters are as follows:
- Control Type: The screen and element type. This will be Salesforce Button or Field when on standard Salesforce screens, or Page Object Operation or Page Object Button or Field when on Visualforce or non-Salesforce pages
- Screen Section: The section of the page layout where the Control is located
- Control/Field: The field, button or other test element on which the action is being performed
- Action: The action to be performed, e.g. Set, Click, Activate Inline Edit, Check. There is a special Today Link available for date fields which inputs today’s date
- Value: The value to be added to a field (if a Set action is being used). The Value could be a static value, e.g. Provar Plc, a variable, a function or a combination of all three
- Tab off field: Indicates whether Provar should press tab after this Test Step is completed
- Press Enter: Indicates whether Provar should press Enter after this Test Step is completed
Click Actions
As of Version 1.8.10.26, Provar now supports IE Click Method options to perform Click interaction on any field in the Internet Explorer browser. The following interactions are supported:
- Click via Selenium
- Click via JavaScript
- Send Enter Key via Selenium
- Send Space Key via Selenium
- Send Click Event via JavaScript
Note that the Default option is for existing test steps.
The setting will be ignored if not running on IE browser:
Test Runner logs will confirm the click method under IE:
Example 1: Creating and submitting an account for approval
This example creates a new Salesforce Account using UI On Screen and UI Action test steps performing various actions and submits the Account for approval.
Step 1: Launch the Test Builder and navigate to the Accounts tab. list view.
Step 2: Right-click on the New button and select Add to Test Case:
Step 3: Configure the draft test step as follows:
Note that Interaction Type is set to Click.
Step 5: Navigate to Provar Desktop and review the test case:
Note that an On Screen test step has been added above the UI Action test step. This hierarchy has been generated automatically through the Test Builder.
Step 6: Navigate back to the Test Builder. Right-click on the ‘Account Name’ button and select Add to Test Case:
Step 7: Configure the draft test step as follows:
Note that Interaction Type is set to Click and Value is Account4.
Step 8: Click Add & Do to save the Test Step, then repeat Steps 6-8 to map additional fields. Make sure that all required fields are populated.
Step 9: Right-click on the Save button and select Add to Test Case, then click Add & Do.
Step 10: Review the newly created Account and verify that the information has been populated as specified:
Step 11: Right-click on the ‘Submit for Approval’ button and select Add to Test Case. In the draft test step, set the Interaction Type to Click and Confirm, then click Add & Do:
Step 12: Navigate to Provar Desktop to view the test case details:
- 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