Why DOM interaction handles complex UIs in Cypress - Automation Benefits in Action

Verify interaction with a complex UI element using DOM selectors

Preconditions (2)

Step 1: Locate the main dropdown menu using a data-cy attribute

Step 2: Click the main dropdown to expand it

Step 3: Locate a nested submenu item using a CSS selector

Step 4: Click the nested submenu item

Step 5: Verify that the nested submenu item triggers the expected action (e.g., displays a message or navigates)

✅ Expected Result: The nested submenu item is clicked successfully and the expected action occurs, demonstrating DOM interaction handles complex UI elements

Automation Requirements - Cypress

Assertions Needed:

Verify the main dropdown is visible before clicking

Verify the nested submenu item is visible before clicking

Verify the expected action after clicking the nested submenu item

Best Practices:

Use data-cy attributes for stable selectors

Use cy.get() with explicit assertions for visibility

Avoid brittle XPath selectors

Use Cypress commands chaining for readability

Use beforeEach hook to set up preconditions if needed

Automated Solution

Cypress

describe('Complex UI DOM Interaction Test', () => {
  beforeEach(() => {
    cy.visit('/complex-ui-page')
  })

  it('should interact with nested dropdown menu and verify action', () => {
    // Locate main dropdown using data-cy attribute and verify visibility
    cy.get('[data-cy=main-dropdown]').should('be.visible').click()

    // Locate nested submenu item and verify visibility
    cy.get('.submenu-item.nested').should('be.visible').click()

    // Verify expected action: for example, a message appears
    cy.get('[data-cy=action-message]').should('contain.text', 'Action successful')
  })
})

The test starts by visiting the page with the complex UI.

We use cy.get('[data-cy=main-dropdown]') to select the main dropdown menu. Using data-cy attributes ensures selectors are stable and not affected by styling or layout changes.

We assert the dropdown is visible before clicking to avoid errors.

Next, we select the nested submenu item with a CSS class selector .submenu-item.nested and assert it is visible before clicking.

Finally, we verify the expected action by checking that a message with data-cy=action-message contains the text 'Action successful'.

This approach shows how interacting with DOM elements directly allows us to handle complex UI components reliably.

Common Mistakes - 3 Pitfalls

Using brittle XPath selectors for nested elements

{'mistake': 'Not asserting element visibility before clicking', 'why_bad': 'Clicking invisible or non-existent elements causes test failures and unreliable results', 'correct_approach': "Always use assertions like .should('be.visible') before interacting with elements"}

Hardcoding waits or using cy.wait() instead of checking element state

Bonus Challenge

Now add data-driven testing with 3 different nested submenu items and verify their respective actions

Show Hint