Automation maintenance challenges in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to identify the main cause of flaky tests.

Testing Fundamentals

if test_result == 'intermittent failure':
    cause = '[1]'
else:
    cause = 'stable failure'

Drag options to blanks, or click blank then click option'

Acorrect assertion

Bconsistent network

Cfixed test data

Denvironment instability

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing stable or consistent options that do not cause flakiness.

Flaky tests often happen because the environment is unstable or changes unexpectedly.

2fill in blank

medium

Complete the code to update a locator when the UI changes.

Testing Fundamentals

def update_locator():
    locator = '[1]'
    return locator

Drag options to blanks, or click blank then click option'

A//button[@id='submit']

Bdiv#header

Cbutton.submit-btn

Dinput[type='text']

Attempts:

3 left

💡 Hint

Common Mistakes

Using an id that might change frequently.

Using a CSS class selector like 'button.submit-btn' is a common way to locate a button that may change its id.

3fill in blank

hard

Fix the error in the test code that causes maintenance issues.

Testing Fundamentals

def test_login():
    username = 'user1'
    password = '[1]'
    assert login(username, password) == True

Drag options to blanks, or click blank then click option'

Aenv.get('PASSWORD')

Bhardcoded_password

Cpassword123

D12345

Attempts:

3 left

💡 Hint

Common Mistakes

Hardcoding passwords that may change or cause security risks.

Using environment variables for passwords avoids hardcoding sensitive data and eases maintenance.

4fill in blank

hard

Fill both blanks to create a robust test that handles UI changes and waits for elements.

Testing Fundamentals

def click_button(driver):
    driver.implicitly_wait([2])
    button = driver.find_element_by_[1]('submit-btn')
    button.click()

Drag options to blanks, or click blank then click option'

Acss_selector

Bid

C5

D10

Attempts:

3 left

💡 Hint

Common Mistakes

Using less stable locators or too short wait times.

Using 'id' is a reliable locator, and waiting 10 seconds helps handle slow UI loading.

5fill in blank

hard

Fill both blanks to create a dictionary comprehension that filters test cases by status.

Testing Fundamentals

filtered_tests = {test: status[1] 'passed' for test, status in test_results.items() if status [2] 'passed'}

Drag options to blanks, or click blank then click option'

A:

B==

C!=

D->

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong operators or symbols that break dictionary syntax.

The colon ':' separates key and value in a dictionary, and '==' checks for equality to filter passed tests.

Practice

1. Why is it important to update automated tests when the software changes?

easy

A. Because updating tests slows down the development process

B. Because tests never need updates once created

C. Because outdated tests may fail even if the software works correctly

D. Because automated tests do not depend on software changes

Solution

1. Step 1: Understand the relationship between software and tests

   Automated tests check software behavior, so if software changes, tests must reflect those changes.

2. Step 2: Identify the effect of not updating tests

   If tests are not updated, they may fail incorrectly, causing confusion and wasted effort.

3. Final Answer:

   Because outdated tests may fail even if the software works correctly -> Option C

4. Quick Check:

   Update tests when software changes = Avoid false failures [OK]

Hint: Tests must match software changes to avoid false failures [OK]

Common Mistakes:

• Thinking tests never need updates
• Believing tests run independently of software
• Assuming updates slow development unnecessarily

2. Which of the following is the correct way to write a locator for a button with id 'submitBtn' in Selenium WebDriver?

easy

A. driver.find_element(By.ID, 'submitBtn')

B. driver.find_element_by_id('submitBtn')

C. driver.find_element('id', 'submitBtn')

D. driver.find_element_by_name('submitBtn')

Solution

1. Step 1: Recall the modern Selenium locator syntax

   In recent Selenium versions, locators use By class with find_element(By.ID, 'value').

2. Step 2: Identify the correct syntax among options

   driver.find_element(By.ID, 'submitBtn'): driver.find_element(By.ID, 'submitBtn'), which is correct syntax in Python Selenium.

3. Final Answer:

   driver.find_element(By.ID, 'submitBtn') -> Option A

4. Quick Check:

   Use By.ID with find_element = Correct locator syntax [OK]

Hint: Use By.ID with find_element for correct Selenium locator [OK]

Common Mistakes:

• Using deprecated find_element_by_id method
• Passing locator type as string instead of By class
• Confusing id with name locator

3. Consider this Python test snippet using pytest:

def test_sum():
    a = 2
    b = 3
    assert a + b == 6

What will be the test result when this runs?

medium

A. Test is skipped automatically

B. Test passes successfully

C. Syntax error stops the test

D. Test fails due to wrong assertion

Solution

1. Step 1: Evaluate the assertion logic

   The assertion checks if 2 + 3 equals 6, but 2 + 3 equals 5, so the assertion is false.

2. Step 2: Determine test outcome based on assertion

   Since the assertion is false, pytest will mark the test as failed.

3. Final Answer:

   Test fails due to wrong assertion -> Option D

4. Quick Check:

   2 + 3 != 6 means assertion fails [OK]

Hint: Check assertion math carefully to predict test pass/fail [OK]

Common Mistakes:

• Assuming assertion is true without calculation
• Confusing syntax error with assertion failure
• Thinking test skips without skip decorator

4. You have this Selenium test code snippet:

element = driver.find_element(By.ID, 'login')
element.click()

But the test fails with NoSuchElementException. What is the most likely cause?

medium

A. The driver object is not initialized

B. The element with id 'login' does not exist on the page

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

D. The syntax of find_element is incorrect

Solution

1. Step 1: Understand NoSuchElementException meaning

   This exception means Selenium could not find the element with the given locator on the page.

2. Step 2: Analyze possible causes

   If the element does not exist or is not loaded yet, this error occurs. The syntax and click() method are correct, and driver is assumed initialized.

3. Final Answer:

   The element with id 'login' does not exist on the page -> Option B

4. Quick Check:

   NoSuchElementException = Missing element on page [OK]

Hint: NoSuchElementException means locator found no matching element [OK]

Common Mistakes:

• Blaming click() method for element not found
• Assuming driver is uninitialized without evidence
• Ignoring page load or locator correctness

5. A test automation suite has many flaky tests that fail randomly due to timing issues. Which approach best reduces maintenance effort and improves reliability?

hard

A. Use explicit waits to wait for specific conditions before actions

B. Rewrite all tests in a different programming language

C. Ignore flaky tests and run only stable ones

D. Add fixed long waits (sleep) before every action

Solution

1. Step 1: Understand flaky tests caused by timing

   Flaky tests often fail because the test tries to interact before the page or element is ready.

2. Step 2: Evaluate maintenance-friendly solutions

   Using explicit waits waits only as long as needed for conditions, improving reliability without slowing tests unnecessarily.

3. Step 3: Compare other options

   Fixed long waits slow tests and increase maintenance. Ignoring flaky tests risks missing bugs. Rewriting tests is costly and unrelated to timing issues.

4. Final Answer:

   Use explicit waits to wait for specific conditions before actions -> Option A

5. Quick Check:

   Explicit waits = Reliable, maintainable tests [OK]

Hint: Use explicit waits, not fixed sleeps, to fix flaky tests [OK]

Common Mistakes:

• Using fixed sleeps causing slow, brittle tests
• Ignoring flaky tests instead of fixing
• Thinking rewriting tests solves timing issues