Force option for hidden elements in Cypress - Test Execution Trace

Test Overview

This test checks clicking a hidden button using Cypress's force: true option. It verifies that the click works even if the button is not visible.

Test Code - Cypress

Cypress

describe('Force click on hidden element', () => {
  it('Clicks hidden button using force option', () => {
    cy.visit('https://example.cypress.io/commands/actions')
    // The button is hidden by default
    cy.get('#hidden-button').click({ force: true })
    // Verify the click triggered a visible change
    cy.get('#hidden-button-clicked').should('be.visible')
  })
})

Execution Trace - 5 Steps

Step	Action	System State	Assertion	Result
1	Test starts	Test runner initialized, browser ready	—	PASS
2	Browser opens and navigates to https://example.cypress.io/commands/actions	Page loaded with elements including a hidden button with id 'hidden-button'	—	PASS
3	Find element with id 'hidden-button'	Hidden button element located in DOM but not visible	Element exists in DOM	PASS
4	Click the hidden button using { force: true } option	Button is clicked despite being hidden	Click event triggered on hidden button	PASS
5	Check that element with id 'hidden-button-clicked' is visible	Element '#hidden-button-clicked' is visible on page indicating click success	Element '#hidden-button-clicked' is visible	PASS

Failure Scenario

Failing Condition: Click fails because force option is not used on hidden element

Execution Trace Quiz - 3 Questions

Why is the { force: true } option used in cy.click()?

A To scroll the element into view before clicking

B To click an element even if it is hidden or covered

C To wait for the element to become visible before clicking

D To disable clicking on the element

Key Result

Use the { force: true } option in Cypress to interact with elements that are hidden or covered, ensuring tests can simulate user actions even when elements are not visible.

Practice

1. What does the force: true option do in Cypress when interacting with elements?

easy

A. Allows Cypress to interact with elements even if they are hidden or not visible.

B. Prevents Cypress from clicking on disabled buttons.

C. Automatically waits for elements to become visible before interacting.

D. Skips the test if the element is not visible.

Solution

1. Step 1: Understand the purpose of force: true

   This option tells Cypress to ignore visibility checks and interact with elements even if they are hidden.

2. Step 2: Compare with default behavior

   By default, Cypress only interacts with visible elements. Using force: true overrides this.

3. Final Answer:

   Allows Cypress to interact with elements even if they are hidden or not visible. -> Option A

4. Quick Check:

   force: true = interact hidden elements [OK]

Hint: Force option lets you click hidden elements safely [OK]

Common Mistakes:

• Thinking force waits for visibility
• Assuming force disables tests on hidden elements
• Confusing force with automatic retries

2. Which of the following is the correct syntax to click a hidden button with id submitBtn using Cypress?

easy

A. cy.get('#submitBtn').click(force=true);

B. cy.get('#submitBtn').click(force:true);

C. cy.get('#submitBtn').click({ force = true });

D. cy.get('#submitBtn').click({ force: true });

Solution

1. Step 1: Recall correct object syntax for options

   Cypress expects options as an object inside curly braces with key-value pairs, e.g., { force: true }.

2. Step 2: Identify correct syntax among options

   cy.get('#submitBtn').click({ force: true }); uses the correct object syntax with curly braces and colon separator.

3. Final Answer:

   cy.get('#submitBtn').click({ force: true }); -> Option D

4. Quick Check:

   Options object uses curly braces and colon [OK]

Hint: Use curly braces and colon for options: { force: true } [OK]

Common Mistakes:

• Using parentheses instead of braces for options
• Using equal sign instead of colon
• Missing braces around options

3. Consider this Cypress code snippet:

cy.get('.hidden-checkbox').check({ force: true });
cy.get('.hidden-checkbox').should('be.checked');

What will be the result of this test?

medium

A. The test will fail because the checkbox is hidden.

B. The test will pass because force allows checking hidden checkboxes.

C. The test will throw a syntax error.

D. The test will skip the check assertion.

Solution

1. Step 1: Understand the effect of force: true on hidden checkboxes

   Using force: true allows Cypress to check the checkbox even if it is hidden.

2. Step 2: Verify the assertion outcome

   The next line asserts the checkbox is checked, which will be true because the previous command succeeded.

3. Final Answer:

   The test will pass because force allows checking hidden checkboxes. -> Option B

4. Quick Check:

   force: true lets hidden checkbox be checked [OK]

Hint: Force lets you check hidden checkboxes successfully [OK]

Common Mistakes:

• Assuming hidden elements cannot be checked
• Confusing force with visibility wait
• Expecting syntax errors from correct code

4. You wrote this Cypress test:

cy.get('#hiddenBtn').click();

It fails because the button is hidden. How can you fix it without changing the HTML?

medium

A. Use cy.get('#hiddenBtn').click({ wait: true });

B. Add .should('be.visible') before clicking.

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

D. Change the selector to a visible element.

Solution

1. Step 1: Identify why the test fails

   The button is hidden, so Cypress refuses to click it by default.

2. Step 2: Apply the force option to override visibility check

   Adding { force: true } to the click command forces Cypress to click the hidden button.

3. Final Answer:

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

4. Quick Check:

   Force option overrides hidden element click failure [OK]

Hint: Use force: true to click hidden elements without HTML changes [OK]

Common Mistakes:

• Adding visibility assertion before click (won't fix hidden)
• Using invalid option like wait: true
• Changing selectors instead of fixing interaction

5. You want to test a hidden dropdown menu that appears only on hover. The dropdown is hidden by default. Which Cypress command correctly selects an option inside it?

hard

A. cy.get('#dropdown').select('Option 1', { force: true });

B. cy.get('#dropdown').select('Option 1');

C. cy.get('#dropdown').invoke('show').select('Option 1');

D. cy.get('#dropdown').click().select('Option 1');

Solution

1. Step 1: Understand dropdown visibility and interaction

   The dropdown is hidden by default, so normal select won't work without visibility.

2. Step 2: Use force option to select hidden option

   Using { force: true } allows Cypress to select the option even if the dropdown is hidden.

3. Step 3: Evaluate other options

   cy.get('#dropdown').select('Option 1'); fails due to hidden dropdown. cy.get('#dropdown').invoke('show').select('Option 1'); tries to show dropdown via invoke but may not trigger UI properly. cy.get('#dropdown').click().select('Option 1'); clicks dropdown but does not guarantee visibility or selection.

4. Final Answer:

   cy.get('#dropdown').select('Option 1', { force: true }); -> Option A

5. Quick Check:

   Select hidden dropdown option using force: true [OK]

Hint: Use select with force: true for hidden dropdowns [OK]

Common Mistakes:

• Trying to select without force on hidden dropdown
• Using invoke('show') without proper UI event
• Clicking dropdown without ensuring visibility