Waterfall testing model in Testing Fundamentals - Test Execution Trace

Test Overview

This test simulates the Waterfall testing model by verifying that each testing phase completes before the next begins. It checks that requirements are reviewed, design is validated, implementation is tested, and final acceptance is confirmed in order.

Test Code - unittest

Testing Fundamentals

class WaterfallTestingModel:
    def __init__(self):
        self.phases = ["Requirements Review", "Design Validation", "Implementation Testing", "Acceptance Testing"]
        self.current_phase_index = 0

    def complete_phase(self, phase_name):
        if self.current_phase_index < len(self.phases) and self.phases[self.current_phase_index] == phase_name:
            self.current_phase_index += 1
            return True
        else:
            return False

import unittest

class TestWaterfallModel(unittest.TestCase):
    def setUp(self):
        self.model = WaterfallTestingModel()

    def test_phases_in_order(self):
        self.assertTrue(self.model.complete_phase("Requirements Review"))
        self.assertTrue(self.model.complete_phase("Design Validation"))
        self.assertTrue(self.model.complete_phase("Implementation Testing"))
        self.assertTrue(self.model.complete_phase("Acceptance Testing"))

    def test_phases_out_of_order(self):
        self.assertFalse(self.model.complete_phase("Design Validation"))
        self.assertTrue(self.model.complete_phase("Requirements Review"))
        self.assertFalse(self.model.complete_phase("Acceptance Testing"))

if __name__ == "__main__":
    unittest.main()

Execution Trace - 8 Steps

Step	Action	System State	Assertion	Result
1	Test starts - unittest framework initializes test class and methods	Test environment ready with WaterfallTestingModel instance	—	PASS
2	Calls complete_phase with 'Requirements Review'	Current phase is 'Requirements Review'	Check if phase matches current phase	PASS
3	Calls complete_phase with 'Design Validation'	Current phase is 'Design Validation'	Check if phase matches current phase	PASS
4	Calls complete_phase with 'Implementation Testing'	Current phase is 'Implementation Testing'	Check if phase matches current phase	PASS
5	Calls complete_phase with 'Acceptance Testing'	Current phase is 'Acceptance Testing'	Check if phase matches current phase	PASS
6	Calls complete_phase with 'Design Validation' out of order	Current phase reset to 0 for new test, which is 'Requirements Review'	Check if phase matches current phase	FAIL
7	Calls complete_phase with 'Requirements Review'	Current phase is 'Requirements Review'	Check if phase matches current phase	PASS
8	Calls complete_phase with 'Acceptance Testing' out of order	Current phase is 'Design Validation'	Check if phase matches current phase	FAIL

Failure Scenario

Failing Condition: Trying to complete a testing phase out of the defined order

Execution Trace Quiz - 3 Questions

What does the test verify about the Waterfall testing model?

A Phases can be completed in any order

B Only the last phase is important

C Phases must be completed in order

D Phases can be skipped

Key Result

Always verify that testing phases follow the defined sequence in Waterfall to catch errors early and maintain process discipline.

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