Element dimensions and location in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of getSize() method?

Consider the following Selenium Java code snippet:

WebElement element = driver.findElement(By.id("sample"));
Dimension size = element.getSize();
System.out.println(size.getWidth() + "," + size.getHeight());

Assuming the element's width is 150 pixels and height is 75 pixels, what will be printed?

Selenium Java

WebElement element = driver.findElement(By.id("sample"));
Dimension size = element.getSize();
System.out.println(size.getWidth() + "," + size.getHeight());

A 150,75

B 75,150

C Size(width=150, height=75)

D Width:150 Height:75

💡 Hint

getWidth() returns the width in pixels, getHeight() returns the height in pixels.

The getSize() method returns a Dimension object. Calling getWidth() and getHeight() returns integer values for width and height respectively. The code concatenates them with a comma, so the output is '150,75'.

❓ assertion

intermediate

Which assertion correctly verifies element location?

You want to verify that a web element is located at x=200 and y=100 on the page. Which assertion correctly checks this using Selenium Java?

Selenium Java

WebElement element = driver.findElement(By.id("locationElement"));
Point location = element.getLocation();

A assertTrue(location.getX() == 100 && location.getY() == 200);

B assertEquals(200, location.getX()); assertEquals(100, location.getY());

C assertEquals(new Point(100, 200), location);

D assertNotNull(location);

💡 Hint

Check the x and y coordinates separately with expected values.

The element's x coordinate should be 200 and y coordinate 100. Option B correctly asserts these values separately. Option B swaps x and y. Option B swaps x and y in Point. Option B only checks non-null, not coordinates.

❓ locator

advanced

Which locator best ensures stable element location for dimension checks?

You need to locate a button whose position and size you want to test. The button has dynamic classes but a stable aria-label attribute 'Submit Form'. Which locator is best for stable element dimension and location testing?

A By.className("btn-primary")

B By.xpath("//button[contains(@class, 'btn')]")

C By.cssSelector("button[aria-label='Submit Form']")

D By.id("submitBtn")

💡 Hint

Choose locator that is stable and unique for the element.

Option C uses a stable attribute 'aria-label' which is less likely to change and uniquely identifies the button. Option C and C rely on classes which are dynamic. Option C assumes an id which may not exist.

🔧 Debug

advanced

Why does getLocation() return (0,0) unexpectedly?

You run this code:

WebElement element = driver.findElement(By.id("hiddenElement"));
Point location = element.getLocation();
System.out.println(location.getX() + "," + location.getY());

The output is '0,0' but you expect different coordinates. What is the most likely reason?

A The driver has a bug and always returns (0,0) for getLocation().

B The element's id is incorrect, so getLocation() returns (0,0).

C The element is not visible or is hidden, so location defaults to (0,0).

D The element is inside an iframe and getLocation() returns (0,0) without switching frames.

💡 Hint

Check if the element is inside an iframe or frame.

If the element is inside an iframe, Selenium must switch to that iframe before accessing element properties. Without switching, getLocation() returns (0,0). Option D is incorrect because hidden elements still have location. Option D would cause NoSuchElementException. Option D is false.

❓ framework

expert

How to design a reusable test method for verifying element size and location?

You want to create a reusable Java method in your Selenium test framework that verifies an element's width, height, x, and y coordinates against expected values. Which method signature and assertion approach is best?

A

public void verifyElementDimensions(WebElement element, int expectedWidth, int expectedHeight, int expectedX, int expectedY) {
  Dimension size = element.getSize();
  Point location = element.getLocation();
  assertEquals(expectedWidth, size.getWidth());
  assertEquals(expectedHeight, size.getHeight());
  assertEquals(expectedX, location.getX());
  assertEquals(expectedY, location.getY());
}

B

public boolean verifyElementDimensions(WebElement element, int width, int height, int x, int y) {
  return element.getSize().getWidth() == width && element.getSize().getHeight() == height && element.getLocation().getX() == x && element.getLocation().getY() == y;
}

C

public void verifyElementDimensions(WebElement element, Dimension expectedSize, Point expectedLocation) {
  assertTrue(element.getSize().equals(expectedSize) && element.getLocation().equals(expectedLocation));
}

D

public void verifyElementDimensions(WebElement element, int width, int height) {
  Dimension size = element.getSize();
  assertEquals(width, size.getWidth());
  assertEquals(height, size.getHeight());
}

💡 Hint

Include all four parameters and assert each separately for clear failure messages.

Option A provides a clear method with separate assertions for width, height, x, and y, making failures easy to diagnose. Option A returns boolean but does not assert, losing test reporting benefits. Option A uses equals on Dimension and Point which may be less clear and harder to debug. Option A ignores location coordinates.