Test environment setup in Testing Fundamentals - Framework Patterns

Framework Mode - Test environment setup

Folder Structure for Test Environment Setup

project-root/
├── config/
│   ├── environments/
│   │   ├── dev.env
│   │   ├── test.env
│   │   └── prod.env
│   └── credentials.env
├── tests/
│   ├── unit/
│   ├── integration/
│   └── e2e/
├── utilities/
│   └── env_manager.py
├── reports/
├── logs/
└── README.md

Test Framework Layers for Environment Setup

• Configuration Layer: Holds environment files and credentials to separate settings from code.
• Utilities Layer: Contains scripts to load and switch environments, manage secrets safely.
• Test Layer: Tests use environment variables to run against different setups (dev, test, prod).
• Reporting Layer: Collects logs and test results per environment for clear analysis.

Configuration Patterns

Use separate environment files for each setup (development, testing, production). Each file stores variables like URLs, database connections, and API keys.

Load environment variables at test start using a utility script. This keeps tests flexible and safe.

Example: dev.env might have BASE_URL=https://dev.example.com, while prod.env has BASE_URL=https://example.com.

Keep credentials in a secure file credentials.env and never commit it to version control.

Test Reporting and CI/CD Integration

Generate separate test reports for each environment run. Include environment details in report headers.

Integrate environment setup in CI/CD pipelines by loading the correct environment file before tests run.

Example: In CI, set environment variable ENV=dev to run tests against development environment automatically.

Store logs and reports in folders named by environment for easy access and debugging.

Best Practices for Test Environment Setup

• Isolate environments: Keep dev, test, and prod separate to avoid accidental data loss or interference.
• Use environment variables: Avoid hardcoding URLs or secrets in test code.
• Secure credentials: Store sensitive data outside code and use secure vaults or encrypted files.
• Automate environment loading: Use scripts or tools to switch environments easily.
• Document environment setup: Keep README updated with instructions to set up and run tests in each environment.

Self Check

Where in this folder structure would you add a new environment file for a staging environment?

Key Result

Separate environment configurations and secure credentials to enable flexible, safe test runs across multiple setups.