Why element location is the core skill in Selenium Python - Automation Benefits in Action

Verify login button is clickable on the login page

Preconditions (1)

Step 1: Locate the login button using its id 'loginBtn'

Step 2: Click the login button

Step 3: Verify that the next page URL contains '/dashboard'

✅ Expected Result: Login button is found and clicked successfully, and user is redirected to the dashboard page

Automation Requirements - Selenium with Python

Assertions Needed:

Verify login button is present and clickable

Verify URL after click contains '/dashboard'

Best Practices:

Use explicit waits to wait for element presence and clickability

Use By.ID locator for stable element location

Avoid hardcoded sleeps

Handle exceptions if element not found

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

# Setup WebDriver
with webdriver.Chrome() as driver:
    driver.get('https://example.com/login')

    wait = WebDriverWait(driver, 10)

    # Wait for login button to be clickable
    login_button = wait.until(EC.element_to_be_clickable((By.ID, 'loginBtn')))

    # Click the login button
    login_button.click()

    # Wait for URL to contain '/dashboard'
    wait.until(EC.url_contains('/dashboard'))

    # Assert URL contains '/dashboard'
    assert '/dashboard' in driver.current_url, f"Expected '/dashboard' in URL but got {driver.current_url}"

This script uses Selenium WebDriver with Python to automate the manual test case.

First, it opens the login page URL.

Then it waits explicitly for the login button to be clickable using WebDriverWait and expected_conditions. This avoids timing issues.

It locates the button by its stable id='loginBtn', which is a best practice for element location.

After clicking the button, it waits until the URL contains '/dashboard' to confirm navigation.

Finally, it asserts the URL contains '/dashboard' to verify the expected result.

This approach shows why locating elements correctly and waiting for them is core to reliable test automation.

Common Mistakes - 3 Pitfalls

Using time.sleep() instead of explicit waits

Using brittle locators like absolute XPath

Not handling element not found exceptions

Bonus Challenge

Now add data-driven testing with 3 different login button IDs to verify the button is clickable for each.

Show Hint

Practice

1. Why is locating elements considered the core skill in Selenium testing?

easy

A. Because it allows interaction with web page elements to perform tests

B. Because it speeds up the browser loading time

C. Because it automatically fixes broken links on the page

D. Because it generates test reports without coding

Solution

1. Step 1: Understand the role of element location

   Locating elements is essential to interact with buttons, inputs, and other page parts during testing.

2. Step 2: Identify why this is core

   Without locating elements, tests cannot simulate user actions or verify page behavior.

3. Final Answer:

   Because it allows interaction with web page elements to perform tests -> Option A

4. Quick Check:

   Element location = core for interaction [OK]

Hint: Remember: No element location, no interaction [OK]

Common Mistakes:

• Thinking element location speeds up browser loading
• Believing it fixes broken links automatically
• Assuming it generates reports without code

2. Which of the following is the correct syntax to locate an element by its ID in Selenium Python?

easy

A. driver.find_element(By.ID, "username")

B. driver.find_element_by_id("username")

C. driver.findElement(By.id("username"))

D. driver.find_element(By.Name, "username")

Solution

1. Step 1: Recall the modern Selenium Python syntax

   Since Selenium 4, the recommended syntax uses find_element(By.ID, "value").

2. Step 2: Identify the correct method and locator

   driver.find_element(By.ID, "username") uses By.ID correctly with find_element.

3. Final Answer:

   driver.find_element(By.ID, "username") -> Option A

4. Quick Check:

   Use find_element(By.ID, ...) [OK]

Hint: Use By.ID with find_element, not old methods [OK]

Common Mistakes:

• Using deprecated find_element_by_id method
• Mixing Java syntax like findElement
• Using wrong locator type like By.Name for ID

3. What will be the output of this Selenium Python code snippet if the element with ID 'submit' is not found?

try:
    button = driver.find_element(By.ID, "submit")
    print("Button found")
except NoSuchElementException:
    print("Button not found")

medium

A. Button found

B. SyntaxError

C. No output, script stops

D. Button not found

Solution

1. Step 1: Understand exception handling in Selenium

   If the element is missing, NoSuchElementException is raised and caught by the except block.

2. Step 2: Identify printed output

   The except block prints "Button not found" when the element is missing.

3. Final Answer:

   Button not found -> Option D

4. Quick Check:

   Missing element triggers except print [OK]

Hint: Missing element triggers except block print [OK]

Common Mistakes:

• Assuming script stops without output
• Expecting 'Button found' when element is missing
• Confusing exception type or syntax

4. Identify the error in this Selenium Python code snippet:

element = driver.find_element(By.id, "login")
element.click()

medium

A. Missing import for By class

B. click() method does not exist

C. Incorrect locator syntax: should be By.ID, not By.id

D. No error, code is correct

Solution

1. Step 1: Check locator case sensitivity

   Locator constants like By.ID are case-sensitive and must be uppercase.

2. Step 2: Confirm correct usage

   Using By.id causes an AttributeError; correct is By.ID.

3. Final Answer:

   Incorrect locator syntax: should be By.ID, not By.id -> Option C

4. Quick Check:

   Locator constants are uppercase [OK]

Hint: Locator constants like By.ID are uppercase [OK]

Common Mistakes:

• Using lowercase locator constants
• Assuming click() method is missing
• Forgetting to import By (not tested here)

5. You want to write a reliable Selenium test that clicks a button with dynamic ID that changes every page load. Which locator strategy is best to locate this button?

hard

A. Locate by full dynamic ID using exact match

B. Locate by XPath using partial attribute match or stable text

C. Locate by CSS selector using tag name only

D. Locate by class name assuming it is unique

Solution

1. Step 1: Understand dynamic IDs problem

   Dynamic IDs change every load, so exact match locators fail often.

2. Step 2: Choose locator that handles dynamic parts

   XPath with partial attribute match (e.g., contains()) or stable visible text is more reliable.

3. Step 3: Evaluate other options

   Tag name alone is too broad; class name may not be unique; exact ID match fails due to dynamics.

4. Final Answer:

   Locate by XPath using partial attribute match or stable text -> Option B

5. Quick Check:

   Use partial XPath for dynamic IDs [OK]

Hint: Use partial XPath or stable text for dynamic IDs [OK]

Common Mistakes:

• Using exact dynamic ID match
• Relying on tag name only
• Assuming class name is always unique