0
0
Testing Fundamentalstesting~8 mins

When to automate vs manual test in Testing Fundamentals - Framework Approaches Compared

Choose your learning style9 modes available
LearnWhyDeepTraceTryChallengeAutomateRecallFrame
Framework Mode - When to automate vs manual test
Folder Structure for Test Automation Project
project-root/
├── tests/                 # Automated test scripts
│   ├── regression/        # Automated regression tests
│   ├── smoke/             # Automated smoke tests
│   └── exploratory/       # Manual test cases documentation
├── pages/                 # Page objects or UI abstractions
├── utils/                 # Helper functions and utilities
├── config/                # Configuration files (env, credentials)
├── reports/               # Test execution reports
└── ci/                    # CI/CD pipeline scripts

This structure supports both automated and manual testing efforts.

Test Framework Layers
  • Test Scripts Layer: Automated tests for repeatable scenarios (e.g., regression, smoke).
  • Manual Test Documentation: Test cases and steps for manual exploratory or usability tests.
  • Page Objects / UI Abstractions: Encapsulate UI elements for automation reuse.
  • Utilities: Helpers for data setup, API calls, waits, logging.
  • Configuration: Environment settings, credentials, browser choices.
  • Reporting: Collect and present test results for both manual and automated tests.
Configuration Patterns
  • Environment Files: Separate configs for dev, test, staging, production.
  • Browser Settings: Choose browsers for automation runs (e.g., Chrome, Firefox).
  • Credentials Management: Secure storage for usernames and passwords.
  • Test Type Flags: Enable or disable automation vs manual test runs.
Test Reporting and CI/CD Integration
  • Automated Test Reports: Generate pass/fail summaries with screenshots and logs.
  • Manual Test Results: Document manual test outcomes in test management tools or spreadsheets.
  • CI/CD Pipelines: Run automated tests on code changes and report results automatically.
  • Notifications: Alert team on test failures or manual test completion.
Framework Design Principles for When to Automate vs Manual Test
  1. Automate repetitive and stable tests: Focus automation on tests that run often and have predictable results.
  2. Manual testing for exploratory and usability: Use manual tests when human judgment or creativity is needed.
  3. Keep manual and automated tests documented: Clear test cases help decide what to automate later.
  4. Maintain automation scripts regularly: Update automated tests as the application changes to avoid false failures.
  5. Use configuration to switch test modes: Easily enable or disable automation or manual test runs based on project needs.
Self-Check Question

Where in this folder structure would you add documentation for manual exploratory test cases?

Key Result
Use automation for repeatable tests and manual testing for exploratory or usability scenarios.