Action chains in Selenium Python - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Selenium ActionChains code?

Consider the following Selenium Python code snippet using ActionChains. What will be printed after execution?

Selenium Python

from selenium.webdriver import ActionChains
from selenium.webdriver.common.by import By
from selenium.webdriver.remote.webelement import WebElement

class DummyDriver:
    def __init__(self):
        self.actions = []
    def find_element(self, by, value):
        return WebElement(None, 'dummy')

class DummyActionChains(ActionChains):
    def __init__(self, driver):
        super().__init__(driver)
        self.actions = []
    def click(self, on_element=None):
        self.actions.append(f"click on {on_element}")
        return self
    def move_to_element(self, to_element):
        self.actions.append(f"move to {to_element}")
        return self
    def perform(self):
        print(self.actions)

# Using dummy classes to simulate

driver = DummyDriver()
actions = DummyActionChains(driver)
element1 = driver.find_element(By.ID, "btn1")
element2 = driver.find_element(By.ID, "btn2")

actions.move_to_element(element1).click().move_to_element(element2).click().perform()

A ["move to <selenium.webdriver.remote.webelement.WebElement object at ...>", "click on None", "move to <selenium.webdriver.remote.webelement.WebElement object at ...>", "click on <selenium.webdriver.remote.webelement.WebElement object at ...>"]

B ["move to <selenium.webdriver.remote.webelement.WebElement object at ...>", "click on <selenium.webdriver.remote.webelement.WebElement object at ...>", "move to <selenium.webdriver.remote.webelement.WebElement object at ...>", "click on None"]

C ["move to <selenium.webdriver.remote.webelement.WebElement object at ...>", "click on <selenium.webdriver.remote.webelement.WebElement object at ...>", "move to <selenium.webdriver.remote.webelement.WebElement object at ...>", "click on <selenium.webdriver.remote.webelement.WebElement object at ...>"]

D ["move to <selenium.webdriver.remote.webelement.WebElement object at ...>", "click on None", "move to <selenium.webdriver.remote.webelement.WebElement object at ...>", "click on None"]

💡 Hint

Look carefully at how the click() method is called without arguments after move_to_element().

The click() method is called without arguments, so it clicks at the current mouse position, not on a specific element. The move_to_element() moves the mouse to the element, but click() receives None as the on_element argument, so it records 'click on None'.

❓ assertion

intermediate

Which assertion correctly verifies a double-click action was performed?

You have a Selenium test that performs a double-click on an element using ActionChains. Which assertion correctly verifies that the double-click was performed by checking the element's text changed to 'Double Clicked'?

Selenium Python

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

# Assume driver and element are already defined

actions = ActionChains(driver)
actions.double_click(element).perform()

# Now verify the text changed
actual_text = element.text

A assert actual_text == 'Double Clicked'

B assert actual_text != 'Double Clicked'

C assert 'Double Clicked' in actual_text

D assert actual_text is None

💡 Hint

The test expects the text to exactly match 'Double Clicked' after the action.

The assertion should check that the actual text equals the expected string exactly, confirming the double-click triggered the expected change.

🔧 Debug

advanced

Why does this ActionChains drag_and_drop code fail to move the element?

This Selenium Python code attempts to drag an element to a target but the element does not move. What is the most likely reason?

Selenium Python

from selenium.webdriver import ActionChains

source = driver.find_element(By.ID, 'source')
target = driver.find_element(By.ID, 'target')
actions = ActionChains(driver)
actions.drag_and_drop(source, target)
# Missing perform call here

A The source element is not visible on the page

B The target element is disabled and cannot receive drops

C The perform() method was not called to execute the action chain

D The drag_and_drop method requires an offset argument

💡 Hint

ActionChains methods build the action but do not execute until perform() is called.

Without calling perform(), the built action chain is not executed, so the drag and drop does not happen.

❓ locator

advanced

Which locator strategy is best for stable ActionChains interaction?

You want to use ActionChains to hover over a menu item that may change position but has a unique visible text 'Settings'. Which locator is best to find this element reliably?

A By.CLASS_NAME, "menu-item"

B By.XPATH, "//li[text()='Settings']"

C By.ID, "menu-item-3"

D By.CSS_SELECTOR, "li:nth-child(3)"

💡 Hint

Choose a locator that depends on visible text, not position or class that may be shared.

Using XPath with exact text match ensures the element is found by its visible label, making the test more stable against layout changes.

❓ framework

expert

How to best integrate ActionChains in a pytest Selenium test for reusability?

You want to write reusable pytest fixtures and helper functions to perform common ActionChains like hover and drag-and-drop. Which approach is best practice?

A Create pytest fixtures that return ActionChains instances and helper functions that accept driver and elements to perform actions, then call perform() inside helpers

B Write all ActionChains code directly inside each test function without helpers or fixtures

C Use global variables to store ActionChains objects and reuse them across tests without reinitializing

D Create a base test class with static methods for ActionChains and inherit it in all test classes

💡 Hint

Think about modularity, reusability, and pytest best practices.

Using pytest fixtures and helper functions promotes clean, reusable code and proper resource management. Calling perform() inside helpers ensures actions execute immediately.