Transitioning to automation in Testing Fundamentals - Framework Patterns

Framework Mode - Transitioning to automation

Folder Structure for Automation Framework

automation-framework/
├── tests/                 # Automated test scripts
│   ├── login_tests/       # Tests for login features
│   ├── checkout_tests/    # Tests for checkout process
│   └── ...
├── pages/                 # Page objects representing UI pages
│   ├── login_page.py
│   ├── home_page.py
│   └── ...
├── utils/                 # Helper functions and utilities
│   ├── browser_manager.py
│   ├── data_loader.py
│   └── ...
├── config/                # Configuration files
│   ├── config.yaml        # Environment and browser settings
│   └── credentials.yaml   # Secure test credentials
├── reports/               # Test execution reports
├── conftest.py            # Test setup and fixtures (for Pytest)
└── README.md              # Project overview and instructions
  

Test Framework Layers

• Test Scripts Layer: Contains automated test cases that verify application behavior.
• Page Object Layer: Represents UI pages as objects with methods to interact with page elements.
• Utilities Layer: Helper functions for browser control, data handling, waits, and logging.
• Configuration Layer: Holds environment settings, browser choices, and sensitive data like credentials.
• Reporting Layer: Generates readable test reports and logs after test runs.

Configuration Patterns

Use separate config files for different environments (e.g., dev, staging, production). Use YAML or JSON files to store settings like URLs, browser types, and timeouts.

Example config.yaml:

environment: staging
base_url: "https://staging.example.com"
browser: chrome
implicit_wait: 10
  

Use environment variables or encrypted files for sensitive data like usernames and passwords.

Load configs at test startup to keep tests flexible and easy to run in different setups.

Test Reporting and CI/CD Integration

• Generate clear test reports showing passed, failed, and skipped tests with details.
• Use tools like Allure, HTMLTestRunner, or built-in Pytest reports for easy reading.
• Integrate tests into CI/CD pipelines (e.g., GitHub Actions, Jenkins) to run tests automatically on code changes.
• Send notifications on test results to the team via email or chat tools.

Best Practices for Transitioning to Automation

1. Start Small: Automate simple, stable test cases first to build confidence.
2. Use Page Object Model: Separate test logic from UI details for easier maintenance.
3. Keep Tests Independent: Each test should run alone without relying on others.
4. Use Clear Naming: Name tests and files clearly to understand their purpose quickly.
5. Regularly Review and Refactor: Keep the framework clean and up to date as the app changes.

Self Check

Where in this framework structure would you add a new page object for the "User Profile" page?

Key Result

Organize automation with clear layers: tests, page objects, utilities, config, and reporting for maintainable and scalable testing.

Practice

1. Why is automation testing preferred for repeated test cases?

easy

A. Because it requires more manual effort

B. Because it cannot be reused

C. Because it is slower than manual testing

D. Because it runs tests quickly and without human error

Solution

1. Step 1: Understand the nature of repeated tests

   Repeated tests are often boring and time-consuming when done manually.

2. Step 2: Identify benefits of automation for repeated tests

   Automation runs tests quickly and consistently without human mistakes.

3. Final Answer:

   Because it runs tests quickly and without human error -> Option D

4. Quick Check:

   Automation speeds up repeated tests = B [OK]

Hint: Automation is best for fast, error-free repeated tests [OK]

Common Mistakes:

• Thinking automation needs more manual work
• Believing automation is slower than manual testing
• Assuming automation cannot be reused

2. Which of the following is the correct way to start an automation script in Python?

easy

A. def test_function():\n assert True

B. function test_function() { assert true; }

C. test_function() => { assert true }

D. start test_function() { assert true }

Solution

1. Step 1: Identify correct Python function syntax

   Python functions start with 'def' followed by the function name and parentheses.

2. Step 2: Check the options for Python syntax

   def test_function():\n assert True uses 'def' and a colon, which is correct Python syntax.

3. Final Answer:

   def test_function():\n assert True -> Option A

4. Quick Check:

   Python functions start with def = D [OK]

Hint: Python functions start with 'def' keyword and colon [OK]

Common Mistakes:

• Using JavaScript or other language syntax in Python
• Missing colon after function definition
• Incorrect arrow function syntax in Python

3. What will be the output of this Python test script?

def test_sum():
    total = 0
    for i in range(3):
        total += i
    assert total == 3

medium

A. SyntaxError occurs

B. Test passes successfully

C. AssertionError occurs

D. Test is skipped

Solution

1. Step 1: Calculate the sum in the loop

   Loop runs i=0,1,2; total starts at 0, then adds 0+1+2 resulting in 3.

2. Step 2: Verify the assertion total == 3

   total = 0+1+2 = 3, so assertion total == 3 is True, no error.

3. Final Answer:

   Test passes successfully -> Option B

4. Quick Check:

   Sum 0+1+2=3, assertion true = C [OK]

Hint: Sum range(3) is 0+1+2=3, so assertion passes [OK]

Common Mistakes:

• Miscounting the sum of range(3)
• Assuming assertion fails without calculation
• Confusing syntax error with logic error

4. Identify the error in this automation test snippet:

def test_login():
    username = "user"
    password = "pass"
    assert username = "user"

medium

A. Using single equals '=' instead of '==' in assertion

B. Missing parentheses in assert statement

C. Incorrect variable names

D. Password variable is unused

Solution

1. Step 1: Check the assertion syntax

   In Python, '=' is assignment, '==' is comparison. Assertion needs '==' to compare.

2. Step 2: Identify the error type

   Using '=' in assert causes SyntaxError because assignment is not allowed there.

3. Final Answer:

   Using single equals '=' instead of '==' in assertion -> Option A

4. Quick Check:

   Assertions need '==' for comparison = A [OK]

Hint: Use '==' in assert, not '=' [OK]

Common Mistakes:

• Confusing assignment '=' with comparison '=='
• Ignoring syntax errors in assert statements
• Thinking unused variables cause assertion errors

5. You want to automate a test that runs daily and checks if a website's homepage loads correctly. Which approach is best to start your automation?

hard

A. Manually check the homepage daily instead of automating

B. Write a complex script that tests every link on the homepage before scheduling

C. Write a simple script that opens the homepage and checks the title, then schedule it to run daily

D. Automate only after the website has no changes for a month

Solution

1. Step 1: Choose a simple test to automate first

   Starting with a simple script to check the homepage title is easy and effective.

2. Step 2: Schedule the script for daily runs

   Scheduling the script automates the daily check without manual effort.

3. Final Answer:

   Write a simple script that opens the homepage and checks the title, then schedule it to run daily -> Option C

4. Quick Check:

   Start simple and schedule = A [OK]

Hint: Start with simple checks before adding complexity [OK]

Common Mistakes:

• Trying to automate too many things at once
• Ignoring automation benefits and doing manual checks
• Waiting too long to start automation