Automation maintenance challenges in Testing Fundamentals - Framework Patterns

Framework Mode - Automation maintenance challenges

Folder Structure for Automation Framework

automation-framework/
├── tests/
│   ├── login_tests.py
│   ├── checkout_tests.py
│   └── user_profile_tests.py
├── pages/
│   ├── login_page.py
│   ├── checkout_page.py
│   └── user_profile_page.py
├── utils/
│   ├── helpers.py
│   ├── wait_utils.py
│   └── logger.py
├── config/
│   ├── config.yaml
│   └── credentials.yaml
├── reports/
│   └── latest_report.html
├── conftest.py
└── README.md
  

Test Framework Layers

• Test Layer: Contains test scripts that use page objects to perform actions and assertions.
• Page Object Layer: Encapsulates UI elements and interactions for each page or component.
• Utility Layer: Helper functions for waits, logging, data handling, and common tasks.
• Configuration Layer: Stores environment settings, credentials, and test parameters.
• Reporting Layer: Generates test execution reports and logs for analysis.

Configuration Patterns

Use separate files for different environments (e.g., dev, staging, production) in config/. Use YAML or JSON format for easy reading and editing.

Store sensitive data like usernames and passwords in encrypted files or environment variables, not hardcoded in tests.

Use a conftest.py or similar setup file to load configurations and provide fixtures for tests.

Example snippet from config.yaml:

environment: staging
browser: chrome
base_url: https://staging.example.com
credentials:
  username: user_staging
  password: pass_staging
  

Test Reporting and CI/CD Integration

• Generate HTML or XML reports after test runs for clear pass/fail results.
• Include screenshots on failure to help diagnose issues quickly.
• Integrate with CI/CD tools (e.g., Jenkins, GitHub Actions) to run tests automatically on code changes.
• Use notifications (email, Slack) to alert the team about test results.

Best Practices for Automation Maintenance

1. Use Page Object Model: Keeps UI locators and actions in one place to reduce duplication and ease updates.
2. Write Clear, Small Tests: Tests should focus on one feature or behavior to isolate failures.
3. Implement Robust Locators: Use stable locators like data-test-id attributes instead of brittle ones like XPath with indexes.
4. Regularly Review and Refactor: Update tests and page objects when the application changes to avoid broken tests.
5. Use Explicit Waits: Avoid flaky tests by waiting for elements to be ready before interacting.

Self Check Question

Where in this folder structure would you add a new page object for the "Settings" page?

Key Result

Organize tests with clear layers and maintainable code to reduce automation maintenance challenges.

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