Page title and URL retrieval in Selenium Python - Deep Dive

Overview - Page title and URL retrieval

What is it?

Page title and URL retrieval means getting the name shown on a browser tab and the web address of the current page using automated tests. This helps testers check if the right page is open during testing. Selenium is a tool that lets you control a web browser with code to do this automatically.

Why it matters

Without checking the page title and URL, tests might miss if the browser opened the wrong page or if navigation failed. This can cause bugs to go unnoticed, leading to broken websites or apps. Retrieving these details ensures the test is on the correct page, making tests reliable and trustworthy.

Where it fits

Before this, you should know how to set up Selenium and open a web page. After learning this, you can move on to interacting with page elements, validating page content, and handling navigation in tests.

Mental Model

Core Idea

Retrieving the page title and URL is like reading the label and address on a package to confirm you have the right one before opening it.

Think of it like...

Imagine you order a book online. When it arrives, you check the title on the cover and the shipping label to make sure it’s the book you wanted. Similarly, in testing, you check the page title and URL to confirm you are on the correct web page.

┌─────────────────────────────┐
│        Browser Window       │
│ ┌─────────────────────────┐ │
│ │ Page Title (Tab Label)  │ │
│ └─────────────────────────┘ │
│                             │
│ URL shown in address bar     │
│                             │
│ Web page content area        │
└─────────────────────────────┘

Build-Up - 7 Steps

1

Foundation

Understanding Page Title and URL

Concept: Learn what page title and URL mean in a web browser context.

The page title is the text shown on the browser tab. The URL is the web address shown in the browser's address bar. Both help identify the current web page.

Result

You can recognize the page title and URL visually in any browser.

Knowing what these two pieces of information represent is essential before automating their retrieval.

2

Foundation

Setting Up Selenium WebDriver

Concept: Learn how to start a browser session using Selenium in Python.

Install Selenium and a browser driver (like ChromeDriver). Write code to open a browser and navigate to a web page.

Result

A browser window opens and loads the specified web page.

Without a running browser session, you cannot retrieve page details programmatically.

3

Intermediate

Retrieving Page Title with Selenium

🤔Before reading on: do you think Selenium returns the page title as a string or an object? Commit to your answer.

Concept: Use Selenium's property to get the page title as a string.

In Selenium Python, use driver.title to get the page title. Example: from selenium import webdriver driver = webdriver.Chrome() driver.get('https://example.com') print(driver.title) driver.quit()

Result

The console prints the page title, e.g., 'Example Domain'.

Understanding that driver.title returns a simple string makes it easy to use in assertions and logs.

4

Intermediate

Retrieving Current URL with Selenium

🤔Before reading on: do you think the current URL changes automatically after navigation or do you need to refresh it manually? Commit to your answer.

Concept: Use Selenium's property to get the current page URL as a string.

In Selenium Python, use driver.current_url to get the current URL. Example: from selenium import webdriver driver = webdriver.Chrome() driver.get('https://example.com') print(driver.current_url) driver.quit()

Result

The console prints the current URL, e.g., 'https://example.com/'.

Knowing driver.current_url updates automatically after navigation helps keep tests accurate.

5

Advanced

Using Title and URL in Assertions

🤔Before reading on: do you think comparing page title and URL in tests is enough to confirm correct page load? Commit to your answer.

Concept: Learn how to write test assertions to verify page title and URL match expected values.

Use assert statements in Python to check if the title and URL are as expected: assert driver.title == 'Example Domain' assert driver.current_url == 'https://example.com/'

Result

Test passes if both assertions are true; fails otherwise.

Using title and URL assertions catches navigation errors early in automated tests.

6

Advanced

Handling Dynamic URLs and Titles

🤔Before reading on: do you think exact string matching always works for page titles and URLs? Commit to your answer.

Concept: Learn strategies to handle pages where titles or URLs change dynamically.

Use partial matching or regular expressions to check if the title or URL contains expected keywords instead of exact matches. Example: assert 'Example' in driver.title assert driver.current_url.startswith('https://example.com')

Result

Tests become more flexible and less brittle when page details vary slightly.

Knowing how to handle dynamic content prevents false test failures.

7

Expert

Performance and Timing Considerations

🤔Before reading on: do you think retrieving title and URL immediately after navigation always gives correct results? Commit to your answer.

Concept: Understand timing issues and how to wait for page load before retrieving title and URL.

Sometimes the page is still loading when you get title or URL, causing wrong values. Use Selenium waits like WebDriverWait to wait until the title or URL meets conditions: from selenium.webdriver.support.ui import WebDriverWait from selenium.webdriver.support import expected_conditions as EC wait = WebDriverWait(driver, 10) wait.until(EC.title_contains('Example')) print(driver.title)

Result

Retrieving title and URL after waits ensures accurate and stable test results.

Understanding timing and waits prevents flaky tests caused by premature retrieval.

Under the Hood

Selenium controls the browser through a driver that communicates with the browser's automation API. When you access driver.title or driver.current_url, Selenium sends commands to the browser to fetch the current page's title and URL from the browser's internal state. This happens over a protocol like WebDriver, which translates your code commands into browser actions and responses.

Why designed this way?

Selenium was designed to mimic real user interactions with browsers remotely and programmatically. Retrieving title and URL directly from the browser's state ensures tests reflect what a user actually sees. Alternatives like parsing HTML source would be less reliable and slower.

┌───────────────┐       ┌───────────────┐       ┌───────────────┐
│ Selenium Test │──────▶│ WebDriver API │──────▶│ Browser Engine│
│   (Python)    │       │ (ChromeDriver) │       │ (Chrome, etc) │
└───────────────┘       └───────────────┘       └───────────────┘
       ▲                      ▲                      ▲
       │                      │                      │
       │ driver.title /        │ fetch title and URL  │
       │ driver.current_url    │                      │
       │                      │                      │
       └──────────────────────────────────────────────┘

Myth Busters - 4 Common Misconceptions

Quick: Does driver.title always return the page title immediately after driver.get()? Commit to yes or no.

Common Belief: driver.title instantly returns the correct page title right after navigation without delay.

Reality: Sometimes the page is still loading, so driver.title may return an old or empty title if accessed too soon.

Why it matters: Tests may fail or pass incorrectly if they check title too early, causing flaky or unreliable results.

Quick: Is driver.current_url always the same as the URL you navigated to? Commit to yes or no.

Common Belief: driver.current_url always matches the URL passed to driver.get().

Reality: The current URL can change due to redirects or JavaScript navigation after loading.

Why it matters: Assuming URLs never change can cause tests to miss navigation errors or unexpected redirects.

Quick: Can you use driver.title and driver.current_url to verify page content? Commit to yes or no.

Common Belief: Checking title and URL is enough to confirm the page content is correct.

Reality: Title and URL only identify the page; they do not guarantee the page content loaded correctly or fully.

Why it matters: Relying only on title and URL can miss content errors, so tests should also check page elements.

Quick: Does driver.title return an object with extra info or just a simple string? Commit to your answer.

Common Belief: driver.title returns a complex object with metadata about the page title.

Reality: driver.title returns a simple string containing only the title text.

Why it matters: Expecting an object can confuse test code and cause errors when using the title.

Expert Zone

1

Page titles can be localized or dynamically generated, so tests must handle multiple expected values or patterns.

2

Some single-page applications change URL fragments or use history API without full reloads, requiring careful URL checks.

3

Browser security policies may restrict access to title or URL in cross-origin frames, affecting test design.

When NOT to use

Do not rely solely on title and URL for verifying page correctness in complex applications. Instead, use element presence, content checks, or API responses for deeper validation.

Production Patterns

In real-world tests, title and URL retrieval is combined with explicit waits and element assertions. Tests often use partial matching or regex for titles and URLs to handle dynamic content and localization.

Connections

Assertions in Automated Testing

Builds-on

Knowing how to retrieve page title and URL enables writing assertions that confirm navigation success and page correctness.

WebDriver Waits and Synchronization

Builds-on

Understanding timing issues with title and URL retrieval connects directly to using waits to avoid flaky tests.

Human Visual Verification

Opposite

Automated retrieval of title and URL replaces manual checking by testers, speeding up testing and reducing human error.

Common Pitfalls

#1 Accessing driver.title immediately after driver.get() without waiting.

Wrong approach:

driver.get('https://example.com')
print(driver.title) # May print empty or old title

Correct approach:

from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC

wait = WebDriverWait(driver, 10)
driver.get('https://example.com')
wait.until(EC.title_contains('Example'))
print(driver.title)

Root cause:

Misunderstanding that page loading is asynchronous and title may not be ready immediately.

#2 Assuming driver.current_url always equals the URL passed to driver.get().

Wrong approach:

driver.get('http://short.url')
assert driver.current_url == 'http://short.url' # Fails if redirected

Correct approach:

driver.get('http://short.url')
actual_url = driver.current_url
assert actual_url.startswith('http://expecteddomain.com')

Root cause:

Ignoring that redirects or JavaScript can change the URL after navigation.

#3 Using exact string match for dynamic page titles or URLs.

Wrong approach:

assert driver.title == 'Welcome User 12345' # Fails if user ID changes

Correct approach:

assert driver.title.startswith('Welcome User') # Flexible check

Root cause:

Not accounting for dynamic or variable parts in titles or URLs.

Key Takeaways

Page title and URL retrieval lets automated tests confirm the browser is on the correct page.

Selenium provides simple properties driver.title and driver.current_url to get these values as strings.

Always wait for the page to load before retrieving title or URL to avoid flaky tests.

Use flexible matching for dynamic titles or URLs to make tests robust.

Title and URL checks are necessary but not sufficient; combine with content checks for full validation.