Full-page screenshots in Cypress - Build an Automation Script

Capture full-page screenshot of the homepage

Preconditions (2)

Step 1: Open the browser and navigate to the homepage URL 'https://example.cypress.io'

Step 2: Wait for the page to fully load

Step 3: Take a full-page screenshot of the homepage

✅ Expected Result: A full-page screenshot image file is saved in the Cypress screenshots folder capturing the entire homepage content

Automation Requirements - Cypress

Assertions Needed:

Verify the screenshot file is created after the test runs

Best Practices:

Use cy.visit() to open the page

Use cy.screenshot() with the 'fullPage' option set to true

Use descriptive screenshot names

Avoid hardcoded waits; rely on Cypress automatic waits

Automated Solution

Cypress

describe('Full-page screenshot test', () => {
  it('should capture a full-page screenshot of the homepage', () => {
    cy.visit('https://example.cypress.io');
    // Cypress automatically waits for page load
    cy.screenshot('homepage-fullpage', { capture: 'fullPage' });
  });
});

This test opens the homepage URL using cy.visit(). Cypress waits automatically for the page to load fully before proceeding. Then, cy.screenshot() is called with the option { capture: 'fullPage' } to capture the entire page, not just the visible viewport. The screenshot is saved with the name homepage-fullpage in the default Cypress screenshots folder.

This approach avoids hardcoded waits and uses Cypress best practices for reliable and maintainable tests.

Common Mistakes - 3 Pitfalls

{'mistake': "Using cy.screenshot() without the 'fullPage' option", 'why_bad': 'Only the visible part of the page is captured, missing content below the fold', 'correct_approach': "Always specify { capture: 'fullPage' } to capture the entire page"}

Adding fixed waits like cy.wait(5000) before taking screenshot

Using invalid or non-descriptive screenshot names

Bonus Challenge

Now add data-driven testing to capture full-page screenshots of three different URLs

Show Hint

Practice

1. What does cy.screenshot({ capture: 'fullPage' }) do in Cypress testing?

easy

A. Clears all previous screenshots

B. Takes a screenshot of the entire webpage, including parts not visible on screen

C. Records a video of the test run

D. Takes a screenshot only of the visible part of the webpage

Solution

1. Step 1: Understand the capture option in cy.screenshot()

   The capture option controls what part of the page is captured. Setting it to 'fullPage' means the entire page, not just the visible viewport.

2. Step 2: Compare with other options

   By default, cy.screenshot() captures only the visible part. 'fullPage' extends this to the whole page including scrollable areas.

3. Final Answer:

   Takes a screenshot of the entire webpage, including parts not visible on screen -> Option B

4. Quick Check:

   Full-page screenshot = entire webpage [OK]

Hint: Remember 'fullPage' means capture everything, not just visible [OK]

Common Mistakes:

• Thinking it captures only visible viewport
• Confusing screenshot with video recording
• Assuming it clears previous screenshots

2. Which of the following is the correct syntax to take a full-page screenshot in Cypress?

easy

A. cy.fullPageScreenshot()

B. cy.screenshot('fullPage')

C. cy.screenshot({ capture: 'fullPage' })

D. cy.screenshot.capture('fullPage')

Solution

1. Step 1: Recall the correct method signature

   The cy.screenshot() command accepts an options object where capture: 'fullPage' is the correct way to specify full-page capture.

2. Step 2: Eliminate incorrect syntax

   Passing 'fullPage' as a string argument directly, using non-existent commands like cy.fullPageScreenshot(), or trying to chain .capture('fullPage') are not valid Cypress syntax for full-page screenshots.

3. Final Answer:

   cy.screenshot({ capture: 'fullPage' }) -> Option C

4. Quick Check:

   Correct syntax uses options object with capture key [OK]

Hint: Use curly braces and capture key for full-page screenshots [OK]

Common Mistakes:

• Passing 'fullPage' as a string argument directly
• Using non-existent commands like cy.fullPageScreenshot()
• Trying to chain .capture() method

3. Consider this Cypress test code snippet:

cy.visit('https://example.com')
cy.screenshot({ capture: 'fullPage' })

What will happen if the page is still loading when the screenshot is taken?

medium

A. The screenshot will capture the fully loaded page anyway

B. The test will fail with an error

C. Cypress will wait automatically until the page loads before screenshot

D. The screenshot may capture an incomplete or partially loaded page

Solution

1. Step 1: Understand Cypress behavior on page load

   Cypress does not automatically wait for all page content to load unless explicitly told. If cy.screenshot() runs immediately after cy.visit(), the page might still be loading.

2. Step 2: Effect on screenshot

   If the page is not fully loaded, the screenshot will capture whatever is visible at that moment, possibly incomplete content.

3. Final Answer:

   The screenshot may capture an incomplete or partially loaded page -> Option D

4. Quick Check:

   Screenshot timing affects completeness [OK]

Hint: Always wait for page load before screenshot to avoid partial capture [OK]

Common Mistakes:

• Assuming Cypress waits automatically for full load
• Expecting error if page not loaded
• Thinking screenshot always captures full content

4. You wrote this Cypress test:

cy.visit('https://example.com')
cy.screenshot({ capture: 'fullpage' })

Why does the full-page screenshot not work as expected?

medium

A. The option value 'fullpage' is case-sensitive and should be 'fullPage'

B. You must call cy.fullPageScreenshot() instead

C. The cy.screenshot() command does not support options

D. You need to add wait() before screenshot

Solution

1. Step 1: Check the option value spelling and case

   The correct option value is 'fullPage' with capital P. 'fullpage' is invalid and ignored.

2. Step 2: Understand Cypress option sensitivity

   Cypress options are case-sensitive. Using wrong case causes fallback to default behavior (visible viewport only).

3. Final Answer:

   The option value 'fullpage' is case-sensitive and should be 'fullPage' -> Option A

4. Quick Check:

   Option values are case-sensitive in Cypress [OK]

Hint: Check option spelling and case carefully [OK]

Common Mistakes:

• Ignoring case sensitivity in option values
• Using non-existent commands
• Assuming wait fixes option errors

5. You want to capture a full-page screenshot only after a dynamic content section finishes loading. Which Cypress code snippet correctly waits for the content and then takes a full-page screenshot?

hard

A. cy.get('#dynamic-section').should('be.visible')
.then(() => cy.screenshot({ capture: 'fullPage' }))

B. cy.screenshot({ capture: 'fullPage' })
cy.get('#dynamic-section').should('be.visible')

C. cy.wait(5000)
cy.screenshot({ capture: 'fullPage' })

D. cy.get('#dynamic-section').click()
cy.screenshot({ capture: 'fullPage' })

Solution

1. Step 1: Wait for dynamic content visibility

   Using cy.get('#dynamic-section').should('be.visible') waits until the dynamic section is visible, ensuring content is loaded.

2. Step 2: Take full-page screenshot after wait

   Chaining .then(() => cy.screenshot({ capture: 'fullPage' })) ensures the screenshot runs only after the wait condition passes.

3. Final Answer:

   cy.get('#dynamic-section').should('be.visible') .then(() => cy.screenshot({ capture: 'fullPage' })) -> Option A

4. Quick Check:

   Wait for content visible, then screenshot [OK]

Hint: Wait for element visible before screenshot using should('be.visible') [OK]

Common Mistakes:

• Taking screenshot before waiting for content
• Using fixed wait times instead of element checks
• Clicking element unnecessarily before screenshot