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 increasing 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 deliver an experimental feature for seeking customer feedback before general availability.
Provar’s TechOps team developed this feature during a recent innovation competition using our Custom API feature. This is an excellent 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 remove unused web elements by analyzing your test project. The execution for the existing test suite should not be 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 by clicking New Test Case under New Test drop-down menu.
Step 2: Drag and Drop API (Page Object Cleaner) from Test Palette into test case.
Click Test Palette 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. Select an option from the drop-down in the Clean Page Object field.
Above: Snapshot of Test Step Parameters section.
a). If you select Scan Unused Element, you can see all the unused elements from the page objects in the logs.
b). If you select Remove Unused Element, you can remove all the unused elements from the page objects.
2. In the Result Name field, enter the value.
3. the Test Case will be displayed automatically in the Result Scope field.
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 remove all the unused elements, as mentioned in Step 3.
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 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 can see it in logs, and any log file will not be generated.
Known Limitations
- 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.
- Provar Automation
- System Requirements
- Browser and Driver Recommendations
- Installing Provar Automation
- Updating Provar Automation
- Licensing Provar
- Granting Org Permissions to Provar Automation
- Optimizing Org and Connection Metadata Processing in Provar
- Using Provar Automation
- Provar Automation
- Creating a New Test Project
- Import Test Project from a File
- Import Test Project from a Remote Repository
- Import Test Project from Local Repository
- Commit a Local Test Project to Source Control
- API Testing
- Behavior-Driven Development
- Consolidating Multiple Test Execution Reports
- 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
- Japanese Language Support
- Override Auto-Retry for Test Step
- Mapping and Executing the Lightning Article Editor in Provar
- Managing Test Steps
- Namespace Org Testing
- NitroX
- Provar Test Builder
- ProvarDX
- 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 Data Generation
- 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
- Provar Manager
- How to Use Provar Manager
- Provar Manager Setup
- Provar Manager Integrations
- Release Management
- Test Management
- Test Operations
- Provar Manager and Provar Automation
- Setting Up a Connection to Provar Manager
- Object Mapping Between Automation and Manager
- How to Upload Test Plans, Test Plan Folders, Test Plan Instances, and Test Cases
- Provar Manager Filters
- Uploading Callable Test Cases in Provar Manager
- Uploading Test Steps in Provar Manager
- How to Know if a File in Automation is Linked in Test Manager
- Test Execution Reporting
- Metadata Coverage with Manager
- Provar Grid
- DevOps
- Introduction to Provar 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
- 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
- Version Control
- Salesforce Testing
- Recommended Practices
- Salesforce Connection Best Practices
- Improve Your Metadata Performance
- Java 21 Upgrade
- Testing Best Practices
- Automation Planning
- Supported Testing Phases
- Provar Naming Standards
- Test Case Design
- Create records via API
- Avoid using static values
- Abort Unused Test Sessions/Runs
- Avoid Metadata performance issues
- Increase auto-retry waits for steps using a global variable
- Create different page objects for different pages
- The Best Ways to Change Callable Test Case Locations
- Working with the .testProject file and .secrets file
- Best practices for the .provarCaches folder
- Best practices for .pageObject files
- Troubleshooting
- How to Use Keytool Command for Importing Certificates
- Installing Provar After Upgrading to macOS Catalina
- Browsers
- Configurations and Permissions
- Connections
- DevOps
- Error Messages
- Provar Manager 3.0 Install Error Resolution
- Provar Manager Test Case Upload Resolution
- 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
- Selenium 4 Upgrade
- Licensing, Installation and Firewalls
- Memory
- Test Builder and Test Cases
- Release Notes