0
0
Testing Fundamentalstesting~8 mins

Waterfall testing model in Testing Fundamentals - Framework Patterns

Choose your learning style9 modes available
Framework Mode - Waterfall testing model
Folder Structure of a Waterfall Testing Project
waterfall-testing-project/
├── requirements/
│   └── requirements-specification.docx
├── design/
│   └── design-documents/
│       └── system-design.pdf
├── implementation/
│   └── source-code/
│       └── main-app-code
├── testing/
│   ├── test-plans/
│   │   └── test-plan.docx
│   ├── test-cases/
│   │   └── test-cases.xlsx
│   ├── test-scripts/
│   │   └── automated-tests/
│   └── test-reports/
│       └── test-report-001.pdf
└── deployment/
    └── deployment-guides/
        └── deployment-instructions.docx
  
Waterfall Testing Model Layers
  • Requirements Layer: Collect and document all requirements before testing.
  • Design Layer: Prepare test plans and test cases based on design documents.
  • Implementation Layer: Develop the software according to design; no testing here.
  • Testing Layer: Execute test cases after implementation is complete.
  • Deployment Layer: Release software after successful testing.
Configuration Patterns in Waterfall Testing

Since Waterfall is a sequential model, configuration is usually fixed per phase:

  • Environment Setup: Prepare test environment only after implementation is done.
  • Test Data: Defined upfront in test plans and test cases.
  • Version Control: Use versioning to freeze code before testing phase.
  • Documentation: Maintain detailed documents for each phase to avoid changes later.
Test Reporting and CI/CD Integration

Waterfall testing typically uses manual reporting and limited automation:

  • Test Reports: Detailed test execution reports created after testing phase.
  • Defect Tracking: Bugs logged and tracked in tools like JIRA.
  • CI/CD: Usually minimal or no continuous integration; deployment happens after testing completes.
  • Sign-off: Formal approval required before moving to deployment.
Best Practices for Waterfall Testing Model
  • Complete Documentation: Keep all requirements and test plans clear and detailed before starting.
  • Phase Completion: Finish one phase fully before starting the next to avoid confusion.
  • Early Review: Review requirements and design early to reduce errors downstream.
  • Test Case Design: Design test cases based on requirements to ensure coverage.
  • Formal Sign-offs: Use approvals at each phase to confirm readiness to proceed.
Self Check Question

In the Waterfall testing project structure shown, where would you add a new test case document for a feature?

Key Result
Waterfall testing follows a strict sequential phase approach with clear documentation and phase sign-offs.