Clicking with JavaScript in Selenium Python - Build an Automation Script

Automate clicking a button using JavaScript in Selenium

Preconditions (2)

Step 1: Open the browser and navigate to the web page URL 'https://example.com/form'

Step 2: Locate the button element with id 'submit-btn'

Step 3: Use JavaScript to click the button instead of the standard click method

Step 4: Verify that clicking the button triggers the expected action, such as navigation or a message

✅ Expected Result: The button is clicked successfully using JavaScript, and the expected action occurs (e.g., page navigates to 'https://example.com/success')

Automation Requirements - Selenium with Python

Assertions Needed:

Verify the current URL changes to 'https://example.com/success' after clicking the button

Best Practices:

Use explicit waits to ensure the button is present and clickable before executing JavaScript

Use Selenium's execute_script method to perform the JavaScript click

Avoid hardcoded sleeps; rely on WebDriverWait

Use By.ID locator for the button element

Automated Solution

Selenium Python

from selenium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC

# Initialize the Chrome WebDriver
with webdriver.Chrome() as driver:
    driver.get('https://example.com/form')

    # Wait until the button with id 'submit-btn' is present and visible
    wait = WebDriverWait(driver, 10)
    button = wait.until(EC.element_to_be_clickable((By.ID, 'submit-btn')))

    # Use JavaScript to click the button
    driver.execute_script('arguments[0].click();', button)

    # Wait until the URL changes to the expected success page
    wait.until(EC.url_to_be('https://example.com/success'))

    # Assert the URL is correct
    assert driver.current_url == 'https://example.com/success', f"Expected URL to be 'https://example.com/success' but got {driver.current_url}"

This script starts by opening the Chrome browser and navigating to the form page.

It waits explicitly for the button with id 'submit-btn' to be clickable to avoid timing issues.

Instead of using the normal Selenium click, it uses JavaScript's click method via execute_script to click the button. This is useful when the normal click might fail due to overlays or other issues.

After clicking, it waits until the URL changes to the expected success page, ensuring the click triggered the correct action.

Finally, it asserts that the current URL matches the expected URL, confirming the test passed.

Common Mistakes - 3 Pitfalls

Using time.sleep() instead of explicit waits

{'mistake': "Using driver.find_element(By.ID, 'submit-btn').click() when the button is covered or not interactable", 'why_bad': "Selenium's click may fail if the element is hidden or overlapped by another element.", 'correct_approach': 'Use JavaScript click via execute_script to bypass such issues.'}

Hardcoding XPath or CSS selectors that are brittle

Bonus Challenge

Now add data-driven testing with 3 different button IDs to click using JavaScript

Show Hint

Practice

1. What is the main reason to use JavaScript click in Selenium Python instead of the normal click() method?

easy

A. To click elements that are hidden or blocked by other elements

B. To speed up the test execution time

C. To avoid writing locators for elements

D. To automatically wait for elements to load

Solution

1. Step 1: Understand normal click limitations

   Normal click() can fail if an element is hidden or covered by another element.

2. Step 2: Role of JavaScript click

   JavaScript click forces the click event on the element regardless of visibility or blocking.

3. Final Answer:

   To click elements that are hidden or blocked by other elements -> Option A

4. Quick Check:

   JavaScript click handles tricky elements = B [OK]

Hint: Use JS click when normal click fails due to element blocking [OK]

Common Mistakes:

• Thinking JS click speeds up tests
• Believing JS click removes need for locators
• Assuming JS click waits for elements automatically

2. Which of the following is the correct syntax to perform a JavaScript click on a WebElement element in Selenium Python?

easy

A. driver.execute_script('click(arguments[0])', element)

B. driver.execute_script('element.click()')

C. driver.execute_script('arguments[0].click()', element)

D. driver.execute_script('arguments.click(element)')

Solution

1. Step 1: Recall JavaScript click syntax in Selenium

   The correct syntax uses arguments[0].click() and passes the element as an argument.

2. Step 2: Check each option

   Only driver.execute_script('arguments[0].click()', element) correctly uses arguments[0].click() with the element argument.

3. Final Answer:

   driver.execute_script('arguments[0].click()', element) -> Option C

4. Quick Check:

   Correct JS click syntax = A [OK]

Hint: Use arguments[0].click() with element as argument [OK]

Common Mistakes:

• Forgetting to pass the element as argument
• Using element.click() inside script without arguments
• Wrong JavaScript function call syntax

3. Given the following code snippet, what will be the output if the JavaScript click successfully triggers a button that changes the page title to 'Clicked!'?

button = driver.find_element(By.ID, 'btn')
driver.execute_script('arguments[0].click()', button)
print(driver.title)

medium

A. The original page title before clicking

B. Empty string

C. An error because execute_script returns None

D. 'Clicked!'

Solution

1. Step 1: Understand what execute_script does

   It runs JavaScript on the element but returns None by default; it does not affect print output directly.

2. Step 2: Effect of JavaScript click on page title

   The click triggers a change that updates the page title to 'Clicked!'. So driver.title will reflect this new title.

3. Final Answer:

   'Clicked!' -> Option D

4. Quick Check:

   JS click changes title, print shows 'Clicked!' [OK]

Hint: JS click triggers event; check page title after click [OK]

Common Mistakes:

• Expecting execute_script to return click result
• Not realizing page title changes after click
• Confusing print output with script return value

4. You wrote this code to click a button using JavaScript but it throws an error: driver.execute_script('arguments[0].click()', button). What is the most likely cause?

medium

A. execute_script cannot click elements

B. The variable button is not a valid WebElement

C. The JavaScript syntax is incorrect

D. You forgot to import By

Solution

1. Step 1: Check JavaScript syntax

   The syntax arguments[0].click() is correct, so syntax error is unlikely.

2. Step 2: Validate the button variable

   If button is not a WebElement (e.g., None or wrong type), the script will fail.

3. Final Answer:

   The variable button is not a valid WebElement -> Option B

4. Quick Check:

   Invalid element causes JS click error = C [OK]

Hint: Ensure element is found before JS click [OK]

Common Mistakes:

• Assuming JS click syntax is wrong
• Believing execute_script can't click
• Ignoring element locator errors

5. You want to click a button that is inside an iframe and is blocked by a transparent overlay. Which sequence correctly uses JavaScript click in Selenium Python to handle this?

hard

A. Switch to iframe, find button, then use JavaScript click on button

B. Use JavaScript click on button without switching iframe

C. Switch to iframe, use normal click on button ignoring overlay

D. Use normal click on button without switching iframe

Solution

1. Step 1: Switch to the iframe context

   Elements inside iframes require switching to that iframe before interacting.

2. Step 2: Use JavaScript click on the button

   Since the button is blocked by an overlay, normal click may fail; JS click forces the click.

3. Final Answer:

   Switch to iframe, find button, then use JavaScript click on button -> Option A

4. Quick Check:

   Switch iframe + JS click = A [OK]

Hint: Always switch iframe before JS click on inner elements [OK]

Common Mistakes:

• Trying JS click without iframe switch
• Using normal click when overlay blocks element
• Ignoring iframe context requirement