Browser-specific workarounds in Selenium Python - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of browser-specific JavaScript execution in Selenium

What will be the output of the following Selenium Python code snippet when run on Firefox browser?

Selenium Python

from selenium import webdriver
from selenium.webdriver.common.by import By

options = webdriver.FirefoxOptions()
driver = webdriver.Firefox(options=options)
driver.get('data:text/html,<html><body><button id="btn">Click</button></body></html>')

# Firefox requires a workaround for click event
script = "var btn = document.getElementById('btn'); btn.addEventListener('click', function() { window.clicked = true; });"
driver.execute_script(script)
driver.find_element(By.ID, 'btn').click()
clicked = driver.execute_script('return window.clicked === true')
driver.quit()
print(clicked)

A None

B False

C True

D JavascriptException

💡 Hint

Consider how event listeners and click simulation behave differently in Firefox.

The code adds a click event listener to the button that sets window.clicked to true. The Selenium click triggers the event properly in Firefox, so the returned value is True.

❓ assertion

intermediate

Correct assertion for Chrome-specific alert handling

Which assertion correctly verifies that a Chrome browser alert contains the expected text 'Warning!' after triggering it?

Selenium Python

from selenium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.common.alert import Alert

options = webdriver.ChromeOptions()
driver = webdriver.Chrome(options=options)
driver.get('data:text/html,<html><body><script>alert("Warning!");</script></body></html>')
alert = Alert(driver)
alert_text = alert.text

# Which assertion below is correct?

A assert alert_text.equals('Warning!')

B assert alert_text.contains('Warning!')

C assert alert_text is 'Warning!'

D assert alert_text == 'Warning!'

💡 Hint

Check Python string comparison syntax.

In Python, to check string equality, use '==' operator. Methods like contains() or equals() do not exist on Python strings.

🔧 Debug

advanced

Debugging Safari WebDriver click failure

You have this Selenium Python code snippet that works on Chrome but fails on Safari with ElementNotInteractableException when clicking a button. What is the most likely cause?

Selenium Python

from selenium import webdriver
from selenium.webdriver.common.by import By

driver = webdriver.Safari()
driver.get('https://example.com')
button = driver.find_element(By.ID, 'submit')
button.click()

A Safari does not support click() method on buttons

B Safari requires scrolling the element into view before clicking

C The button ID is invalid only in Safari

D Safari WebDriver does not support find_element

💡 Hint

Think about how Safari handles elements not visible on screen.

Safari WebDriver often requires elements to be scrolled into view before interaction. Without scrolling, click() may raise ElementNotInteractableException.

🧠 Conceptual

advanced

Reason for browser-specific workarounds in Selenium tests

Why do Selenium tests often require browser-specific workarounds?

A Different browsers implement WebDriver APIs and JavaScript engines with subtle differences affecting test behavior

B Selenium only supports Chrome fully, other browsers are experimental

C Browsers block Selenium commands by default except Firefox

D All browsers use the same engine, so workarounds are unnecessary

💡 Hint

Consider browser engine and API implementation differences.

Browsers have different JavaScript engines and WebDriver implementations, causing subtle differences that require tailored workarounds.

❓ framework

expert

Best practice for handling browser-specific quirks in Selenium test framework

In a Selenium test framework supporting Chrome, Firefox, and Safari, what is the best way to handle browser-specific workarounds?

A Implement a browser abstraction layer that detects browser type and applies specific fixes transparently

B Write separate test scripts for each browser with duplicated code

C Use only Chrome for testing to avoid browser-specific issues

D Ignore browser differences and rely on Selenium to handle them automatically

💡 Hint

Think about maintainability and code reuse.

A browser abstraction layer centralizes browser-specific fixes, reducing code duplication and improving maintainability.

Practice

1. Why do we need browser-specific workarounds in Selenium tests?

easy

A. Because different browsers may behave differently and need special handling

B. Because Selenium only supports one browser at a time

C. Because browsers do not support JavaScript

D. Because tests run faster on some browsers

Solution

1. Step 1: Understand browser differences

   Browsers like Chrome, Firefox, and Edge can behave differently in how they handle web elements or JavaScript.

2. Step 2: Recognize need for workarounds

   To keep tests reliable, we write special code for each browser to handle these differences.

3. Final Answer:

   Because different browsers may behave differently and need special handling -> Option A

4. Quick Check:

   Browser differences = need workarounds [OK]

Hint: Remember: Different browsers act differently, so adjust tests [OK]

Common Mistakes:

• Thinking Selenium supports only one browser at a time
• Believing all browsers behave exactly the same
• Assuming JavaScript is unsupported in browsers

2. Which is the correct way to detect the browser name in Selenium Python?

easy

A. driver.get_browser_name()

B. driver.getCapabilities('browser')

C. driver.browserName

D. driver.capabilities['browserName']

Solution

1. Step 1: Recall Selenium's capability dictionary

   Selenium stores browser info in driver.capabilities, a dictionary with keys like 'browserName'.

2. Step 2: Identify correct syntax

   Accessing driver.capabilities['browserName'] returns the browser name string correctly.

3. Final Answer:

   driver.capabilities['browserName'] -> Option D

4. Quick Check:

   Use capabilities dictionary for browser name [OK]

Hint: Use driver.capabilities['browserName'] to get browser name [OK]

Common Mistakes:

• Using non-existent methods like get_browser_name()
• Trying to access driver.browserName directly
• Using wrong method names or parameters

3. What will the following code print if the browser is Firefox?

browser = driver.capabilities['browserName']
if browser == 'firefox':
    print('Use Firefox workaround')
else:
    print('Use default code')

medium

A. Use default code

B. Use Firefox workaround

C. KeyError

D. SyntaxError

Solution

1. Step 1: Check browser value

   The variable browser is assigned driver.capabilities['browserName'], which is 'firefox' here.

2. Step 2: Evaluate if condition

   Since browser == 'firefox' is True, the code prints 'Use Firefox workaround'.

3. Final Answer:

   Use Firefox workaround -> Option B

4. Quick Check:

   Browser is 'firefox' so prints Firefox workaround [OK]

Hint: Match browserName string exactly to choose workaround [OK]

Common Mistakes:

• Assuming else branch runs for Firefox
• Confusing case sensitivity in browser name
• Expecting errors when key exists

4. Identify the error in this Selenium Python snippet for browser-specific workaround:

browser = driver.capabilities.browserName
if browser == 'chrome':
    print('Chrome workaround')

medium

A. driver.capabilities is a dictionary, so .browserName is invalid

B. Missing colon after if statement

C. Print statement syntax is wrong

D. No error, code is correct

Solution

1. Step 1: Check how capabilities is accessed

   driver.capabilities is a dictionary, so keys must be accessed with ['key'], not dot notation.

2. Step 2: Identify the error

   Using driver.capabilities.browserName causes an AttributeError because 'dict' has no attribute 'browserName'.

3. Final Answer:

   driver.capabilities is a dictionary, so .browserName is invalid -> Option A

4. Quick Check:

   Use ['browserName'] not .browserName [OK]

Hint: Access capabilities keys with brackets, not dot notation [OK]

Common Mistakes:

• Using dot notation on dictionary objects
• Ignoring Python syntax for dictionary access
• Assuming no error in attribute access

5. You want to run a Selenium test that clicks a button differently on Chrome and Firefox due to a known issue. Which code snippet correctly implements this workaround?

hard

A. driver.find_element(By.ID, 'btn').click() # Works on all browsers without changes

B. if driver.capabilities['browserName'] == 'chrome':
driver.execute_script("arguments[0].click();", driver.find_element(By.ID, 'btn'))
else:
driver.find_element(By.ID, 'btn').click()

C. browser = driver.capabilities['browserName']
if browser == 'chrome':
driver.find_element(By.ID, 'btn').click()
elif browser == 'firefox':
driver.execute_script("arguments[0].click();", driver.find_element(By.ID, 'btn'))

D. browser = driver.capabilities.browserName
if browser == 'firefox':
driver.find_element(By.ID, 'btn').click()
else:
driver.execute_script("arguments[0].click();", driver.find_element(By.ID, 'btn'))

Solution

1. Step 1: Detect browser correctly

   Use driver.capabilities['browserName'] to get the browser name safely.

2. Step 2: Apply browser-specific click

   For Chrome, use normal click(). For Firefox, use JavaScript click workaround to avoid issues.

3. Final Answer:

   Use if-elif with correct browser detection and click methods -> Option C

4. Quick Check:

   Detect browser then apply specific click method [OK]

Hint: Detect browser, then choose click method accordingly [OK]

Common Mistakes:

• Using dot notation on capabilities dictionary
• Applying wrong click method for browser
• Assuming one click method fits all browsers