Click actions in Selenium Python - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Selenium click action code?

Consider the following Selenium Python code snippet that tries to click a button. What will be printed after execution?

Selenium Python

from selenium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.chrome.service import Service
from selenium.common.exceptions import ElementClickInterceptedException

service = Service('/path/to/chromedriver')
driver = webdriver.Chrome(service=service)
driver.get('https://example.com')

try:
    button = driver.find_element(By.ID, 'submit-btn')
    button.click()
    print('Clicked successfully')
except ElementClickInterceptedException:
    print('Click intercepted')
finally:
    driver.quit()

A Clicked successfully

B Click intercepted

C NoSuchElementException error

D TimeoutException error

💡 Hint

The button with ID 'submit-btn' exists and is clickable on the page.

The code finds the button by its ID and clicks it. Since the button is clickable and no interception occurs, the try block succeeds and prints 'Clicked successfully'.

❓ locator

intermediate

Which locator is best for clicking a button with text 'Submit'?

You want to click a button on a webpage that displays the visible text 'Submit'. Which locator strategy is the best to find this button reliably?

A driver.find_element(By.XPATH, "//button[text()='Submit']")

B driver.find_element(By.CSS_SELECTOR, "button:contains('Submit')")

C driver.find_element(By.ID, 'submit')

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

💡 Hint

The button has no ID or class attributes, only visible text.

XPath with exact text match is the best way to locate a button by visible text. CSS selector :contains() is not supported in Selenium. ID or class may not exist or be unreliable.

❓ assertion

advanced

Which assertion correctly verifies a button was clicked?

After clicking a button, the page shows a message with id 'msg' containing text 'Success'. Which assertion correctly checks this?

Selenium Python

message = driver.find_element(By.ID, 'msg').text

A assert message == 'Success'

B assert 'Success' in message

C assert message != ''

D assert message is not None

💡 Hint

The message text may contain extra spaces or other text around 'Success'.

Using 'in' checks if 'Success' is anywhere in the message, making the assertion more flexible and less brittle than exact equality.

🔧 Debug

advanced

Why does this Selenium click action raise ElementNotInteractableException?

This code tries to click a button but raises ElementNotInteractableException. What is the most likely cause?

Selenium Python

button = driver.find_element(By.ID, 'hidden-btn')
button.click()

A The button ID is incorrect and element not found

B The click method is deprecated and should not be used

C The driver is not initialized properly

D The button is present but not visible or disabled on the page

💡 Hint

ElementNotInteractableException means the element cannot be clicked because it is hidden or disabled.

The exception occurs when the element is in the DOM but not visible or interactable, such as hidden by CSS or disabled.

❓ framework

expert

Which pytest fixture setup is best for reusable Selenium click tests?

You want to write multiple Selenium tests that click buttons on a webpage. Which pytest fixture setup ensures the browser opens once per test and closes after?

A

@pytest.fixture(scope='session')
def driver():
    driver = webdriver.Chrome()
    yield driver
    driver.quit()

B

@pytest.fixture(scope='module')
def driver():
    driver = webdriver.Chrome()
    yield driver
    driver.quit()

C

@pytest.fixture(scope='function')
def driver():
    driver = webdriver.Chrome()
    yield driver
    driver.quit()

D

@pytest.fixture(scope='class')
def driver():
    driver = webdriver.Chrome()
    yield driver
    driver.quit()

💡 Hint

Each test should start with a fresh browser instance to avoid state issues.

Using function scope means the driver is created and destroyed for each test function, ensuring isolation and no leftover state.