V-Model (verification and validation) in Testing Fundamentals - Build an Automation Script

Verify V-Model phases and their corresponding verification and validation activities

Preconditions (2)

Step 1: Review the V-Model diagram showing development phases on the left and testing phases on the right

Step 2: Identify the verification activities linked to each development phase

Step 3: Identify the validation activities linked to each testing phase

Step 4: Match each development phase with its corresponding testing phase in the V-Model

Step 5: Confirm that verification activities ensure correctness of deliverables at each phase

Step 6: Confirm that validation activities ensure the product meets user needs

✅ Expected Result: All development phases are correctly matched with their verification and validation testing phases, demonstrating understanding of the V-Model concept

Automation Requirements - Python unittest

Assertions Needed:

Assert that each development phase has a corresponding verification activity

Assert that each testing phase has a corresponding validation activity

Assert that the mapping between development and testing phases follows the V-Model structure

Best Practices:

Use clear and descriptive test method names

Organize test data as dictionaries for easy mapping

Use assertions that provide meaningful failure messages

Automated Solution

Testing Fundamentals

import unittest

class TestVModelVerificationValidation(unittest.TestCase):
    def setUp(self):
        # Define development phases and their verification activities
        self.development_phases = {
            'Requirements': 'Requirements Review',
            'System Design': 'System Design Review',
            'Architecture Design': 'Architecture Review',
            'Module Design': 'Module Design Review',
            'Coding': 'Code Review'
        }
        # Define testing phases and their validation activities
        self.testing_phases = {
            'Unit Testing': 'Module Validation',
            'Integration Testing': 'Architecture Validation',
            'System Testing': 'System Validation',
            'Acceptance Testing': 'Requirements Validation'
        }
        # Define expected mapping between development and testing phases
        self.v_model_mapping = {
            'Requirements': 'Acceptance Testing',
            'System Design': 'System Testing',
            'Architecture Design': 'Integration Testing',
            'Module Design': 'Unit Testing',
            'Coding': 'Unit Testing'
        }

    def test_verification_activities_exist(self):
        for phase, activity in self.development_phases.items():
            self.assertIsInstance(activity, str, f'Verification activity missing for {phase}')

    def test_validation_activities_exist(self):
        for phase, activity in self.testing_phases.items():
            self.assertIsInstance(activity, str, f'Validation activity missing for {phase}')

    def test_v_model_phase_mapping(self):
        for dev_phase, test_phase in self.v_model_mapping.items():
            self.assertIn(dev_phase, self.development_phases, f'Development phase {dev_phase} not defined')
            self.assertIn(test_phase, self.testing_phases, f'Testing phase {test_phase} not defined')

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

This test class checks the V-Model phases and their verification and validation activities.

In setUp, we define dictionaries for development phases with their verification activities, testing phases with validation activities, and the expected mapping between them.

The first test test_verification_activities_exist ensures each development phase has a verification activity defined.

The second test test_validation_activities_exist ensures each testing phase has a validation activity defined.

The third test test_v_model_phase_mapping verifies that each development phase maps to a valid testing phase according to the V-Model.

Assertions include clear messages to help understand failures.

Common Mistakes - 3 Pitfalls

Not defining all development phases or testing phases

Using vague or missing assertion messages

Mixing verification and validation activities incorrectly

Bonus Challenge

Now add data-driven testing to verify multiple sets of V-Model mappings with different project types

Show Hint

Practice

1. What is the main purpose of the V-Model in software testing?

easy

A. To focus only on validation after development is complete

B. To replace all manual testing with automated testing

C. To link development phases with corresponding testing phases

D. To eliminate the need for documentation during testing

Solution

1. Step 1: Understand the V-Model concept

   The V-Model connects each development phase with a matching testing phase to ensure thorough testing coverage.

2. Step 2: Analyze the options

   Only 'To link development phases with corresponding testing phases' correctly describes this linking of development and testing phases. Other options describe incorrect or unrelated ideas.

3. Final Answer:

   To link development phases with corresponding testing phases -> Option C

4. Quick Check:

   V-Model = Link dev and test phases [OK]

Hint: Remember V-Model pairs dev and test steps early [OK]

Common Mistakes:

• Thinking V-Model is only about validation
• Believing it removes manual testing
• Assuming no documentation is needed

2. Which of the following correctly describes verification in the V-Model?

easy

A. Ensuring the product is built according to specifications

B. Checking if the product meets user needs

C. Testing the product after deployment

D. Validating the user interface design

Solution

1. Step 1: Define verification in V-Model context

   Verification means checking if the product is built correctly according to specifications and design documents.

2. Step 2: Match options to verification definition

   Ensuring the product is built according to specifications matches this definition. Checking if the product meets user needs describes validation, testing the product after deployment is incorrect timing, and validating the user interface design is a specific validation activity.

3. Final Answer:

   Ensuring the product is built according to specifications -> Option A

4. Quick Check:

   Verification = built correctly [OK]

Hint: Verification = build right; Validation = build right product [OK]

Common Mistakes:

• Confusing verification with validation
• Thinking verification happens only after deployment
• Assuming verification tests user needs

3. Consider the following phases in the V-Model:
Requirements Analysis and Acceptance Testing.
Which statement is true about their relationship?

medium

A. Requirements Analysis is validated by Unit Testing

B. Acceptance Testing verifies the Requirements Analysis phase

C. Acceptance Testing is unrelated to Requirements Analysis

D. Requirements Analysis is tested after system deployment

Solution

1. Step 1: Identify matching phases in V-Model

   In the V-Model, Acceptance Testing corresponds to and verifies the Requirements Analysis phase.

2. Step 2: Evaluate options based on this mapping

   Acceptance Testing verifies the Requirements Analysis phase correctly states this relationship. The option 'Requirements Analysis is validated by Unit Testing' incorrectly pairs Requirements Analysis with Unit Testing, the option 'Acceptance Testing is unrelated to Requirements Analysis' denies the relationship, and the option 'Requirements Analysis is tested after system deployment' is incorrect timing.

3. Final Answer:

   Acceptance Testing verifies the Requirements Analysis phase -> Option B

4. Quick Check:

   Req Analysis ↔ Acceptance Testing [OK]

Hint: Match left side dev phase with right side test phase [OK]

Common Mistakes:

• Mixing up which test phase matches which dev phase
• Thinking Unit Testing validates requirements
• Ignoring the V shape mapping

4. A tester finds that system testing is started before the design phase is complete. What is the main issue with this in the V-Model?

medium

A. Requirements gathering is incomplete

B. Verification is done after validation

C. Validation is skipped entirely

D. Testing phases are not aligned with development phases

Solution

1. Step 1: Understand V-Model phase alignment

   The V-Model requires testing phases to start only after their corresponding development phases complete.

2. Step 2: Analyze the problem

   Starting system testing before design completion breaks this alignment, causing potential test mismatches.

3. Final Answer:

   Testing phases are not aligned with development phases -> Option D

4. Quick Check:

   Test phases must follow dev phases [OK]

Hint: Test only after matching dev phase done [OK]

Common Mistakes:

• Confusing verification and validation order
• Assuming validation is skipped
• Blaming requirements instead of phase timing

5. In the V-Model, if validation activities are performed too early before the product is stable, what is a likely consequence?

hard

A. Validation results may be inaccurate due to incomplete product

B. Verification will automatically fix all defects

C. Testing phases will be skipped to save time

D. Requirements will be ignored during testing

Solution

1. Step 1: Understand timing of validation in V-Model

   Validation ensures the product meets user needs and is usually done after the product is stable.

2. Step 2: Analyze early validation impact

   If validation happens too early, the product may be incomplete or unstable, causing inaccurate or misleading validation results.

3. Final Answer:

   Validation results may be inaccurate due to incomplete product -> Option A

4. Quick Check:

   Early validation = inaccurate results [OK]

Hint: Validate only after product stability [OK]

Common Mistakes:

• Believing verification fixes defects automatically
• Thinking testing phases can be skipped
• Assuming requirements are ignored