Hidden elements handling in Cypress - Build an Automation Script

Verify interaction with hidden elements on a web page

Preconditions (2)

Step 1: Open the web page at URL 'https://example.com/hidden-elements'

Step 2: Locate the hidden button with id 'hidden-btn'

Step 3: Force click the hidden button

Step 4: Locate the hidden input field with id 'hidden-input'

Step 5: Force type the text 'Test Input' into the hidden input field

Step 6: Verify that a confirmation message with id 'confirmation-msg' becomes visible

✅ Expected Result: The hidden button is clicked successfully, the hidden input field receives the text, and the confirmation message is visible on the page

Automation Requirements - Cypress

Assertions Needed:

Verify the confirmation message is visible after interaction

Verify the hidden input field contains the typed text

Best Practices:

Use cy.get() with proper selectors

Use { force: true } option to interact with hidden elements

Use assertions like .should('be.visible') and .should('have.value')

Avoid flaky tests by waiting for elements to exist before interaction

Automated Solution

Cypress

describe('Hidden elements handling test', () => {
  beforeEach(() => {
    cy.visit('https://example.com/hidden-elements');
  });

  it('should interact with hidden elements using force option', () => {
    // Click the hidden button
    cy.get('#hidden-btn').click({ force: true });

    // Type into the hidden input field
    cy.get('#hidden-input').type('Test Input', { force: true });

    // Verify the hidden input field contains the typed text
    cy.get('#hidden-input').should('have.value', 'Test Input');

    // Verify the confirmation message is visible
    cy.get('#confirmation-msg').should('be.visible');
  });
});

This Cypress test visits the target page before each test to ensure a fresh state.

It uses cy.get() with the element IDs to locate the hidden button and input field.

Since these elements are hidden, the { force: true } option is used with click() and type() commands to bypass Cypress's default visibility checks.

Assertions check that the input field contains the typed text and that the confirmation message is visible, confirming the interactions succeeded.

This approach follows best practices by using explicit selectors, forcing actions on hidden elements, and verifying outcomes with clear assertions.

Common Mistakes - 3 Pitfalls

Trying to click or type on hidden elements without using { force: true }

Using vague or overly broad selectors like classes that match multiple elements

Not asserting the result of the interaction, such as missing confirmation message checks

Bonus Challenge

Now add data-driven testing with 3 different input texts for the hidden input field

Show Hint

Practice

1. Which Cypress command is used to check if an element is hidden on the page?

easy

A. .should('not.be.visible')

B. .click()

C. .type()

D. .should('be.enabled')

Solution

1. Step 1: Understand visibility assertion

   The command .should('not.be.visible') checks if an element is hidden or not visible on the page.

2. Step 2: Compare with other commands

   Commands like .click() and .type() perform actions, not visibility checks. .should('be.enabled') checks if an element is enabled, not visibility.

3. Final Answer:

   .should('not.be.visible') -> Option A

4. Quick Check:

   Check hidden = .should('not.be.visible') [OK]

Hint: Use .should('not.be.visible') to check hidden elements [OK]

Common Mistakes:

• Using .click() to check visibility
• Confusing enabled state with visibility
• Using .type() for visibility check

2. Which syntax correctly clicks a hidden button using Cypress?

easy

A. cy.get('button.hidden').click({ force: true })

B. cy.get('button.hidden').click()

C. cy.get('button.hidden').click({ visible: true })

D. cy.get('button.hidden').click({ hidden: false })

Solution

1. Step 1: Identify force option usage

   To click a hidden element, Cypress requires the option { force: true } to override visibility checks.

2. Step 2: Evaluate other options

   Options like { visible: true } or { hidden: false } are invalid in Cypress click command. Clicking without force on hidden element fails.

3. Final Answer:

   cy.get('button.hidden').click({ force: true }) -> Option A

4. Quick Check:

   Click hidden = click with { force: true } [OK]

Hint: Use { force: true } to click hidden elements [OK]

Common Mistakes:

• Omitting { force: true } when clicking hidden elements
• Using invalid options like { visible: true }
• Trying to click without force on hidden elements

3. What will be the result of this Cypress code snippet?

cy.get('#secret').should('not.be.visible')
cy.get('#secret').click()

Assuming #secret is hidden.

medium

A. Test fails at visibility check

B. Test passes, element clicked successfully

C. Test passes but click is ignored silently

D. Test fails at click because element is hidden

Solution

1. Step 1: Check visibility assertion

   The first line asserts the element is hidden, so it passes as expected.

2. Step 2: Analyze click on hidden element

   Clicking a hidden element without { force: true } causes Cypress to fail the test because the element is not interactable.

3. Final Answer:

   Test fails at click because element is hidden -> Option D

4. Quick Check:

   Click hidden without force = fail [OK]

Hint: Clicking hidden without force causes failure [OK]

Common Mistakes:

• Assuming click on hidden element passes
• Ignoring need for { force: true }
• Thinking click is silently ignored

4. You wrote this Cypress test:

cy.get('.hidden-link').click()

But the test fails with an error about element not being visible. What is the best fix?

medium

A. Add .should('be.visible') before click

B. Change selector to a visible element

C. Add { force: true } to the click command

D. Remove the click command

Solution

1. Step 1: Understand error cause

   The error occurs because Cypress cannot click a hidden element without forcing the action.

2. Step 2: Apply correct fix

   Adding { force: true } to .click() forces the click on the hidden element, fixing the error.

3. Final Answer:

   Add { force: true } to the click command -> Option C

4. Quick Check:

   Force click fixes hidden element error [OK]

Hint: Use { force: true } to fix hidden element click errors [OK]

Common Mistakes:

• Trying to click without force on hidden elements
• Adding visibility assertion before click on hidden element
• Removing click instead of fixing it

5. You want to test a hidden checkbox with id #agree. Which Cypress code correctly checks it and verifies it is checked?

hard

A. cy.get('#agree').check().should('be.checked')

B. cy.get('#agree').check({ force: true }).should('be.checked')

C. cy.get('#agree').click().should('be.checked')

D. cy.get('#agree').click({ force: true }).should('not.be.checked')

Solution

1. Step 1: Identify hidden element interaction

   Since the checkbox is hidden, .check() requires { force: true } to interact with it.

2. Step 2: Verify checked state

   After forcing the check, .should('be.checked') confirms the checkbox is checked.

3. Final Answer:

   cy.get('#agree').check({ force: true }).should('be.checked') -> Option B

4. Quick Check:

   Check hidden checkbox with force and assert checked [OK]

Hint: Use .check({ force: true }) for hidden checkboxes [OK]

Common Mistakes:

• Using .check() without force on hidden checkbox
• Using .click() instead of .check() for checkbox
• Asserting not checked after clicking