Shadow DOM Settings for Scenario Editor Tests

Recommended guidance

Shadow DOM can hide application elements behind component boundaries, which affects how Scenario Editor identifies and interacts with controls. Review Shadow DOM settings when selectors work on normal pages but fail inside web components.

When to review these settings

• Elements are visible but cannot be found during playback.
• Recorded locators are unstable inside custom components.
• Self-healing chooses a similar element outside the intended component.
• The application framework changed and moved elements into shadow roots.

Maintenance workflow

1. Confirm the target element is inside open or closed Shadow DOM.
2. Use stable labels, accessible names, or application-provided test attributes when possible.
3. Validate the selector in the same browser and Test Node used by the scenario.
4. Update waits and assertions so the component is ready before interaction.
5. Document Shadow DOM dependencies that may break after front-end framework changes.

Last updated: October 6, 2026