Authentication testing in Testing Fundamentals - Framework Patterns

Framework Mode - Authentication testing

Folder Structure for Authentication Testing Framework

authentication-testing-project/
├── tests/
│   ├── login_tests/
│   │   ├── test_valid_login.py
│   │   ├── test_invalid_login.py
│   │   └── test_password_reset.py
│   ├── logout_tests/
│   │   └── test_logout.py
│   └── setup_tests.py
├── pages/
│   ├── login_page.py
│   ├── dashboard_page.py
│   └── reset_password_page.py
├── utils/
│   ├── helpers.py
│   ├── validators.py
│   └── data_generator.py
├── config/
│   ├── config.yaml
│   └── credentials.yaml
├── reports/
│   └── latest_report.html
├── conftest.py
└── README.md

Test Framework Layers

• Test Layer: Contains test scripts that verify authentication features like login, logout, and password reset. These tests use assertions to check expected outcomes.
• Page Object Layer: Encapsulates web page elements and actions for login, dashboard, and reset password pages. This keeps tests clean and easy to maintain.
• Utility Layer: Provides helper functions such as input validators, test data generators, and common utilities to support tests.
• Configuration Layer: Holds environment settings, browser options, and user credentials securely separated from code.
• Reporting Layer: Generates readable test reports and integrates with CI/CD pipelines for automated feedback.

Configuration Patterns

• Environment Config: Use a config.yaml file to define URLs for dev, staging, and production environments. Tests read this file to know where to run.
• Credentials Management: Store usernames and passwords in a separate credentials.yaml file, not hardcoded in tests, to keep secrets safe and easy to update.
• Browser Settings: Define browser type and options in config to allow running tests on different browsers without code changes.
• Fixture Setup: Use conftest.py to initialize browser sessions and load config before tests run, ensuring consistent setup and teardown.

Test Reporting and CI/CD Integration

• Generate HTML or XML reports after test runs to show which authentication tests passed or failed.
• Integrate with CI/CD tools like Jenkins, GitHub Actions, or GitLab CI to run tests automatically on code changes.
• Configure notifications (email or chat) to alert the team immediately if authentication tests fail.
• Keep historical reports in the reports/ folder for tracking test stability over time.

Best Practices for Authentication Testing Framework

1. Use Page Object Model: Separate page details from tests to make maintenance easier when UI changes.
2. Keep Credentials Secure: Never hardcode passwords in tests; use encrypted or environment-based secrets.
3. Test Both Positive and Negative Cases: Verify valid logins succeed and invalid attempts fail with proper messages.
4. Use Explicit Waits: Wait for page elements to load before interacting to avoid flaky tests.
5. Isolate Tests: Each test should run independently to avoid side effects between login and logout tests.

Self-Check Question

Where in this folder structure would you add a new page object for a "Multi-Factor Authentication" page?

Key Result

Organize authentication tests using clear layers: page objects, tests, utilities, config, and reporting for maintainability and security.

Practice

1. What is the main goal of authentication testing in software testing?

easy

A. To verify that only valid users can access the system

B. To check the speed of the application

C. To test the user interface design

D. To validate database connections

Solution

1. Step 1: Understand authentication testing purpose

   Authentication testing focuses on verifying user identity before granting access.

2. Step 2: Compare options with this purpose

   Only To verify that only valid users can access the system matches this goal; others relate to different testing areas.

3. Final Answer:

   To verify that only valid users can access the system -> Option A

4. Quick Check:

   Authentication testing = verify valid users [OK]

Hint: Authentication = check valid user access [OK]

Common Mistakes:

• Confusing authentication with performance testing
• Thinking authentication tests UI elements
• Mixing authentication with database testing

2. Which of the following is the correct way to test a login form's authentication feature?

easy

A. Enter valid username and password, then check for successful login

B. Click random buttons without entering data

C. Only check if the login button is visible

D. Test the color of the login page background

Solution

1. Step 1: Identify valid test steps for authentication

   Testing authentication requires entering valid credentials and verifying access.

2. Step 2: Evaluate options for correctness

   Enter valid username and password, then check for successful login correctly describes this; others do not test authentication properly.

3. Final Answer:

   Enter valid username and password, then check for successful login -> Option A

4. Quick Check:

   Valid credentials test = successful login [OK]

Hint: Test with valid credentials for login success [OK]

Common Mistakes:

• Ignoring input fields and clicking randomly
• Testing only UI elements without input
• Confusing visual checks with authentication tests

3. Consider this test case for authentication:

Input: username='user1', password='wrongpass'
Expected: Login fails with error message 'Invalid credentials'

What will be the test result if the system allows login with these credentials?

medium

A. Test passes if error message is shown

B. Test passes because login is successful

C. Test is inconclusive without more data

D. Test fails because login should not succeed

Solution

1. Step 1: Analyze expected vs actual behavior

   The test expects login failure with an error message for wrong password.

2. Step 2: Compare actual system behavior

   If login succeeds with wrong password, it contradicts expected behavior, causing test failure.

3. Final Answer:

   Test fails because login should not succeed -> Option D

4. Quick Check:

   Wrong password login = test fail [OK]

Hint: Wrong password must fail login [OK]

Common Mistakes:

• Assuming any login success means pass
• Ignoring expected error messages
• Confusing test pass/fail logic

4. You wrote this test script for authentication:

def test_login():
    username = 'admin'
    password = 'admin123'
    result = login(username, password)
    assert result == False

What is the error in this test?

medium

A. The password variable is empty

B. The username variable is not defined

C. The assertion expects login to fail but credentials are valid

D. The login function is missing parentheses

Solution

1. Step 1: Understand test intent and data

   Username and password appear valid, so login should succeed (True).

2. Step 2: Check assertion correctness

   Assertion expects False (failure), which contradicts valid credentials, causing test error.

3. Final Answer:

   The assertion expects login to fail but credentials are valid -> Option C

4. Quick Check:

   Valid credentials expect True, not False [OK]

Hint: Match assertion with expected login result [OK]

Common Mistakes:

• Asserting wrong expected result
• Assuming variables undefined without checking
• Confusing function call syntax

5. You want to test a system that locks a user account after 3 failed login attempts. Which test case best verifies this feature?

hard

A. Login once with correct password and check access

B. Attempt login 3 times with wrong password, then check if account is locked

C. Try logging in with empty username and password

D. Check if password reset link is visible on login page

Solution

1. Step 1: Identify feature to test

   The feature locks account after 3 failed login attempts.

2. Step 2: Select test case matching feature

   Attempt login 3 times with wrong password, then check if account is locked tests exactly this by failing login 3 times and checking lock status.

3. Final Answer:

   Attempt login 3 times with wrong password, then check if account is locked -> Option B

4. Quick Check:

   3 failed attempts = account lock test [OK]

Hint: Test lock by 3 failed logins [OK]

Common Mistakes:

• Testing unrelated features like password reset
• Using correct password instead of failed attempts
• Ignoring the number of failed attempts