Software Testing Module 3

V Model

1. Verification (Static Testing) ( Left Arm of V model)

Definition

Verification is the process of checking whether the software is being developed correctly according to requirements, without executing the code.

👉 It answers:
“Are we doing the job right?”

Key Points

• It is static testing

• No code execution

• Done by reading documents

• Done early in SDLC

Example

If SRS says:

“Student result should show marks, grade, and pass/fail status”

Verification checks:

• Is this requirement clearly written?

• Is anything missing?

• Is it understandable?

Diagram :User Requirements

                         ↓

                     SRS

                         ↓

                Verification

           (Check documents, not code)

Activities In Verification are as follows

1.Walkthrough ( Informal Verification  method)

2.Review  (Formal Verification method)

Walkthrough (Verification Method – Informal)

Definition

A walkthrough is an informal review where the author explains the document to colleagues.

👉 Author leads the meeting.

Who Participates

• Author

• Colleagues / peers

Purpose

• Find errors

• Get clarification

• Improve understanding

Example

Author explains SRS of Student Result System to classmates and collects feedback.

Diagram

Author
  ↓ explains
Colleagues

Review (Formal Verification Method)
Definition
A review is a formal and planned evaluation of a software document.
Participants
Peer
Superior
Management
Customer
Key Features
Pre-planned
Proper agenda
Records maintained

 MOM – Minutes of Meeting
Definition
MOM is a written record of what was discussed and decided in a meeting.
Contents
Date & time
Participants
Points discussed
Decisions taken
Action items
Example
Meeting: SRS Review
Decision: Add grade column
Action: Developer to update SRS


Validation (Dynamic Testing) ( Right Arm of V model)
Definition
Validation is a disciplined approach used to evaluate whether the final developed software meets the user’s needs and intended purpose by executing the software.
👉 It answers the question:
“Are we doing the right job?”
Key Points
Validation is dynamic testing
Code is executed
Performed after coding
Focuses on user expectations
2. Validation in V-Model
Validation is performed on the right arm of the V-Model during testing phases.
Simple V-Model Diagram
Requirements  ←→  User Acceptance Testing
System Design ←→  System Testing
Module Design ←→  Integration Testing
Coding        ←→  Unit Testing
✔ Left side → Verification
✔ Right side → Validation
3. Why Validation is Important
Confirms software solves the actual problem
Ensures customer satisfaction
Finds defects missed during verification
Reduces failure after deployment
4. Levels of Validation (Testing Levels)
1️⃣ Unit Testing
Definition
Testing of individual modules or components of the software.
Performed By
Developer
Example
In a Job Portal:
Testing login function
Testing resume upload module
Login(username, password) → Success / Error
✔ Ensures each unit works correctly
2️⃣ Integration Testing
Definition
Testing the interaction between integrated modules.
Focus
Interfaces between modules
Example
In an Online Shopping App:
Cart module + Payment gateway
Email sent only after payment success
Cart → Payment → Order Confirmation Email
✔ Ensures modules work together
3️⃣ System Testing
Definition
Testing the complete integrated system to verify compliance with specified requirements.
Performed By
Testers
Example
For a Student Result System:
Login
View marks
Grade calculation
Logout
✔ Entire system is tested as one unit
4️⃣ User Acceptance Testing (UAT)
Definition
Final testing performed by end users or customers to decide whether to accept the system.
Purpose
Confirm system is ready for real use
Example
College staff checks:
Can results be uploaded?
Can students view results correctly?
✔ Final approval before deployment
5. Alpha Testing
Definition
A type of User Acceptance Testing conducted at the developer’s site.
Who Performs
Customer
End users
Developers may assist
Example
College admin tests the Result System in the lab before release.
✔ Uses dummy/synthetic data
6. Beta Testing
Definition
A type of User Acceptance Testing conducted at the user’s location in a real environment.
Who Performs
Actual users
Example
Students use the Result System online after limited release.
✔ Uses real data
7. Alpha vs Beta Testing
Alpha Testing
Beta Testing
At developer site
At user site
Before beta
After alpha
Dummy data
Real data
Controlled environment
Real environment
8. Validation Example (End-to-End)
Online Shopping App
User adds item to cart
Makes payment
Order confirmed
Email notification sent
✔ If all steps work correctly → Validation successful
9. One-Line Summary for Blog
Validation ensures that the final software product meets user expectations by executing the system through different testing levels.