Salesforce Application Testing
Lightning fast authoring and unmatched stability for testing Salesforce applications.Try TTA for Salesforce
Salesforce testing challenges
Class names and indexes can change frequently rendering them unreliable as locators.
Shadow DOM on many objects makes them more challenging for some tools to engage.
Many 3rd party apps integrate with Salesforce requiring built-in API testing for E2E scenarios.
Organizations' users can change views and layouts to suit their needs.
Classic and Lightning web pages and object properties are fluid and change based on context.
Salesforce users will have different role-based experiences that need to be validated.
Fast, flexible authoring
Author, configure and customize stable tests fast. Leverage pre-built actions to create Salesforce objects like accounts or contacts, interact with the objects, and validate expected results.
AI-powered Smart Locators automatically identify and lock in elements of default and custom objects. Testim handles dynamic tables and switches to active tabs automatically. You don’t need to constantly remap locators every time an object changes.
Testim automatically handles Salesforce Lightning components behind #shadow-root navigating the shadow tree to access and lock in DOM elements.
For changing attributes like those in Vlocity, Testim auto-maps and filters dynamic classes and IDs to improve the stability of elements.
Reuse made easy
Auto-complete a form or reuse a sequence of steps while authoring. Share steps or groups across multiple tests. Refactor duplications automatically to create cleaner tests.
AI-powered locators augmented by Salesforce metadata adjust and auto-improve to keep tests stable and minimize updates. Other tools require hours or days to fix tests when static locators break.
Error aggregation and suggested causes help you triage failures. Side-by-side screenshots pinpoint failures. Drill deeper with console and network logs at each test step.
Efficiently scaling your project entails organizing tests, assigning ownership, building trust in tests, establishing controls, and leveraging dashboards that reveal insights into your team and tests.
Problems with other automation tools
Tabs and frames
Salesforce pages are dynamic and include tabs that shift the context of embedded frames and objects. Traditional tools require multiple scripting or modeling paths to manually switch frames rather than automatically handling objects in different frames.
Frameworks like Selenium and tools that rely on them, use single locators to find elements and objects. These locators can frequently change from Salesforce updates and break your tests, requiring more maintenance time to fix.
Salesforce has default and custom objects that should be part of your tests. Custom objects strain these tools requiring deep Selenium and scripting experience, extending authoring time and increasing maintenance.
While some traditional tools can use scripts to pierce the Shadow DOM, it requires a particular tool or language knowledge, additional time scripting, and manual locator selection that lead to test flakiness.
Many tools rely on specific CSS selectors like class names, indexes, IDs that change frequently and break tests. Testim’s smart locators automatically filter and map dynamic attributes to keep your tests stable.
Creating tests for similar objects that repeat within a page like table rows, contacts, or opportunities can require multiple tests with manual locator selection at each step of a similar object.