Page Object Cleaner
When using Page Objects in Provar it’s possible that over time as you remap elements or refactor your test cases you may have mappings for elements that are no longer required. These can affect performance by bloating the size of your Page Objects and increase the compilation time during execution. To resolve this issue we have launched a new beta feature to allow you to automatically identify unused elements, and optionally remove them.
Note: We are delivering an experimental feature for seeking feedback from customers before general availability.
Provar’s TechOps team developed this feature during a recent innovation competition using our Custom API feature. This is a great example of the power of Provar Automation and how you can extend the platform. To learn more about Custom APIs please check out our help pages and documentation here.
The Page Object Cleaner will help you to remove all such unused web elements by analyzing your test project. The execution for the existing test suite should be not negatively impacted and there shouldn’t be extra log entries related to cleaner in the usual run for the existing test cases.
Note: The use of Provar Labs prototypes is at your own risk. Provar Labs prototypes should only be used on your non-production instance to test their functionality if you accept the risk of doing so. These prototypes have not completed the beta testing phase and might pose a higher-than-normal risk for bugs. We may enhance, withdraw or replace prototype features based on extended testing and feedback gathered. Do not rely on these features as part of your test automation.
Steps to remove unused Page Objects
Step 1: Create a new test case.
Click New Test Case under New Test drop-down menu.
Above: Snapshot of creating a new test case.
Step 2: Drag and Drop API (Page Object Cleaner) from Test Palette into test case.
Click Test Pallete on the Provar screen and drag Page Object Cleaner API from Custom API section to test case.
Above: Snapshot of Page object cleaner in the custom API section.
Step 3: Enter the required details in the TestStep parameters section
In the Test Step Parameters section –
1. In the Clean Page Object field, select an option from the drop-down.
Above: Snapshot of Test Step Parameters section.
a). If you select Scan Unused Element, you will be able to see all the unused elements from the page objects in the logs.
b). If you select Remove Unused Element, you will be able to remove all the unused elements from the page objects.
2. In the Result Name field, enter the value.
3. In the Result Scope field, the Test Case will be displayed automatically.
Step 4: Run the test case.
Click Run to execute the test case then you will be able to see the logs of all unused elements or you can remove all the unused elements as mentioned in Step 3.
Above: Snapshot of Scan Unused Element.
Above: Screenshot displaying “Remove unused element”.
Note: Unused elements are removed from the Page Object while selecting “Remove Unused Element” and will generate a Log file with Page Object’s location, name and with all removed elements. The backup will be created in the user directory.
By selecting the “Scan Unused Element”, elements will not be removed from the Page Object but we would be able to see it in logs and any log file will not be generated.
- Limited log entries output when the page object execution is performed
- The feature is currently placed in the Test Palette for visibility but we plan to move it to be a right click or menu item that uses a modal dialog providing multiple test project cleaning and refactoring options. This will remove the risk of accidental re-execution of the Page Object Cleaner when not required.
- The test case could have a web request step.
- 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
- Override auto-retry for Test Step
- 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
- Generate Test Case
- List compare
- Page Object Cleaner
- 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
- Guide in Salesforce CPQ Testing in Provar
- Guide in ServiceMax Testing
- Skuid Testing
- Vlocity API Testing
- Webservices testing
- 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
- 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
- Execution Environment Security Configuration
- Provar Jenkins Plugin
- Parallel Execution
- Running Provar on Linux
- Salesforce DX
- 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
- Configurations and permissions
- Error messages
- Administrator has blocked access to client
- 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
- Test Builder and test cases
- Release notes