Why element interaction drives test scenarios in Selenium Python - Automation Benefits in Action

Verify login functionality by interacting with input fields and buttons

Preconditions (2)

Step 1: Enter '[e-mail]' in the email input field

Step 2: Enter 'Password123' in the password input field

Step 3: Click the login button

Step 4: Wait for the dashboard page to load

✅ Expected Result: User is redirected to the dashboard page with URL containing '/dashboard' and a welcome message is displayed

Automation Requirements - Selenium with Python

Assertions Needed:

Verify the URL contains '/dashboard' after login

Verify the welcome message element is visible on the dashboard page

Best Practices:

Use explicit waits to wait for elements to be interactable

Use meaningful locators like By.ID or By.NAME instead of brittle XPath

Separate page interactions into functions or page objects for clarity

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


def test_login_functionality():
    driver = webdriver.Chrome()
    driver.get('https://example.com/login')

    wait = WebDriverWait(driver, 10)

    # Wait for email input to be visible and enter email
    email_input = wait.until(EC.visibility_of_element_located((By.ID, 'email')))
    email_input.clear()
    email_input.send_keys('[e-mail]')

    # Wait for password input to be visible and enter password
    password_input = wait.until(EC.visibility_of_element_located((By.ID, 'password')))
    password_input.clear()
    password_input.send_keys('Password123')

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

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

    # Verify welcome message is visible
    welcome_message = wait.until(EC.visibility_of_element_located((By.ID, 'welcomeMsg')))
    assert welcome_message.is_displayed(), 'Welcome message is not displayed'

    driver.quit()

This test script uses Selenium WebDriver with Python to automate the login scenario.

First, it opens the login page URL.

It uses explicit waits to wait for the email and password input fields to be visible before interacting with them. This ensures the elements are ready for input.

It clears any existing text and enters the provided credentials.

Then it waits for the login button to be clickable before clicking it, ensuring the button is ready to receive the click.

After clicking, it waits for the URL to contain '/dashboard' to confirm navigation to the dashboard page.

Finally, it waits for the welcome message element to be visible and asserts it is displayed, confirming successful login.

Using explicit waits and meaningful locators makes the test reliable and easy to maintain.

Common Mistakes - 3 Pitfalls

{'mistake': 'Using time.sleep() instead of explicit waits', 'why_bad': 'It causes tests to wait unnecessarily long or fail if the element loads slower or faster than expected.', 'correct_approach': "Use Selenium's explicit waits like WebDriverWait with expected_conditions to wait only as long as needed."}

Using brittle XPath locators that break easily

Not clearing input fields before sending keys

Bonus Challenge

Now add data-driven testing with 3 different sets of login credentials (valid and invalid) to verify login behavior.

Show Hint

Practice

1. Why is interacting with elements like clicking or typing important in Selenium test scenarios?

easy

A. Because it automatically fixes bugs in the application

B. Because it speeds up the test execution time

C. Because it reduces the number of test cases needed

D. Because it simulates real user actions to verify website behavior

Solution

1. Step 1: Understand the purpose of element interaction

   Interacting with elements like clicking or typing simulates what a real user does on a website.

2. Step 2: Connect interaction to test verification

   This simulation helps verify if the website behaves correctly when users perform actions.

3. Final Answer:

   Because it simulates real user actions to verify website behavior -> Option D

4. Quick Check:

   Element interaction = Simulate user actions [OK]

Hint: Think: tests mimic what users do on the site [OK]

Common Mistakes:

• Confusing interaction with speeding tests
• Believing interaction reduces test cases
• Assuming interaction fixes bugs automatically

2. Which of the following is the correct way to click a button with id 'submit' using Selenium in Python?

easy

A. driver.find_element_by_id('submit').click()

B. driver.find_element(By.ID, 'submit').click()

C. driver.find_element(By.id='submit').click()

D. driver.find_element(By.id, submit).click()

Solution

1. Step 1: Identify correct syntax for find_element

   In Selenium Python 4+, use driver.find_element(By.ID, 'value') with By imported.

2. Step 2: Check method call and parameters

   driver.find_element(By.ID, 'submit').click() uses correct syntax: By.ID and string 'submit'. driver.find_element_by_id('submit').click() uses deprecated method. driver.find_element(By.id='submit').click() has wrong parameter format. driver.find_element(By.id, submit).click() misses quotes around 'submit'.

3. Final Answer:

   driver.find_element(By.ID, 'submit').click() -> Option B

4. Quick Check:

   Correct syntax = driver.find_element(By.ID, 'submit').click() [OK]

Hint: Use By.ID with string in find_element [OK]

Common Mistakes:

• Using deprecated find_element_by_id method
• Missing quotes around id value
• Wrong parameter format in find_element

3. What will be the output of the following Selenium Python code snippet?

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

button = WebDriverWait(driver, 10).until(
    EC.element_to_be_clickable((By.ID, 'login-btn'))
)
button.click()
print('Clicked')

medium

A. Throws TimeoutException immediately

B. Prints 'Clicked' without clicking the button

C. Prints 'Clicked' after clicking the button if clickable

D. SyntaxError due to wrong import

Solution

1. Step 1: Analyze WebDriverWait usage

   The code waits up to 10 seconds for the element with id 'login-btn' to be clickable.

2. Step 2: Understand click and print behavior

   If clickable, it clicks the button and prints 'Clicked'. No syntax errors or immediate exceptions expected.

3. Final Answer:

   Prints 'Clicked' after clicking the button if clickable -> Option C

4. Quick Check:

   Wait for clickable then click = prints 'Clicked' [OK]

Hint: Wait ensures clickable before click, then prints [OK]

Common Mistakes:

• Assuming immediate TimeoutException without wait
• Thinking print runs before click
• Confusing import statements as errors

4. You wrote this Selenium code to click a button:

button = driver.find_element(By.ID, 'submit-btn')
button.click()

But the test fails with ElementNotInteractableException. What is the likely cause?

medium

A. The button is hidden or disabled and cannot be clicked

B. The locator By.ID is incorrect syntax

C. The click() method is not supported on buttons

D. The driver object is not initialized

Solution

1. Step 1: Understand ElementNotInteractableException meaning

   This exception means the element is found but cannot be interacted with, often because it is hidden or disabled.

2. Step 2: Evaluate other options

   By.ID syntax is correct, click() works on buttons, and if driver was not initialized, a different error would occur.

3. Final Answer:

   The button is hidden or disabled and cannot be clicked -> Option A

4. Quick Check:

   ElementNotInteractable = element not clickable [OK]

Hint: ElementNotInteractable means element is hidden or disabled [OK]

Common Mistakes:

• Confusing locator syntax with interaction errors
• Thinking click() is unsupported on buttons
• Assuming driver not initialized causes this error

5. You want to write a test scenario that types 'hello' into a text box only if it is visible and enabled. Which Selenium Python code snippet correctly achieves this?

hard

A. input_box = driver.find_element(By.ID, 'input')
if input_box.is_displayed() and input_box.is_enabled():
input_box.send_keys('hello')

B. input_box = driver.find_element(By.ID, 'input')
input_box.send_keys('hello')

C. input_box = driver.find_element(By.ID, 'input')
if input_box.is_displayed() or input_box.is_enabled():
input_box.send_keys('hello')

D. input_box = driver.find_element(By.ID, 'input')
if not input_box.is_displayed() and not input_box.is_enabled():
input_box.send_keys('hello')

Solution

1. Step 1: Check conditions for safe typing

   We must ensure the input box is both visible (is_displayed) and enabled (is_enabled) before typing.

2. Step 2: Analyze each option's condition

   input_box = driver.find_element(By.ID, 'input') if input_box.is_displayed() and input_box.is_enabled(): input_box.send_keys('hello') uses 'and' correctly. input_box = driver.find_element(By.ID, 'input') input_box.send_keys('hello') types without checks. input_box = driver.find_element(By.ID, 'input') if input_box.is_displayed() or input_box.is_enabled(): input_box.send_keys('hello') uses 'or' which allows typing if only one condition is true. input_box = driver.find_element(By.ID, 'input') if not input_box.is_displayed() and not input_box.is_enabled(): input_box.send_keys('hello') types only if both are false, which is wrong.

3. Final Answer:

   input_box = driver.find_element(By.ID, 'input') if input_box.is_displayed() and input_box.is_enabled(): input_box.send_keys('hello') -> Option A

4. Quick Check:

   Use 'and' to check visible and enabled before typing [OK]

Hint: Check both visible and enabled with 'and' before send_keys [OK]

Common Mistakes:

• Using 'or' instead of 'and' for conditions
• Skipping visibility and enabled checks
• Typing when element is hidden or disabled