Drag and drop in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the result of this drag and drop Selenium code?

Consider the following Selenium Java code snippet that performs a drag and drop action. What will be the output if the drag and drop is successful?

Selenium Java

WebElement source = driver.findElement(By.id("drag-source"));
WebElement target = driver.findElement(By.id("drop-target"));
Actions actions = new Actions(driver);
actions.dragAndDrop(source, target).perform();
System.out.println(target.getText());

A The text of the target element after the drag and drop, reflecting the dropped item

B The text of the source element before drag and drop

C An exception is thrown because dragAndDrop requires clickAndHold

D The text of the target element remains unchanged

💡 Hint

Think about what happens to the target element's text after a successful drag and drop.

The dragAndDrop method moves the source element onto the target. After performing, the target's text usually changes to reflect the dropped item. So printing target.getText() shows the updated text.

❓ locator

intermediate

Which locator is best for identifying draggable and droppable elements?

You want to automate drag and drop in Selenium Java. Which locator strategy is best practice for identifying the source and target elements?

A By.id("drag-source") and By.id("drop-target")

B By.xpath("//div[@class='draggable']") and By.xpath("//div[@class='droppable']")

C By.className("drag") and By.className("drop")

D By.cssSelector("div:nth-child(1)") and By.cssSelector("div:nth-child(2)")

💡 Hint

IDs are unique and fastest to locate.

Using By.id is best because IDs are unique, fast, and reliable locators. XPath and class names can be less stable or slower. CSS nth-child is fragile and depends on page structure.

❓ assertion

advanced

Which assertion correctly verifies a successful drag and drop?

After performing drag and drop, you want to assert that the target element contains the text "Dropped!". Which assertion is correct in JUnit?

A assertNull(target.getText());

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

C assertFalse(target.getText().equals("Dropped!"));

D assertEquals("Dropped!", target.getText());

💡 Hint

You want to check exact text equality.

assertEquals checks that the target's text exactly matches "Dropped!" which confirms success. assertTrue with contains is less strict. assertFalse and assertNull are incorrect here.

🔧 Debug

advanced

Why does this drag and drop code fail with ElementNotInteractableException?

Given this code snippet, the drag and drop fails with ElementNotInteractableException. What is the most likely cause?

Selenium Java

WebElement source = driver.findElement(By.id("drag-source"));
WebElement target = driver.findElement(By.id("drop-target"));
Actions actions = new Actions(driver);
actions.clickAndHold(source).moveToElement(target).release().perform();

A The target element locator is incorrect causing NoSuchElementException

B The source element is not visible or not enabled for interaction

C The Actions class does not support clickAndHold method

D The perform() method is missing at the end

💡 Hint

ElementNotInteractableException means element cannot be interacted with currently.

This exception usually means the source element is hidden, disabled, or overlapped, so Selenium cannot interact with it. The locator is found, Actions supports clickAndHold, and perform() is present.

❓ framework

expert

In a Selenium Java test framework, where should drag and drop logic be placed for best design?

You are designing a Selenium Java test framework. Where is the best place to put the drag and drop code for reusability and maintainability?

A Directly inside the test method where drag and drop is needed

B Inside a utility/helper class with static methods for drag and drop

C Inside the Page Object class representing the page containing draggable elements

D In the main method of the test suite class

💡 Hint

Think about the Page Object Model design pattern.

Placing drag and drop logic inside the Page Object class keeps tests clean and encapsulates page behavior. Utility classes are less ideal for actions tied to specific pages. Test methods and main methods should not contain detailed UI interaction code.