Element screenshots in Selenium Java - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is an element screenshot in Selenium?

An element screenshot captures only a specific web element on the page, not the entire page. It helps focus on the part you want to test or verify visually.

beginner

Which Selenium interface allows taking a screenshot of a web element?

The WebElement interface has a method called getScreenshotAs() that captures the screenshot of that element.

beginner

Why use element screenshots instead of full page screenshots?

Element screenshots are smaller, faster to capture, and focus on the exact part you want to check. This reduces noise and makes tests clearer.

intermediate

How do you save an element screenshot to a file in Selenium Java?

You call getScreenshotAs(OutputType.FILE) on the element, then copy the file to your desired location using Java file utilities.

beginner

What is a common use case for element screenshots in testing?

They are used to verify visual correctness of buttons, images, or sections after changes, or to capture evidence of bugs in specific UI parts.

Which method captures a screenshot of a specific web element in Selenium Java?

A captureElement() on WebElement

B getScreenshotAs() on WebDriver

C getScreenshotAs() on WebElement

D takeScreenshot() on WebDriver

The getScreenshotAs() method on the WebElement interface captures the screenshot of that element only.

What type of object does getScreenshotAs(OutputType.FILE) return?

A A BufferedImage

B A File object

C A String path

D A byte array

It returns a File object representing the screenshot image file.

Why might you prefer element screenshots over full page screenshots?

A They are faster and focus on the needed part

B They capture the entire page

C They require more memory

D They are harder to save

Element screenshots are faster and focus only on the element you want to check.

Which Selenium interface provides the getScreenshotAs() method for elements?

A WebElement

B WebDriver

C TakesScreenshot

D RemoteWebDriver

The WebElement interface provides getScreenshotAs() to capture element screenshots.

What is a typical file format for element screenshots saved by Selenium?

A TXT

B CSV

C DOCX

D PNG

Selenium saves screenshots as PNG image files by default.

Explain how to capture and save a screenshot of a specific web element using Selenium Java.

Think about the WebElement interface and Java file handling.

Describe why element screenshots are useful in automated testing compared to full page screenshots.

Consider test clarity and performance.

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