Tests That Heal Themselves
Stop spending 30% of your sprint fixing broken test scripts. Our AI adapts to UI changes automatically.
When a developer changes a button class or moves an element into a new layout, legacy tests fail. SimpleTest detects the semantic change, auto-patches the test script, and opens a PR for you—all without manual intervention.
SimpleTest, defined.
When Salesforce UI changes, SimpleTest heals the test. QA stops spending 80% of the sprint on locators.
What we address
What we address
- Maintenance is the jobPackage, Lightning, and Flow changes break scripts every week. Coverage silently dies.
- Flaky red buildsNobody trusts the suite. Teams ignore failures or skip the gate.
- Heal-by-handEngineers chase CSS IDs after every community or console restyle.
- Fear of upgradingTeams delay FSC, CGC, or Experience Cloud packages because tests will not survive.
What you get
What you get
- Self-healing locatorsIntent survives Lightning, Flow, and template changes.
- Time back for explorationQA spends the sprint finding real bugs, not patching selectors.
- A suite you can requireStable results mean the PR check stays on. Failures mean something real broke.
- Upgrades without a freezeShip the cloud package. Re-run. Heal. Merge.
End-to-end AI test maintenance flow.
Lightning rerenders break locators. Watch SimpleTest snapshot the DOM, patch selectors, retry the step, and only open CI after every healed path passes.
Test Cases
Test execution
Waiting for run
0%
Starting
Stop Chasing
Broken Selectors.
Our AI maintenance engine detects structural drift in your application and patches the underlying code automatically.
Root Cause Analysis
When a test fails, SimpleTest doesn't just throw a timeout error. It analyzes the DOM tree from the previous passing run against the current failure to pinpoint exactly what changed visually and structurally.
Intelligent Patching
If an ID changes from `#submit-v1` to `#submit-v2`, or a button is moved to a new div container, the AI dynamically recalculates the most resilient selector strategy and patches the test execution in real-time.
Automated PRs
We never change your source code without permission. When a test is healed, SimpleTest automatically generates a Pull Request with the corrected code for your QA engineers to review and merge.
Watch a Test Heal Itself.
A real-world example: Salesforce pushes a Lightning Winter '26 update. A button moves. Your test breaks. Here's what happens next — automatically.
TC-0087 'Create Opportunity' failed at Step 3: Click 'Save' button
DOM diff: button[data-aura-class='forceActionButton'] moved from div.actionsContainer to div.slds-page-header__control
Old: button.slds-button[data-aura-rendered-by='412:0'] → New: button[title='Save'][data-aura-class='forceActionButton']
Re-executed TC-0087 with healed selector — all 6 steps passed
PR #412 opened: 'fix(TC-0087): update Save button selector after Lightning Winter '26 release'
Why Salesforce Tests Break.
Salesforce ships 3 major releases per year. Each one can silently break your entire test suite.
Tri-Annual Releases
Spring, Summer, and Winter releases change Lightning component structure, shadow DOM hierarchy, and Aura rendering IDs across every org.
Dynamic Aura IDs
Salesforce generates data-aura-rendered-by IDs at runtime. IDs like '412:0' can change to '597:0' on every page load, breaking ID-based selectors.
Shadow DOM Depth
Lightning Web Components use nested shadow roots up to 6 levels deep. Standard querySelector calls cannot penetrate these boundaries.
Async Loading Patterns
Salesforce uses complex async rendering — spinners, lazy loading, skeleton screens. Hard-coded waits either timeout or slow tests down.
Custom LWC Components
Admins and developers deploy custom Lightning components that change the DOM structure unpredictably across sandbox and production orgs.
Field-Level Changes
Adding, removing, or reordering fields on a page layout shifts the entire DOM structure, invalidating positional selectors.
Before & After SimpleTest AI.
Manual selector fixes after every Salesforce release
Tests fail randomly due to dynamic IDs and timing
Per broken test — investigating DOM changes manually
QA team can't guarantee test results are reliable
AI auto-heals broken selectors and opens PRs
Semantic anchoring eliminates dynamic ID failures
AI detects, heals, verifies, and commits automatically
Every Salesforce release passes regression within minutes
Full Visibility Into Test Health.
Track every auto-heal, every flaky test, and every PR — all from a single command center.
Everything in SimpleTest.
Generation, data, recording, parallel runs, self-healing, and CI gates — one product, every Salesforce release.
Stop fixing broken tests by hand.
Let AI heal Salesforce tests when the UI changes, then ship with confidence.