Full page screenshot in Selenium Python - Framework Patterns

Framework Mode - Full page screenshot

Folder Structure

selenium-python-project/
├── tests/
│   ├── test_full_page_screenshot.py
│   └── __init__.py
├── pages/
│   ├── base_page.py
│   └── home_page.py
├── utils/
│   ├── screenshot_helper.py
│   └── __init__.py
├── config/
│   ├── config.yaml
│   └── __init__.py
├── drivers/
│   └── chromedriver.exe (or chromedriver binary)
├── reports/
│   └── (test reports and screenshots saved here)
├── requirements.txt
└── conftest.py
    

Test Framework Layers

• Driver Layer: Manages browser setup and teardown using Selenium WebDriver.
• Page Objects: Classes representing web pages, encapsulating elements and actions (e.g., BasePage with screenshot method).
• Utilities: Helper functions like full page screenshot capture logic, image saving, and scrolling.
• Tests: Test scripts that use page objects and utilities to perform actions and assertions.
• Configuration: Environment settings, browser options, credentials stored in config files (e.g., YAML).
• Reports: Store screenshots and test reports for review.

Configuration Patterns

Use a config.yaml file to store environment URLs, browser types, and credentials.

# config/config.yaml
base_url: "https://example.com"
browser: "chrome"
screenshot_path: "reports/screenshots/"
    

Load config in conftest.py or utility modules to initialize WebDriver and paths.

import yaml

def load_config():
    with open('config/config.yaml') as f:
        return yaml.safe_load(f)
    

Test Reporting and CI/CD Integration

• Save full page screenshots in reports/screenshots/ with timestamped filenames.
• Use pytest-html or Allure for HTML test reports embedding screenshots.
• Integrate tests in CI/CD pipelines (GitHub Actions, Jenkins) to run on push and upload reports as artifacts.
• Configure failure hooks to capture screenshots automatically on test failure.

Best Practices

• Use Page Object Model to keep page interactions and screenshot logic organized.
• Implement explicit waits before taking screenshots to ensure page fully loads.
• Store screenshots with clear, timestamped names for easy traceability.
• Keep configuration separate from code for easy environment switching.
• Use utilities for scrolling and stitching screenshots if native full page capture is not supported.

Self Check

Where would you add a new utility function to scroll the page before taking a full page screenshot?

Key Result

Organize Selenium Python tests with clear layers, config, and utilities to capture reliable full page screenshots.

Practice

1. What is the main advantage of taking a full page screenshot in Selenium?

easy

A. It speeds up the test execution

B. It only captures the visible part of the webpage

C. It captures the entire webpage, including parts not visible on screen

D. It automatically scrolls the page during testing

Solution

1. Step 1: Understand what a full page screenshot means

   A full page screenshot captures the entire webpage, not just the visible part on the screen.

2. Step 2: Compare options with this definition

   Only It captures the entire webpage, including parts not visible on screen correctly states this advantage. Options B, C, and D describe other unrelated behaviors.

3. Final Answer:

   It captures the entire webpage, including parts not visible on screen -> Option C

4. Quick Check:

   Full page screenshot = entire page capture [OK]

Hint: Full page means entire webpage, not just visible part [OK]

Common Mistakes:

• Confusing full page with visible viewport only
• Thinking it speeds up tests automatically
• Assuming it scrolls the page during capture

2. Which Selenium Python method is used to save a full page screenshot in Firefox?

easy

A. driver.get_screenshot_as_file('file.png')

B. driver.save_full_page_screenshot('file.png')

C. driver.save_screenshot('file.png')

D. driver.take_full_screenshot('file.png')

Solution

1. Step 1: Identify the correct method for full page screenshot in Firefox

   Firefox does not have a built-in method named save_full_page_screenshot. The standard method to save a screenshot is get_screenshot_as_file, which captures the visible viewport.

2. Step 2: Check other options for correctness

   driver.save_full_page_screenshot('file.png') is invalid as save_full_page_screenshot is not a standard Selenium method. driver.save_screenshot('file.png') saves visible viewport screenshot. driver.take_full_screenshot('file.png') is not a valid method.

3. Final Answer:

   driver.get_screenshot_as_file('file.png') -> Option A

4. Quick Check:

   Standard screenshot method = get_screenshot_as_file [OK]

Hint: Use get_screenshot_as_file to save screenshot [OK]

Common Mistakes:

• Using non-existent save_full_page_screenshot method
• Confusing save_screenshot with full page capture
• Trying invalid methods like take_full_screenshot

3. Given this code snippet, what will be the result?

driver.get('https://example.com')
driver.save_full_page_screenshot('page.png')
print('Screenshot saved')

medium

A. Runtime error because get_full_page_screenshot_as_file is unsupported

B. Screenshot saved and full page screenshot saved as 'page.png'

C. Only visible part screenshot saved as 'page.png'

D. SyntaxError due to incorrect method name

Solution

1. Step 1: Analyze the method usage

   The method save_full_page_screenshot is not a valid Selenium WebDriver method and will cause a SyntaxError or AttributeError.

2. Step 2: Check the print statement

   The print statement will not execute because the previous line causes an error.

3. Final Answer:

   SyntaxError due to incorrect method name -> Option D

4. Quick Check:

   Invalid method call causes error [OK]

Hint: Invalid method names cause errors [OK]

Common Mistakes:

• Assuming method is supported causing success
• Confusing full page with visible screenshot
• Thinking method name is correct syntax

4. You wrote this code but get a blank screenshot file:

driver.get('https://example.com')
driver.save_screenshot('screen.png')

What is the likely cause?

medium

A. Page did not fully load before screenshot

B. save_screenshot does not save files

C. Method get_full_page_screenshot_as_file is required instead

D. Screenshot file path is invalid

Solution

1. Step 1: Understand why screenshot is blank

   If the page is not fully loaded, the screenshot may capture a blank or incomplete page.

2. Step 2: Evaluate other options

   save_screenshot does save files. Method get_full_page_screenshot_as_file is unrelated to blank screenshot issue. Invalid file path would cause an error, not a blank file.

3. Final Answer:

   Page did not fully load before screenshot -> Option A

4. Quick Check:

   Wait for page load before screenshot [OK]

Hint: Always wait for page load before screenshot [OK]

Common Mistakes:

• Assuming save_screenshot never saves files
• Confusing full page screenshot with blank image issue
• Ignoring page load timing problems

5. How can you ensure a clean full page screenshot in headless Firefox using Selenium Python?

hard

A. Use save_screenshot immediately after driver.get() without waits

B. Scroll manually and take multiple viewport screenshots

C. Use headless mode, wait for page load, then call save_full_page_screenshot

D. Use driver.execute_script to hide elements before screenshot

Solution

1. Step 1: Understand headless mode limitations

   Headless Firefox does not support a built-in full page screenshot method.

2. Step 2: Use manual scrolling and multiple viewport screenshots

   To capture the full page, scroll manually and stitch multiple viewport screenshots.

3. Final Answer:

   Scroll manually and take multiple viewport screenshots -> Option B

4. Quick Check:

   Manual scroll + multiple screenshots = full page capture [OK]

Hint: Manual scrolling needed for full page in headless Firefox [OK]

Common Mistakes:

• Assuming save_full_page_screenshot exists in headless mode
• Taking screenshot immediately without waiting
• Hiding elements unnecessarily before capture