Iframe interaction strategies in Cypress - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to get the iframe body for interaction.

Cypress

cy.get('iframe').its('0.contentDocument.body').should('[1]', 'not.be.empty').then(cy.wrap)

Drag options to blanks, or click blank then click option'

Aexist

Bbe.visible

Ccontain

Dhave.length

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'be.visible' causes flaky tests if iframe is hidden initially.

Using 'contain' is incorrect because we check existence, not content.

We use should('exist') to ensure the iframe's body is present before interacting.

2fill in blank

medium

Complete the code to click a button inside the iframe.

Cypress

cy.get('iframe').its('0.contentDocument.body').should('exist').then(cy.wrap).find('[1]').click()

Drag options to blanks, or click blank then click option'

Ainput[type='text']

Bdiv.button

Cbutton.submit

D#submitBtn

Attempts:

3 left

💡 Hint

Common Mistakes

Using input[type='text'] selects a text field, not a button.

Using class selectors may select multiple elements causing test failures.

The selector #submitBtn targets the button by its unique ID inside the iframe.

3fill in blank

hard

Fix the error in the code to correctly access iframe contents.

Cypress

cy.get('iframe').[1]('0.contentDocument.body').should('exist').then(cy.wrap)

Drag options to blanks, or click blank then click option'

Afind

Bits

Cget

Dcontains

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'find' causes an error because '0.contentDocument.body' is not a selector.

Using 'contains' is for text matching, not property access.

The its command accesses a property of the iframe element, here 0.contentDocument.body.

4fill in blank

hard

Fill both blanks to wait for iframe load and then interact with its body.

Cypress

cy.get('iframe').[1]('load').then(() => {
  cy.get('iframe').its('[2]').should('exist').then(cy.wrap)
})

Drag options to blanks, or click blank then click option'

Ashould

B0.contentDocument.body

C0.contentWindow.document.body

Dtrigger

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'should' instead of 'trigger' does not wait for load event.

Using '0.contentWindow.document.body' is less common and may cause confusion.

We use trigger('load') to wait for the iframe to load, then access 0.contentDocument.body to interact.

5fill in blank

hard

Fill all three blanks to create a custom command to get iframe body.

Cypress

Cypress.Commands.add('getIframeBody', () => {
  return cy.get('iframe').[1]('0.contentDocument.body').should('[2]', 'not.be.empty').then(cy.[3])
})

Drag options to blanks, or click blank then click option'

Aits

Bexist

Cwrap

Dfind

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'find' instead of 'its' causes errors accessing properties.

Using 'should('be.visible')' may fail if iframe is hidden.

This custom command uses its to get the iframe body, asserts it exists and is not empty, then wraps it for Cypress chaining.

Practice

1. Why do iframes need special handling in Cypress tests?

easy

A. Because iframes load separate HTML documents inside the main page

B. Because iframes are always hidden elements

C. Because Cypress cannot find elements outside the iframe

D. Because iframes automatically block all user interactions

Solution

1. Step 1: Understand iframe structure

   An iframe loads a separate HTML document inside the main page, acting like a mini browser window.

2. Step 2: Recognize Cypress limitation

   Cypress commands by default work on the main page DOM, so special steps are needed to access iframe content.

3. Final Answer:

   Because iframes load separate HTML documents inside the main page -> Option A

4. Quick Check:

   Iframes = separate pages inside page [OK]

Hint: Remember iframe is like a page inside a page [OK]

Common Mistakes:

• Thinking iframe content is part of main DOM
• Assuming iframe is always hidden
• Believing Cypress can't access iframe at all

2. Which Cypress command correctly wraps the iframe body for interaction?

easy

A. cy.get('iframe').find('body').wrap()

B. cy.get('iframe').contentWindow.body.then(cy.wrap)

C. cy.get('iframe').contentDocument.body.wrap()

D. cy.get('iframe').its('0.contentDocument.body').then(cy.wrap)

Solution

1. Step 1: Access iframe document body

   Use its('0.contentDocument.body') to get the iframe's body element correctly.

2. Step 2: Wrap body for Cypress commands

   Use then(cy.wrap) to wrap the body so Cypress commands can chain inside the iframe.

3. Final Answer:

   cy.get('iframe').its('0.contentDocument.body').then(cy.wrap) -> Option D

4. Quick Check:

   Correct iframe body access = cy.get('iframe').its('0.contentDocument.body').then(cy.wrap) [OK]

Hint: Use its('0.contentDocument.body').then(cy.wrap) [OK]

Common Mistakes:

• Using contentWindow instead of contentDocument
• Trying to wrap without then()
• Calling wrap() directly on body without cy.wrap

3. What will the following Cypress code do?

cy.get('iframe').its('0.contentDocument.body').then(cy.wrap).find('button').click()

medium

A. Fails because iframe contentDocument is undefined

B. Throws an error because find() cannot be used after then()

C. Clicks the button inside the iframe after wrapping the iframe body

D. Clicks the button outside the iframe on the main page

Solution

1. Step 1: Wrap iframe body for chaining

   The code gets the iframe, accesses its body, wraps it so Cypress commands can chain inside.

2. Step 2: Find and click button inside iframe

   After wrapping, it finds the button inside iframe body and clicks it correctly.

3. Final Answer:

   Clicks the button inside the iframe after wrapping the iframe body -> Option C

4. Quick Check:

   Wrapping iframe body enables find() and click() inside iframe [OK]

Hint: Wrap iframe body before find() to interact inside [OK]

Common Mistakes:

• Assuming find() works on iframe element directly
• Not wrapping iframe body before chaining
• Confusing iframe contentDocument with undefined

4. You wrote this code but it fails with 'Cannot read property body of undefined':

cy.get('iframe').its('0.contentDocument.body').then(cy.wrap).find('input').type('Hello')

What is the likely cause?

medium

A. The iframe content has not loaded yet when accessing contentDocument

B. The selector 'iframe' is incorrect and finds no element

C. You cannot use then() with cy.wrap in Cypress

D. The input element does not exist inside the iframe

Solution

1. Step 1: Understand error meaning

   'Cannot read property body of undefined' means contentDocument is undefined because iframe content is not ready.

2. Step 2: Recognize iframe loading timing

   Iframe content loads asynchronously; accessing contentDocument too early causes undefined error.

3. Final Answer:

   The iframe content has not loaded yet when accessing contentDocument -> Option A

4. Quick Check:

   Wait for iframe load before accessing contentDocument [OK]

Hint: Wait for iframe to load before accessing contentDocument [OK]

Common Mistakes:

• Assuming selector is wrong without checking
• Thinking then() with cy.wrap is invalid
• Ignoring iframe load timing issues

5. You want to click a button inside an iframe, but the iframe content loads slowly. Which is the best Cypress strategy to ensure stable interaction?

hard

A. Directly call cy.get('iframe').find('button').click() without waiting

B. Use cy.get('iframe').its('0.contentDocument.body').should('not.be.empty').then(cy.wrap).find('button').click()

C. Use cy.wait(5000) before accessing iframe content

D. Reload the page until the iframe button is found

Solution

1. Step 1: Wait for iframe body to load

   Using should('not.be.empty') waits until iframe body has content, ensuring it's loaded.

2. Step 2: Wrap and interact safely

   After confirming content, wrap the body and find the button to click reliably.

3. Final Answer:

   Use cy.get('iframe').its('0.contentDocument.body').should('not.be.empty').then(cy.wrap).find('button').click() -> Option B

4. Quick Check:

   Wait for iframe content before actions = Use cy.get('iframe').its('0.contentDocument.body').should('not.be.empty').then(cy.wrap).find('button').click() [OK]

Hint: Use should('not.be.empty') to wait iframe content [OK]

Common Mistakes:

• Using fixed wait times instead of content checks
• Trying to find elements directly on iframe without wrapping
• Reloading page repeatedly instead of waiting properly