Software Testing Methodologies (STM) - Full Notes
1. Introduction to Software Testing
Software Testing ■■ software requirements ■■■■■■■■ software ■■■ ■■■■ ■■■■ ■■■■■
■ ■■■■■■■ ■■■■ ■■■■■■■■■■
Why Testing Required
- Bugs ■■■■■■ - Quality ■■■■■■■ ■■■■ - Security ■ Performance ■■■■■ ■■■■ - User
satisfaction ■■■■■■■ ■■■■
Types of Errors
- Error: Developer mistake - Bug/Defect: Code ■ ■■■■■■ - Failure: Wrong output ■■■■ ■■■■
2. Verification & Validation (V&V;)
Verification: ■■■■■■■ ■■■ product ■■■■■■■ build ■■■■■ Validation: Confirm software
user requirement ■■■■ ■■■■
3. SDLC & Testing Models
Models: Waterfall, V-Model, Agile Agile ■ continuous testing ■■■■
4. Levels of Testing
Unit Testing, Integration Testing, System Testing, User Acceptance Testing (UAT)
5. Types of Testing
Functional, Non-Functional, White-Box, Black-Box
Black Box Techniques
Equivalence Partitioning, Boundary Value Analysis, Decision Table, State Transition
6. STLC (Software Testing Life Cycle)
Requirement Analysis → Test Planning → Test Case Design → Environment Setup → Test
Execution → Defect Reporting → Closure
7. Test Case Format
Fields: Test ID, Description, Preconditions, Steps, Expected Output, Actual Output, Status
8. Defect Life Cycle
New → Assigned → In-Progress → Fixed → Retest → Closed/Reopened
Severity vs Priority
Severity = Impact Priority = Fix urgency
9. Automation Testing
Tools: Selenium, JUnit, TestNG, PyTest Used for repetitive and performance tests
Important Interview Concepts
Smoke Testing, Sanity Testing, Regression Testing, Alpha & Beta Testing, Performance Testing
Boundary Value Example
If range = 1–10 → test values: 0,1,10,11