Deeply Nested DOM

Difficult DOM Deeply Intermediate Must Have

Hands-on

Interactive Sandbox

Static partial

Try this

  1. Open page
  2. Interact control
  3. Read result

Assert this

  • Visible elements
  • Text matches
  • Button state toggles

Difficult DOM / Deeply nested

Deeply Nested DOM

Inputs and buttons are buried several layers deep.

Traverse wrappers but still rely on stable data-test-id attributes.
Waiting inside nested layers
Layers have non-semantic classes to encourage robust locator strategies.

Learning & behavior

User flow

  1. Open page
  2. Interact control
  3. Read result

Learning objectives

  • Pick solid locators
  • Time waits
  • Assert state

Suggested assertions

  • Visible elements
  • Text matches
  • Button state toggles

Selector tips

Good

  • [data-test-id='deeply-nested-dom-primary']
  • [data-test-id='deeply-nested-dom-secondary']
  • [data-test-id='deeply-nested-dom-action']
  • [aria-label='Deeply Nested DOM']
  • getByRole('button', { name: 'Deeply' })

Fallback

  • section.deeply-nested-dom-container :nth-of-type(1)
  • .card.deeply_nested_dom button:nth-of-type(1)
  • form.deeply-nested-dom-form .field-group:nth-child(1)

Avoid

  • .mt-4.mb-2.flex.items-center > input:nth-child(1)
  • .css-1a2b3c4
  • div[class*='temp-'][class*='hover']

Notes

  • Some parts delay render
  • Icon buttons need aria-label
  • Layout classes may shift
Prev Icon-only Buttons
Shadow DOM Next