Page object operations
A page object operation is a custom function that is used to execute Java code on a page object within Provar. You can use a page object operation in your test case when you need to perform UI testing that is either not possible or too complex to achieve using standard Provar test step types. In general, you need to write the Java code in a function and call it into your test case on a page object.
An example use case
The following includes one suggested use case. In this scenario, you can configure the filters on a custom Salesforce Visualforce page where the filtered data is defined in an Excel sheet which has to be read and driven into the test case and subsequently on the UI.
Strategy
First identify the UI fields to be mapped and the page object operations that you want to execute. Since this is a custom Visualforce page, you should define the page object and map the fields. Looking at the UI, the following fields can be easily mapped via the Test Builder using locators:
- Last Name
- Checkbox
- Delete Button
- Lookup
However, the fields – Field, Operator and Value are repetitive but do not form a table. The locators for these fields under a column are not unique and thus have to be assigned a row index on the column locator as shown for the Value column below.
To make the test case data-driven, you should read the data from the Excel file and pass it into the above page object operation using a Foreach loop.
Implementation
Step 1: Create a test case invoking the Salesforce Connection and launch the Test Builder.
Step 2: Read the Excel file for the data to be entered in the filters.
Step 3: Go to the Visualforce page. One-by-one, map the five fields as defined in the strategy using the Add operation within the Test Builder creating a new Page Object.
Step 4: Open the file from the Navigator under Project->src->pageobjects. Verify from the Page Object Editor view that the five fields have been mapped.
Step 5: From the Java Source tab, create a new page object operation as shown below.
Step 6: On the test case, add (drag and drop) the UI Action test step to create the test step to call the above page object operation (function) under the ForEach loop passing the values read from the Excel sheet as shown below.
Note: The function parameters defined above (LastName) are being reflected as inputs under interaction with the Action = Call.
Step 7: Order the test steps properly and debug and execute your test case to make sure all operations are performed successfully.
References for detailed Selenium help documentation:
http://www.seleniumhq.org/docs
https://newcircle.com/bookshelf/selenium_tutorial/index#introduction
Create a page object operation to retrieve the current URL from your browser
Step 1: Create a page object operation.
Step 2: Add a UI OnScreen test step and select the page object name.
Step 3: Add the Action API test step and select Page Operation.
Step 4: Insert the following:
package pageobjects; import java.util.List; import org.openqa.selenium.WebDriver; import org.openqa.selenium.WebElement; import org.openqa.selenium.support.FindBy; import com.provar.core.testapi.annotations.*; @Page(title = "Get Current URL", summary = "", relativeUrl = "", connection = "ThreePanellayout") public class GetCurrentURL { WebDriver driver; GetCurrentURL(WebDriver driver) { this.driver = driver; } public String getCurrentURL() { return driver.getCurrentUrl(); } }
- 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