Test data management in Testing Fundamentals - Framework Patterns

Framework Mode - Test data management

Folder Structure for Test Data Management

  test-data-management-project/
  ├── tests/
  │   ├── test_login.py
  │   ├── test_checkout.py
  │   └── test_user_profile.py
  ├── testdata/
  │   ├── users.json
  │   ├── products.csv
  │   └── orders.yaml
  ├── utils/
  │   └── data_loader.py
  ├── config/
  │   └── environments.yaml
  ├── conftest.py
  └── README.md
  

Test Framework Layers for Test Data Management

• Test Data Layer: Stores test data files (JSON, CSV, YAML) in testdata/ folder for easy access and maintenance.
• Data Access Utilities: Functions or classes in utils/data_loader.py to read and parse test data files into usable objects.
• Test Layer: Test scripts in tests/ folder that use data loaded from the test data layer to run tests.
• Configuration Layer: Environment settings and credentials stored in config/environments.yaml to separate data from code.
• Fixtures/Setup: conftest.py defines fixtures to provide test data to tests dynamically.

Configuration Patterns for Test Data Management

• Environment-specific Data: Use separate sections or files for different environments (dev, test, prod) in config/environments.yaml.
• Centralized Data Access: Create utility functions to load data by key or file name, so tests do not handle file parsing directly.
• Data Versioning: Keep test data files under version control to track changes and maintain history.
• Secure Sensitive Data: Store credentials or sensitive info encrypted or use environment variables referenced in config files.
• Data Refresh Strategy: Define when and how test data is reset or refreshed to keep tests reliable and independent.

Test Reporting and CI/CD Integration

• Include test data usage details in test reports to help understand which data sets were tested.
• Automate test data setup and cleanup in CI/CD pipelines to ensure consistent test environments.
• Use logs to capture data loading errors or mismatches for easier debugging.
• Integrate with tools that support data-driven testing reports showing coverage of data variations.

Best Practices for Test Data Management

1. Separate Test Data from Test Code: Keep data files outside test scripts to simplify updates and reuse.
2. Use Realistic and Meaningful Data: Mimic real user data to catch real-world issues.
3. Keep Test Data Small and Focused: Avoid huge files; use only necessary data for each test to improve speed and clarity.
4. Automate Data Loading: Use utility functions or fixtures to load data cleanly and avoid duplication.
5. Maintain Data Consistency: Ensure data matches application expectations and is kept up to date with app changes.

Self Check

Where in this folder structure would you add a new test data file for user permissions?

Key Result

Organize test data separately with utilities and config to keep tests clean, maintainable, and reliable.

Practice

1. What is the main purpose of test data management in software testing?

easy

A. To design the user interface of the application

B. To write the test cases for the software

C. To organize and maintain data needed for testing

D. To fix bugs found during testing

Solution

1. Step 1: Understand the role of test data management

   Test data management is about handling the data used during testing to ensure tests run smoothly and reliably.

2. Step 2: Differentiate from other testing activities

   Writing test cases, fixing bugs, and designing UI are separate tasks from managing test data.

3. Final Answer:

   To organize and maintain data needed for testing -> Option C

4. Quick Check:

   Test data management = Organize test data [OK]

Hint: Test data management means organizing test data [OK]

Common Mistakes:

• Confusing test data management with writing test cases
• Thinking it involves fixing bugs
• Mixing it up with UI design

2. Which of the following is a correct way to represent test data in a CSV file?

easy

A. "username","password","email"\nuser1,pass123,[e-mail]

B. username;password;email
user1;pass123;[e-mail]

C. username password email
user1 pass123 [e-mail]

D. username|password|email
user1|pass123|[e-mail]

Solution

1. Step 1: Identify the CSV format rules

   CSV files use commas to separate values, and text fields are often enclosed in quotes.

2. Step 2: Check each option for correct CSV syntax

   "username","password","email"\nuser1,pass123,[e-mail] uses commas and quotes correctly. Options A, B, and D use spaces, semicolons, or pipes, which are not standard CSV separators.

3. Final Answer:

   "username","password","email"\nuser1,pass123,[e-mail] -> Option A

4. Quick Check:

   CSV uses commas and quotes [OK]

Hint: CSV uses commas, not semicolons or pipes [OK]

Common Mistakes:

• Using semicolons or pipes instead of commas
• Not enclosing text fields in quotes when needed
• Using spaces as separators

3. Given the following Python code snippet for test data setup, what will be the output?

test_data = [
    {'id': 1, 'name': 'Alice'},
    {'id': 2, 'name': 'Bob'},
    {'id': 3, 'name': 'Charlie'}
]

names = [user['name'] for user in test_data if user['id'] > 1]
print(names)

medium

A. ['Alice', 'Bob', 'Charlie']

B. ['Bob', 'Charlie']

C. ['Alice']

D. []

Solution

1. Step 1: Understand the list comprehension condition

   The code selects names where 'id' is greater than 1, so it excludes the entry with id 1 (Alice).

2. Step 2: Identify which names meet the condition

   Users with id 2 and 3 are Bob and Charlie, so the list will be ['Bob', 'Charlie'].

3. Final Answer:

   ['Bob', 'Charlie'] -> Option B

4. Quick Check:

   Filter id > 1 gives Bob and Charlie [OK]

Hint: Filter list by condition to find matching names [OK]

Common Mistakes:

• Including all names without filtering
• Confusing id comparison operators
• Misreading list comprehension syntax

4. A tester wrote this SQL query to insert test data but it fails:

INSERT INTO users (id, username, email)
VALUES (1, 'testuser', [e-mail]);

What is the error and how to fix it?

medium

A. The email value is missing quotes; fix by adding quotes around '[e-mail]'

B. The table name 'users' is incorrect; fix by renaming it to 'user_data'

C. The id value should be a string; fix by adding quotes around 1

D. The VALUES keyword is misspelled; fix by changing it to VALUE

Solution

1. Step 1: Identify syntax error in SQL query

   The email value is a string and must be enclosed in single quotes in SQL.

2. Step 2: Correct the email value by adding quotes

   Change [e-mail] to '[e-mail]' to fix the syntax error.

3. Final Answer:

   The email value is missing quotes; fix by adding quotes around '[e-mail]' -> Option A

4. Quick Check:

   String values need quotes in SQL [OK]

Hint: String values in SQL must be quoted [OK]

Common Mistakes:

• Forgetting quotes around string values
• Changing table names unnecessarily
• Misusing SQL keywords

5. You need to create test data for a user registration form that requires unique emails. Which approach best manages this test data to avoid conflicts during repeated test runs?

hard

A. Store emails in a plain text file without any uniqueness checks

B. Manually create a fixed list of emails and reuse them in every test run

C. Use the same email for all tests and reset the database after each run

D. Use a script that generates a new unique email each time by appending a timestamp

Solution

1. Step 1: Understand the need for unique test data

   Unique emails prevent conflicts and errors when tests run multiple times.

2. Step 2: Evaluate approaches for uniqueness

   Generating emails with timestamps ensures uniqueness automatically, avoiding manual errors or conflicts.

3. Final Answer:

   Use a script that generates a new unique email each time by appending a timestamp -> Option D

4. Quick Check:

   Automate unique data generation to avoid conflicts [OK]

Hint: Generate unique data automatically with timestamps [OK]

Common Mistakes:

• Reusing fixed emails causing test failures
• Resetting database is slow and error-prone
• Ignoring uniqueness leads to conflicts