Page title and URL retrieval in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Selenium Java code snippet?

Consider the following Selenium WebDriver code that opens a webpage and retrieves its title and URL. What will be printed to the console?

Selenium Java

WebDriver driver = new ChromeDriver();
driver.get("https://example.com");
String title = driver.getTitle();
String url = driver.getCurrentUrl();
System.out.println(title + " - " + url);
driver.quit();

A Example Domain - https://example.com

B https://example.com - Example Domain

C null - null

D Throws NoSuchElementException

💡 Hint

Remember that getTitle() returns the page title and getCurrentUrl() returns the current URL loaded in the browser.

The code navigates to https://example.com, whose page title is "Example Domain". The getTitle() method returns this title, and getCurrentUrl() returns the URL. The output concatenates these with " - ".

❓ assertion

intermediate

Which assertion correctly verifies the page title in Selenium Java?

You want to verify that the page title is exactly "Welcome Page" after loading the page. Which assertion is correct?

Selenium Java

WebDriver driver = new ChromeDriver();
driver.get("https://mysite.com/welcome");
String actualTitle = driver.getTitle();

A assertTrue(actualTitle.contains("Welcome Page"));

B assertFalse(actualTitle.isEmpty());

C assertNotNull(actualTitle);

D assertEquals("Welcome Page", actualTitle);

💡 Hint

You want to check exact equality, not just presence or non-null.

assertEquals(expected, actual) checks that the actual title exactly matches "Welcome Page". Other options check partial or non-null conditions but do not verify exact match.

❓ locator

advanced

Identify the best locator to verify the current URL contains a specific path

You want to write a test that verifies the current URL contains the path "/dashboard" after login. Which Selenium Java code snippet correctly retrieves the URL for this check?

A String url = driver.findElement(By.id("url")).getText();

B String url = driver.getCurrentUrl();

C String url = driver.getTitle();

D String url = driver.getPageSource();

💡 Hint

The URL is not an element on the page but a property of the browser.

getCurrentUrl() returns the current page URL loaded in the browser. Using findElement or getTitle does not retrieve the URL. getPageSource returns HTML source, not URL.

🔧 Debug

advanced

Why does this Selenium Java test fail to get the page title?

Examine the code below. The test throws a NullPointerException when trying to get the title. What is the most likely cause?

Selenium Java

WebDriver driver;
driver.get("https://example.com");
String title = driver.getTitle();
System.out.println(title);

A driver was never initialized with a browser instance

B getTitle() method is deprecated and throws exception

C The URL https://example.com is unreachable

D Missing driver.quit() causes NullPointerException

💡 Hint

Check if the WebDriver object is assigned before use.

The driver variable is declared but never assigned a new browser instance like new ChromeDriver(). Calling methods on a null driver causes NullPointerException.

❓ framework

expert

In a Selenium Java test framework, which method is best to retrieve and log page title and URL after each test?

You want to automatically log the page title and URL after every test method runs in your Selenium Java test suite using TestNG. Which approach is best?

A Use @BeforeClass annotated method to log title and URL before tests run

B Call driver.getTitle() and driver.getCurrentUrl() inside every @Test method manually

C Use @AfterMethod annotated method to call driver.getTitle() and driver.getCurrentUrl() and log them

D Use a static block to log title and URL once when class loads

💡 Hint

Think about running code after each test method automatically.

@AfterMethod runs after each @Test method, making it ideal to retrieve and log page title and URL after every test. Calling inside each test is repetitive. @BeforeClass runs once before all tests. Static block runs once when class loads.