Waterfall testing model in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the Waterfall testing model?

The Waterfall testing model is a step-by-step approach where testing happens after the software development phases are complete, following a fixed sequence.

beginner

List the main phases of the Waterfall testing model.

The main phases are: Requirements, Design, Implementation, Testing, Deployment, and Maintenance.

beginner

Why is the Waterfall testing model called 'sequential'?

Because each phase must finish before the next one starts, like steps in a waterfall flowing down one after another.

intermediate

What is a key disadvantage of the Waterfall testing model?

It is hard to go back and change something once a phase is finished, so bugs found late can be costly to fix.

intermediate

When is the Waterfall testing model most suitable?

It works best when requirements are clear and unlikely to change, like in simple or well-understood projects.

In the Waterfall testing model, when does testing occur?

A Only after deployment

B Continuously during development

C Before requirements gathering

D After all development phases are complete

Testing happens after the implementation phase is finished in the Waterfall model.

Which of the following is NOT a phase in the Waterfall model?

A Continuous Integration

B Implementation

C Design

D Maintenance

Continuous Integration is a modern practice not part of the traditional Waterfall phases.

What is a major risk of using the Waterfall testing model?

A Too much flexibility in requirements

B Difficulty fixing bugs found late

C Testing happens too early

D No documentation is created

Because testing is late, bugs found then can be expensive and hard to fix.

Which project type suits the Waterfall testing model best?

A Projects with changing requirements

B Projects needing frequent releases

C Simple projects with clear requirements

D Exploratory projects

Waterfall works well when requirements are stable and clear from the start.

How does the Waterfall model handle changes in requirements?

A Changes are difficult and costly after a phase is done

B Easily adapts at any phase

C Changes are ignored

D Changes are handled during testing

Once a phase is finished, going back to change something is hard and expensive.

Explain the sequence of phases in the Waterfall testing model and why it is called sequential.

Think of how water flows down steps one after another.

Describe the advantages and disadvantages of using the Waterfall testing model.

Consider both what makes it simple and what makes it risky.

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