🧪 Testing Fundamentals & V-Model
275 words
1 min read
Visual companion
Python
Type and operator map
Python Week 1: the first filter for runtime behavior
View
Revision summary
What this note is really saying
Short form
# 🧪 Testing Fundamentals & V-Model ## 1. 🎯 Learning Objectives - Explain the V-Model and its verification/validation phases - Distinguish verification (did we build it right?) from validation (did we build the right thing?) - Describe the four levels of testing maturity - Create a traceability matrix ## 2.
🧪 Testing Fundamentals & V-Model
1. 🎯 Learning Objectives
- Explain the V-Model and its verification/validation phases
- Distinguish verification (did we build it right?) from validation (did we build the right thing?)
- Describe the four levels of testing maturity
- Create a traceability matrix
2. 📖 Core Content
3.1 What is Software Testing?
Testing is the process of evaluating a system to detect differences between expected and actual behavior. It is NOT just debugging — it is a systematic quality assurance activity.
3.2 The V-Model
The V-Model maps testing activities to development phases:
(Diagram)
Verification (Left side): Are we building the product right? (Reviews, inspections, static analysis) Validation (Right side): Are we building the right product? (Testing against user needs)
3.3 Levels of Testing Maturity
| Level | Name | Description |
|---|---|---|
| 0 | Debugging | Testing = finding bugs during development |
| 1 | Show correctness | Testing proves the software works |
| 2 | Show it doesn't work | Testing aims to find failures |
| 3 | Reduce risk | Testing reduces risk of using software |
| 4 | Mental discipline | Testing is a quality discipline throughout SDLC |
3.4 Traceability Matrix
A table linking requirements to test cases, ensuring all requirements are tested:
| Requirement ID | Test Case ID | Status |
|---|---|---|
| REQ-001 | TC-001, TC-002 | Pass |
| REQ-002 | TC-003 | Fail |
4. 📝 Practice Questions
Q1: What is the difference between verification and validation?Answer: Verification asks "Are we building the product right?" (checking against specifications). Validation asks "Are we building the right product?" (checking against user needs). Verification = reviews/inspections; Validation = testing with users. Q2: A team only tests after finding bugs in production. What testing maturity level is this?Answer: Level 0 (Debugging). Testing is reactive, not systematic. The team has no testing process beyond debugging failures. Join Discord NextBlack-Box Testing