Waterfall testing model in Testing Fundamentals - Framework Patterns

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.

Practice

1. Which of the following best describes the Waterfall testing model?

easy

A. Testing happens before requirements gathering.

B. Testing is done continuously during coding.

C. Testing is skipped to save time.

D. Testing is done after all development phases are completed.

Solution

1. Step 1: Understand Waterfall phases order

   The Waterfall model follows a strict sequence: requirements, design, implementation, testing, and maintenance.

2. Step 2: Identify when testing occurs

   Testing happens only after implementation is complete, not during coding or before requirements.

3. Final Answer:

   Testing is done after all development phases are completed. -> Option D

4. Quick Check:

   Waterfall testing = after implementation [OK]

Hint: Remember: Waterfall tests only after coding ends [OK]

Common Mistakes:

• Thinking testing happens during coding
• Assuming testing is skipped
• Believing testing is before requirements

2. Which phase comes immediately before testing in the Waterfall model?

easy

A. Requirements gathering

B. Implementation (coding)

C. Maintenance

D. Design

Solution

1. Step 1: Recall Waterfall phase order

   The phases are: requirements, design, implementation, testing, maintenance.

2. Step 2: Identify phase before testing

   Implementation (coding) is done right before testing starts.

3. Final Answer:

   Implementation (coding) -> Option B

4. Quick Check:

   Phase before testing = Implementation [OK]

Hint: Testing follows coding phase in Waterfall [OK]

Common Mistakes:

• Choosing design instead of implementation
• Confusing maintenance with testing phase
• Selecting requirements as previous phase

3. Consider this Waterfall model scenario:
Requirements -> Design -> Implementation -> Testing -> Maintenance
What is the main risk if a requirement error is found during testing?

medium

A. It can be fixed easily without affecting other phases.

B. It will be ignored since testing is last.

C. It may require going back to earlier phases, causing delays.

D. It means the design phase was skipped.

Solution

1. Step 1: Understand Waterfall's linear flow

   Waterfall is sequential; going back to fix earlier phases is costly and slow.

2. Step 2: Analyze impact of requirement errors found late

   Finding errors during testing means redoing requirements, design, and implementation, causing delays.

3. Final Answer:

   It may require going back to earlier phases, causing delays. -> Option C

4. Quick Check:

   Late errors cause phase rework and delays [OK]

Hint: Late fixes in Waterfall cause costly rework [OK]

Common Mistakes:

• Assuming fixes are easy after testing
• Ignoring errors found late
• Confusing skipped phases with errors

4. A tester finds that testing started before implementation was fully done in a Waterfall project. What is the main problem here?

medium

A. Testing is happening too early, breaking Waterfall rules.

B. Testing is correctly done in parallel with coding.

C. Requirements phase was skipped.

D. Maintenance phase started too soon.

Solution

1. Step 1: Recall Waterfall testing timing

   Testing must start only after implementation is complete in Waterfall.

2. Step 2: Identify issue with early testing

   Starting testing before implementation breaks the strict phase order, causing confusion and errors.

3. Final Answer:

   Testing is happening too early, breaking Waterfall rules. -> Option A

4. Quick Check:

   Testing before coding ends = wrong in Waterfall [OK]

Hint: Waterfall testing only after coding finishes [OK]

Common Mistakes:

• Thinking testing can run in parallel with coding
• Blaming requirements or maintenance phases
• Ignoring phase order importance

5. A project using the Waterfall model has very unclear requirements that keep changing. What is the best testing approach to handle this?

hard

A. Switch to an iterative model with testing during development.

B. Skip testing to save time on changing requirements.

C. Stick to Waterfall testing after implementation despite changes.

D. Test only after maintenance phase.

Solution

1. Step 1: Understand Waterfall limits with changing requirements

   Waterfall works best with clear, stable requirements; changes cause delays and rework.

2. Step 2: Choose suitable testing approach

   Iterative models allow testing during development and adapt to changes better than Waterfall.

3. Final Answer:

   Switch to an iterative model with testing during development. -> Option A

4. Quick Check:

   Changing requirements = use iterative testing [OK]

Hint: Use iterative testing if requirements change often [OK]

Common Mistakes:

• Forcing Waterfall despite unstable requirements
• Skipping testing to save time
• Testing only after maintenance phase