Waterfall testing model in Testing Fundamentals - Build an Automation Script

Verify Waterfall Testing Model Phases Execution

Preconditions (2)

Step 1: Review the requirements documentation

Step 2: Verify the design document is created based on requirements

Step 3: Check that the implementation (coding) is done according to design

Step 4: Confirm that the testing phase is executed after implementation

Step 5: Validate that the deployment happens only after testing is complete

Step 6: Ensure maintenance phase is planned after deployment

✅ Expected Result: Each phase of the Waterfall testing model is completed in sequence without overlap, and the output of one phase is the input for the next phase.

Automation Requirements - N/A - Manual process verification

Assertions Needed:

Verify phase completion order

Verify documentation artifacts exist for each phase

Verify no phase starts before the previous phase ends

Best Practices:

Use checklist to confirm phase completion

Maintain clear documentation for each phase

Communicate phase status with stakeholders

Automated Solution

The Waterfall testing model is a sequential process and is mostly verified through documentation and process checks rather than automation code. Automation is not applicable here because it is a methodology, not a software feature. The test involves confirming that each phase is completed before the next begins, which is done by reviewing documents and project status reports.

Therefore, no automation script is provided. Instead, testers use checklists and documentation reviews to ensure the Waterfall phases are followed correctly.

Common Mistakes - 3 Pitfalls

Trying to automate the Waterfall model phases as if it were a software feature

Skipping phase verification and assuming phases are completed

Overlapping phases in Waterfall model

Bonus Challenge

Create a checklist template to manually track the completion of each Waterfall testing model phase with three sample projects.

Show Hint

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