Confirmation alert handling in Selenium Python - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Selenium Python code handling a confirmation alert?

Consider the following Selenium Python code snippet that clicks a button to trigger a confirmation alert, then accepts it. What will be printed?

Selenium Python

from selenium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC

# Assume driver is already initialized and navigated to the page
button = driver.find_element(By.ID, 'confirmBtn')
button.click()

alert = WebDriverWait(driver, 5).until(EC.alert_is_present())
alert.accept()
print('Alert accepted')

A UnhandledAlertException

B Alert accepted

C NoSuchElementException

D TimeoutException

💡 Hint

Think about what happens after the alert is accepted and the print statement runs.

The code waits for the alert to appear, accepts it, then prints 'Alert accepted'. No exceptions occur if the alert is present and handled correctly.

❓ assertion

intermediate

Which assertion correctly verifies the alert text before accepting it?

You want to check that the confirmation alert text is exactly 'Are you sure?' before accepting it. Which assertion is correct?

Selenium Python

alert = driver.switch_to.alert
alert_text = alert.text
# Which assertion below is correct?

A assert alert_text == 'Are you sure?'

B assert alert_text.equals('Are you sure?')

C assert alert.text = 'Are you sure?'

D assert alert_text != 'Are you sure?'

💡 Hint

Remember how to compare strings in Python.

Option A uses the correct equality operator '==' to compare strings in Python. Option A uses assignment '=' which is invalid in assert. Option A uses a method not available on Python strings. Option A asserts the opposite.

❓ locator

advanced

Which locator is best to find a button that triggers a confirmation alert?

You want to locate a button that triggers a confirmation alert. The button has the text 'Delete' and a class 'btn-danger'. Which locator is best practice?

A driver.find_element(By.ID, 'Delete')

B driver.find_element(By.CSS_SELECTOR, "button.btn-danger:contains('Delete')")

C driver.find_element(By.XPATH, "//button[text()='Delete' and contains(@class, 'btn-danger')]")

D driver.find_element(By.CLASS_NAME, 'btn-danger')

💡 Hint

CSS selectors do not support :contains pseudo-class in Selenium.

Option C uses XPath to match button text and class, which is precise. Option C uses a CSS selector with :contains which is not supported in Selenium. Option C uses an ID that does not exist. Option C selects all buttons with class 'btn-danger' but does not check text.

🔧 Debug

advanced

Why does this Selenium code raise UnexpectedAlertPresentException?

Review the code below. It tries to click a button and then get page title. Why does it raise UnexpectedAlertPresentException?

Selenium Python

button = driver.find_element(By.ID, 'confirmBtn')
button.click()
title = driver.title
print(title)

A Because the button ID is incorrect

B Because the click() method is asynchronous and needs wait

C Because driver.title is not a valid property

D Because the confirmation alert is not handled before accessing driver.title

💡 Hint

Think about what happens when an alert is present and you try to interact with the page.

If a confirmation alert appears after clicking the button, Selenium blocks further commands until the alert is handled. Accessing driver.title without accepting or dismissing the alert causes UnexpectedAlertPresentException.

❓ framework

expert

In a pytest Selenium test, how to properly handle confirmation alerts to avoid flaky tests?

You write pytest tests using Selenium. Confirmation alerts appear unpredictably after clicking buttons. Which approach best avoids flaky tests?

A Use explicit waits for alert presence and accept alerts before continuing test steps

B Ignore alerts and catch exceptions when they appear

C Use time.sleep() after clicks to wait for alerts to appear

D Disable alerts in browser settings before tests

💡 Hint

Think about reliable ways to detect alerts instead of guessing with fixed delays.

Explicit waits for alerts ensure the test waits exactly until the alert appears, then handles it. Ignoring alerts or using fixed sleeps causes flaky tests. Disabling alerts may not be possible or realistic.