UI action
Usage
It is best to add this 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.
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, describing all the available parameters for editing and debugging is helpful.
The full UI Action parameters are as follows:
- Control Type: The screen and element type. This will be the 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. A special Today Link is available for date fields, which inputs today’s date.
- Value: The value to be added to a field (if a Set action is used). The Value could be static, e.g., Provar Plc, a variable, a function, or a combination of all three.
- Tab off the field: Indicates whether Provar should press the tab after this Test Step is completed
- Press Enter: Indicates whether Provar should press Enter after this Test Step is completed
Click Actions
Automation 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.
- Provar Automation
- Installing Provar Automation
- Updating Provar Automation
- Using Provar Automation
- 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
- NitroX
- Provar desktop
- Provar Test Builder
- Refresh and Recompile
- Reintroduction of CLI license Check
- 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 Automation Command Line Interface
- Continuous integration
- AutoRABIT Salesforce DevOps in Provar Test
- Azure DevOps
- Running a Provar CI Task in Azure DevOps Pipelines
- Configuring the Automation 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 Automation 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
- Provar Automation trial guide and extensions
- Salesforce Testing
- Provar Manager
- Best Practices
- Troubleshooting
- Release Notes