Element screenshots in Selenium Java - Test Execution Trace

Test Overview

This test opens a webpage, finds a specific element, takes a screenshot of that element, and verifies the screenshot file is created successfully.

Test Code - JUnit with Selenium WebDriver

Selenium Java

import org.openqa.selenium.By;
import org.openqa.selenium.OutputType;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
import org.openqa.selenium.chrome.ChromeDriver;
import org.openqa.selenium.io.FileHandler;
import org.junit.jupiter.api.AfterEach;
import org.junit.jupiter.api.BeforeEach;
import org.junit.jupiter.api.Test;
import java.io.File;
import java.io.IOException;
import static org.junit.jupiter.api.Assertions.assertTrue;

public class ElementScreenshotTest {
    WebDriver driver;

    @BeforeEach
    public void setUp() {
        driver = new ChromeDriver();
    }

    @Test
    public void testElementScreenshot() throws IOException {
        driver.get("https://example.com");
        WebElement element = driver.findElement(By.cssSelector("h1"));
        File screenshot = element.getScreenshotAs(OutputType.FILE);
        File destination = new File("element_screenshot.png");
        FileHandler.copy(screenshot, destination);
        assertTrue(destination.exists() && destination.length() > 0, "Screenshot file should exist and not be empty");
    }

    @AfterEach
    public void tearDown() {
        if (driver != null) {
            driver.quit();
        }
    }
}

Execution Trace - 6 Steps

Step	Action	System State	Assertion	Result
1	Test starts and Chrome browser opens	Chrome browser window is open and ready	—	PASS
2	Navigates to https://example.com	Browser displays the Example Domain webpage	—	PASS
3	Finds the <h1> element using CSS selector 'h1'	The <h1> element with text 'Example Domain' is located	Element is found without exception	PASS
4	Takes screenshot of the <h1> element	Screenshot file of the element is created in memory	—	PASS
5	Saves the screenshot file as 'element_screenshot.png'	File 'element_screenshot.png' is saved on disk	File exists and file size > 0 bytes	PASS
6	Test ends and browser closes	Browser window is closed	—	PASS

Failure Scenario

Failing Condition: The element with CSS selector 'h1' is not found on the page

Execution Trace Quiz - 3 Questions

What does the test verify after saving the element screenshot?

A That the screenshot file exists and is not empty

B That the entire page screenshot is saved

C That the element is clickable

D That the browser title matches expected

Key Result

Always verify that the element exists before taking a screenshot and confirm the screenshot file is saved and not empty to ensure the test validity.

Practice

1. What is the main purpose of taking an element screenshot in Selenium Java?

easy

A. To record user interactions on the webpage

B. To capture the entire webpage including all elements

C. To capture only a specific part of the webpage for focused testing

D. To speed up the browser loading time

Solution

1. Step 1: Understand element screenshot concept

   Element screenshots capture only the selected element, not the whole page.

2. Step 2: Compare with other screenshot types

   Full page screenshots capture everything, but element screenshots focus on one part.

3. Final Answer:

   To capture only a specific part of the webpage for focused testing -> Option C

4. Quick Check:

   Element screenshot = focused capture [OK]

Hint: Element screenshots capture one element, not whole page [OK]

Common Mistakes:

• Confusing element screenshot with full page screenshot
• Thinking it records user actions
• Assuming it improves browser speed

2. Which Selenium Java method is used to capture a screenshot of a specific WebElement?

easy

A. takeScreenshot()

B. getScreenshotAs(OutputType.FILE)

C. captureElement()

D. saveScreenshot()

Solution

1. Step 1: Identify the correct method for element screenshot

   The WebElement interface provides getScreenshotAs(OutputType.FILE) to capture its screenshot.

2. Step 2: Verify other options

   Methods like takeScreenshot(), captureElement(), saveScreenshot() do not exist in Selenium Java API.

3. Final Answer:

   getScreenshotAs(OutputType.FILE) -> Option B

4. Quick Check:

   WebElement.getScreenshotAs = correct method [OK]

Hint: Use getScreenshotAs on WebElement for element screenshot [OK]

Common Mistakes:

• Using driver.getScreenshotAs instead of element.getScreenshotAs
• Choosing non-existent method names
• Confusing with full page screenshot methods

3. What will happen if you run the following Selenium Java code snippet?

WebElement logo = driver.findElement(By.id("logo"));
File screenshot = logo.getScreenshotAs(OutputType.FILE);
System.out.println(screenshot.exists());

medium

A. Prints true if the screenshot file is saved successfully

B. Prints false because getScreenshotAs returns null

C. Throws NoSuchElementException at runtime

D. Prints the file path as a string

Solution

1. Step 1: Understand getScreenshotAs behavior

   getScreenshotAs(OutputType.FILE) saves the element screenshot as a temporary file and returns a File object.

2. Step 2: Check what screenshot.exists() returns

   exists() returns true if the file exists on disk, which it should after saving.

3. Final Answer:

   Prints true if the screenshot file is saved successfully -> Option A

4. Quick Check:

   File.exists() = true after screenshot saved [OK]

Hint: getScreenshotAs returns a File; check exists() to confirm [OK]

Common Mistakes:

• Assuming getScreenshotAs returns null
• Expecting file path string instead of File object
• Ignoring possibility of NoSuchElementException if element missing

4. Identify the error in this Selenium Java code snippet for taking an element screenshot:

WebElement button = driver.findElement(By.name("submit"));
File screenshot = button.getScreenshotAs(OutputType.FILE);
FileUtils.copyFile(screenshot, new File("button.png"));

medium

A. Missing import for FileUtils causes compilation error

B. getScreenshotAs method is called on driver instead of element

C. By.name locator is invalid for buttons

D. FileUtils.copyFile requires IOException handling

Solution

1. Step 1: Check method calls and imports

   getScreenshotAs is correctly called on the element; By.name is valid; FileUtils is commonly used from Apache Commons IO.

2. Step 2: Identify exception handling issue

   FileUtils.copyFile throws IOException which must be handled or declared, missing here causes compile error.

3. Final Answer:

   FileUtils.copyFile requires IOException handling -> Option D

4. Quick Check:

   copyFile needs try/catch or throws [OK]

Hint: copyFile throws IOException; handle it with try/catch [OK]

Common Mistakes:

• Assuming missing import causes error without checking
• Confusing driver and element method calls
• Thinking By.name is invalid locator

5. You want to capture screenshots of multiple elements on a page and save them with unique names. Which approach correctly implements this in Selenium Java?

List<WebElement> items = driver.findElements(By.className("product"));
int count = 1;
for (WebElement item : items) {
    File src = item.getScreenshotAs(OutputType.FILE);
    File dest = new File("product_" + count + ".png");
    FileUtils.copyFile(src, dest);
    count++;
}

hard

A. This code works but needs exception handling for copyFile

B. getScreenshotAs cannot be used in a loop for multiple elements

C. File names must be generated before the loop to avoid overwriting

D. driver.findElements returns only one element, so loop is unnecessary

Solution

1. Step 1: Analyze the loop and screenshot logic

   The code loops over elements, takes screenshots, and saves with unique names using count variable.

2. Step 2: Identify missing exception handling

   FileUtils.copyFile throws IOException which must be handled; otherwise code is correct.

3. Final Answer:

   This code works but needs exception handling for copyFile -> Option A

4. Quick Check:

   Loop + getScreenshotAs + unique names = correct, handle exceptions [OK]

Hint: Use loop with count for unique names; handle IOException [OK]

Common Mistakes:

• Thinking getScreenshotAs can't be used multiple times
• Not incrementing count causing file overwrite
• Misunderstanding findElements returns multiple elements