Swipe left or tap Next ▶ to turn the page.
Select any text to highlight it or add a note. Tap a diagram to enlarge it.
Testing Foundations: SDLC, STLC, Models, Levels and Types
- ✔ Explain what a software tester does and the seven testing principles
- ✔ Walk through SDLC and STLC phases with entry and exit criteria
- ✔ Compare Waterfall, V-Model, Agile and Scrum, and the tester's role in each
- ✔ Name the testing levels and types, and tell verification from validation
What a software tester really does
The first question in most QA interviews is "What is software testing?", and a clear answer tells the panel you understand the job, not just the word.
Software testing is the process of checking a product against what it is supposed to do, so that problems are found before users find them. A tester runs the software, studies documents, asks questions and reports what is wrong, unclear or risky.
Think of a railway booking app. The developer checks the happy path. The tester asks: what if the train is full, the UPI payment times out, or two people book the last berth at the same second?
Error, defect, failure
These three words are asked very often, and each has a precise meaning.
| Term | Who or what | Example |
|---|---|---|
| Error (mistake) | A human action that is wrong | Developer types > instead of >= |
| Defect (bug, fault) | The flaw that sits in the code or document | The age check now rejects a 60-year-old for senior concession |
| Failure | What the user sees when the defect runs | A 60-year-old passenger does not get the discount |
flowchart LR E[Error by a person] --> D[Defect in code or document] D --> F[Failure when the code runs]
Story: a developer misreads the rule "free delivery above ₹499" and codes "above ₹500".
The misreading is the error (a human mistake).
The wrong number in the code is the defect.
A customer with a ₹499.50 cart is charged delivery. That visible wrong behaviour is the failure.
Answer: error → defect → failure, in that order.
A tester sees that the app shows ₹0 as the total for a cart with two items. What is this, in testing terms?
The tester is seeing wrong behaviour while the software runs. That is a failure; the cause in the code is the defect.
The seven principles of testing
Interviewers love "Tell me any three testing principles". Know all seven with one example each, and you can answer in under a minute.
These come from the ISTQB Foundation syllabus.
| # | Principle | In one line |
|---|---|---|
| 1 | Testing shows the presence of defects | Testing can prove bugs exist, never that none exist |
| 2 | Exhaustive testing is impossible | You cannot try every input, so you prioritise |
| 3 | Early testing saves time and money | Find problems in requirements, not after release |
| 4 | Defects cluster together | A few modules usually hold most of the bugs |
| 5 | Beware of the pesticide paradox | The same old tests stop finding new bugs |
| 6 | Testing is context dependent | A banking app and a game are tested differently |
| 7 | Absence-of-errors is a fallacy | A bug-free app that solves the wrong problem is still useless |
Why exhaustive testing is impossible
Even small forms have huge numbers of input combinations, so testers pick a smart sample (Day 2 techniques).
A 4-digit OTP field accepts 0000 to 9999.
Number of values = 10 × 10 × 10 × 10 = 10,000.
Add a language choice (Hindi or English): 10,000 × 2 = 20,000.
Answer: 20,000 cases for two small fields, so we test a chosen sample.
The pesticide paradox
Insects resist a pesticide used every season. In the same way, old tests that are run unchanged every sprint stop finding new bugs. The fix is to review and add new tests regularly.
Situation: the payment module had 40 bugs last release; the profile page had 2.
Most bugs are in one area.
This is defect clustering.
Answer: Principle 4, defects cluster together.
SDLC: how software is built, phase by phase
Every tester works inside a Software Development Life Cycle, so you must know where testing fits and what each phase produces.
The Software Development Life Cycle (SDLC) is the series of phases a team follows to plan, build and deliver software. Names vary slightly between books, but the common six are:
| Phase | Main question | Typical output |
|---|---|---|
| 1. Requirement gathering and analysis | What does the customer need? | Requirement document (SRS / BRS) |
| 2. Design | How will we build it? | High-level and low-level design documents |
| 3. Implementation (coding) | Build it | Source code, unit tests |
| 4. Testing | Does it work as required? | Test results, defect reports |
| 5. Deployment | Release to users | Live system, release notes |
| 6. Maintenance | Fix and improve after release | Patches, updates |
flowchart LR R[Requirements] --> D[Design] D --> C[Coding] C --> T[Testing] T --> Dep[Deployment] Dep --> M[Maintenance] M -. new needs .-> R
Activity: "The architect decides the app will use a separate service for payments."
This decides how to build, not what to build.
Answer: Design phase.
Keep going with the full course
Day 1 has 23 pages. You have read the first 3.
See what's inside →