Action chain execution (perform) in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Selenium Java code snippet?

Consider the following Selenium Java code that performs a double-click action on a web element. What will be the result of executing this code?

Selenium Java

WebElement button = driver.findElement(By.id("submitBtn"));
Actions actions = new Actions(driver);
actions.doubleClick(button).perform();
System.out.println("Action performed");

A The button is double-clicked and "Action performed" is printed

B The button is clicked once and "Action performed" is printed

C No action is performed and a NoSuchElementException is thrown

D The code throws an IllegalStateException because perform() is missing

💡 Hint

Remember that perform() executes the built action chain.

The doubleClick() method prepares a double-click action on the specified element. Calling perform() executes it. So the button is double-clicked and the print statement runs.

❓ assertion

intermediate

Which assertion correctly verifies that a drag-and-drop action was successful?

After performing a drag-and-drop action using Selenium Actions, which assertion best confirms the drop was successful?

Selenium Java

WebElement source = driver.findElement(By.id("dragItem"));
WebElement target = driver.findElement(By.id("dropArea"));
Actions actions = new Actions(driver);
actions.dragAndDrop(source, target).perform();

A assertTrue(target.getText().contains("Dropped!"));

B assertEquals(source.getText(), "Dropped!");

C assertNull(source);

D assertFalse(target.isDisplayed());

💡 Hint

Check the target element's text or state after drop.

After drag-and-drop, the target element usually updates its text or state. Verifying the target's text contains "Dropped!" confirms success.

🔧 Debug

advanced

Why does this action chain fail to execute the intended click?

Review the code below. The intention is to move to an element and click it. Why does the click not happen?

Selenium Java

WebElement menu = driver.findElement(By.id("menu"));
Actions actions = new Actions(driver);
actions.moveToElement(menu);
actions.click();
// Missing perform() call

A Because <code>click()</code> must be chained directly after <code>moveToElement()</code>

B Because <code>perform()</code> is not called, the actions are not executed

C Because the element locator is incorrect and throws NoSuchElementException

D Because <code>build()</code> must be called before <code>perform()</code>

💡 Hint

Check if the action chain is executed.

Actions are only executed when perform() is called. Without it, the chain is built but not run, so no click happens.

🧠 Conceptual

advanced

What is the role of the perform() method in Selenium Actions?

Choose the best description of what perform() does in an Actions chain.

A <code>perform()</code> builds the action chain but does not execute it

B <code>perform()</code> only validates the action chain syntax

C <code>perform()</code> resets the action chain to empty

D <code>perform()</code> executes all the actions built in the chain in sequence

💡 Hint

Think about when the actions actually happen.

The perform() method triggers the execution of all actions that were added to the chain. Without it, no actions run.

❓ framework

expert

In a Selenium test framework, how should you handle multiple chained actions to ensure reliable execution?

When chaining multiple actions like move, click, and sendKeys in Selenium, which practice ensures the chain executes reliably without stale element or timing issues?

A Call <code>perform()</code> after each individual action in the chain

B Use <code>build()</code> without <code>perform()</code> to prepare the chain

C Build the entire chain and call <code>perform()</code> once at the end

D Avoid chaining and perform each action separately with waits in between

💡 Hint

Consider how chaining and execution timing affect element state.

Building the full chain and calling perform() once executes all actions atomically, reducing timing issues. Calling perform() multiple times breaks the chain and may cause stale element errors.