With every Salesforce release, the ecosystem becomes smarter, faster, and more user friendly. However, as the platform evolves, so do the complexities of maintaining test automation scripts.
The Spring ’25 release is no exception, with exciting new UI changes and enhanced components designed to improve productivity for users. But for testers, these updates can feel like navigating a maze of new DOM structures and layouts.
Here’s the good news: With Provar’s advanced automation capabilities, you can stop worrying about broken scripts and start focusing on the future. Let’s break down the Spring ’25 changes, their real world impact, and how Provar ensures your testing workflows remain bulletproof.
Advanced Search Changes: A Replacement for Lookups
What’s Changing:
The traditional Lookup screen has undergone a major transformation in Spring ’25, evolving into a brand new Advanced Search screen built on lwc with new elements such as radio buttons and search and select options. From a test automation perspective, this is a significant change that impacts all objects and nearly every test case. These updates necessitate creating new automation scripts for tools.
Usage and Impact:
Lookups are integral to Salesforce workflows and are widely used in end-to-end flows for both Standard and Custom objects. Rewriting scripts for every object with conventional tools could result in considerable effort, frustration, and a loss of critical time during the Salesforce release cycle.
How Provar Helps:
Provar ensures that your existing Lookup scripts remain fully functional even with this new Advanced Search screen.This saves substantial time and effort, allowing testers to focus on creating new test cases instead of revisiting and maintaining the old ones.
Path Assistant’s LWC Transition
What’s Changing:
In an interesting update not explicitly mentioned in the release notes, the Path Assistant has been moved to the LWC framework, aligning with Salesforce’s long-term vision of migrating to LWC. This change alters the DOM structure for all Path components, introducing challenges for automation scripts built on the previous framework.
Usage and Impact:
The Path Assistant plays a critical role in guiding users through key workflows, such as sales stages and case resolutions. While the transition to LWC enhances performance and responsiveness, it can disrupt automation scripts that rely on older DOM structures, leading to potential rework and delays.
How Provar Helps:
Provar handles the transition effortlessly, ensuring that existing and new path scripts work flawlessly. This means your automation is ready to embrace Salesforce’s Lightning future without missing a beat and also saves significant time and effort by eliminating the need for script rework.
Section Metadata Sync for Standard/Flexi Pages
What’s Changing:
Hidden sections in page layouts are now treated as independent layouts, rather than being grouped under the previous section. This change alters the DOM indexing for subsequent sections and brings it in sync with layout information on Record Layout and metadata. As a result, key screens like New, View, and Edit are impacted across Salesforce objects.
Usage and Impact:
The Path component change affects opportunities, leads, campaigns, contracts, contacts, orders, and custom objects etc record detail pages in Lightning Experience (with the exception of Campaigns and Tasks). This change impacts non-English languages as well. For testers and admins, metadata shifts often lead to cascading script failures, requiring substantial updates and effort to fix issues tied to fixed DOM indexing.
How Provar Helps:
Provar guarantees seamless compatibility with these updates, ensuring that existing test cases, including those for Path components, remain fully functional. This eliminates disruptions and allows testers to focus on Spring ’25 functionalities instead of time consuming script fixes. Provar saves you effort, reduces complexity, and ensures a hassle-free transition.
Card View of Related List and Recent Items
What’s Changing:
Updates to the DOM attributes for Related List, Related List Single, and Recent Items have been introduced. However, these changes are limited to the Card View layout for Related List Single and Recent Items, while the Table View remains unaffected.
Usage and Impact:
Card Views are widely preferred for their visual clarity and ease of navigation, especially in compact or flexi page layouts. These updates impact all fields under Recent Items and Related Lists, RL Singles in the Card View, potentially causing automation scripts that rely on the updated class attributes to encounter errors.
How Provar Helps:
Provar ensures complete compatibility with these changes, allowing seamless automation for Card Views of Related List, Related List Single, and Recent Items. Provar’s capabilities eliminate script failures and the need for tedious updates, saving valuable time and effort for your team while maintaining the integrity of your testing flow.
Read Only Fields (Owner, Created By, and Last Modified Fields
What’s Changing:
This change impacts the New, Edit, and Clone screens for all Standard and Custom Objects, where the DOM structure for key read only fields like Owner, Created By, and Last Modified By has been updated, leading to execution issues in automation scripts.
Usage and Impact:
These fields are critical for audit trails, data ownership, and regulatory compliance, particularly in industries with stringent reporting requirements. The DOM changes across these screens can result in unnecessary script failures, leading to frustration and increased maintenance effort.
How Provar Helps:
Provar ensures that your Provar automation scripts remain unaffected by these changes. Existing scripts will execute flawlessly without any modifications, and new mappings for tests will work seamlessly. Provar eliminates the need for time-consuming updates, ensuring your focus remains on testing new functionality rather than troubleshooting script issues.
Date Time Calendar on Classic Screens
What’s Changing:
For the first time in a while, an interesting change has been observed in Classic screens. While there are no functional or DOM changes, the Date Time calendar now lingers even after tabbing off during inline edits in Spring ’25. This disrupts the end to end automation flow, causing issues when setting values in other fields via automation.
Usage and Impact:
Date Time fields are widely used across multiple Standard and Custom Objects. This lingering behavior has a broad impact, as it interferes with setting other fields and disrupts the automated test flow. This can result in failed executions and inefficiencies.
How Provar Helps:
Provar handles this behavior seamlessly, ensuring that your scripts remain unaffected by the lingering Date Time calendar. Provar employs alternate mechanisms to close the floating calendar window, allowing smooth execution of scripts without interruptions.
Publisher Action Navigation
What’s Changing:
In Spring 25, there are dom changes in Publisher Actions for Work Order screens (e.g., Book Appointment, Candidates, and Emergency) include attribute modifications, such as the removal of the title attribute. This impacts navigation and automation flows.
Usage and Impact:
Work order management is the systematic process of creating, assigning, tracking, and completing maintenance and other field service requests to ensure smooth operations and high quality service delivery. This change affects the automatic navigation to these publisher actions in FSL causing failure during the use case flow.
How Provar Helps:
Provar scripts remain functional for both existing executions and new mappings, which means there is no additional effort required from our users to update any script, and they can rely on the test execution results to assess the impact of this Salesforce release on the org.
Why This Matters to You
Every Salesforce release is a double-edged sword. While it brings new features, it also introduces challenges for testers and admins managing automation. Without the right tools, you could be spending hours fixing broken scripts, updating page objects, and troubleshooting errors.
Provar is designed with Salesforce’s rapid evolution in mind, ensuring that your automation remains future proof, seamless, and efficient.
Want to learn more about how Provar can help you keep pace with every Salesforce release and product update? Contact our team today!
View the full list of changes here — Provar Documentation: Spring ’25 Release 1
