End-to-End Salesforce Automation: Lightning Components, a Dynamic DOM, and OTP MFA

Description and use

Salesforce automation that handles dynamic DOM, Lightning components, and OTP MFA enables unattended end‑to‑end business workflows using stable selectors, persistent sessions, and an isolated environment.

Problem

Salesforce’s dynamic DOM, Lightning components, and OTP-based MFA make naive automation fragile, preventing unattended end‑to‑end business workflow tests.

Outcome

The suite runs unattended, handling dynamic DOM changes, Lightning components, and OTP MFA without manual intervention or full test rewrites.

Workflow

• Identify stable selectors or build custom strategies for dynamic DOM elements.
• Use a Chrome Debugger Profile to maintain an authenticated session and bypass OTP challenges.
• Configure a dedicated VM for consistent execution environment.
• Implement component‑aware automation logic for Lightning components (dynamic forms, dropdowns, tables, pop‑ups).
• Apply fallback selector strategies and enable selector healing to patch broken selectors without full rewrites.
• Automate complete business workflows across multiple Salesforce screens, including navigation, data entry, validation, and record updates.

Evidence

Salesforce’s Lightning interface generates much of its markup dynamically, and element attributes — including IDs and classes automation would normally rely on — can change between sessions or even between renders of the same page.

Source

Instead, we used a dedicated Chrome Debugger Profile to maintain an already-authenticated Salesforce session.

Source

We configured a dedicated VM specifically for Salesforce test execution, separate from other automation infrastructure.

Source

Salesforce-specific components — dynamic forms, dropdowns, data tables, pop-ups, and Lightning components generally — needed automation logic built for how they actually behave, not treated like standard HTML controls.

Source