Explore the core concepts and practical examples of software testing:
Software Testing Types, Levels, and Techniques
A complete overview of how, where, and what to test, covering White/Black/Grey Box, Unit to UAT, and Smoke/Sanity/Regression testing.
QA Testing Examples: Online Banking Transfer
A step-by-step practical example applying testing principles to a money transfer feature, perfect for interview preparation.
🧠 Super Memory Trick 🔥 Smoke = Build is not broken 🔥 Sanity = Fix is logical 🔥 Regression = Nothing else broke Software testing is classified/divided into in 3 main ways: HOW → Testing Techniques (White/Black/Grey Box) WHERE → Testing Levels (Unit → Integration → System → UAT → Release) WHAT → Testing Types (Smoke, Sanity, Regression, Performance, Security, etc.) WHEN CHANGE → Regression/Retest ✅ Complete Software Testing Summary Table (One Page Revision) Testing Type Level / Category Main Purpose (Key Idea) Who Performs When Done Example White Box Testing Technique Tests internal code logic Developers During coding Test all branches in if/else Black Box Testing Technique Tests input/output behavior QA Testers, Users After build ready Login with valid/invalid credentials Unit Testing Level Tests individual function/module Developers First testing stage Test add() function Integration Testing Level Tests interaction between modules Dev + QA After Unit Testing Login module → Dashboard module System Testing Level Tests complete system end-to-end QA Team After Integration Testing Full e-commerce flow checkout Acceptance Testing (UAT) Level Confirms system meets business needs Clients/End Users After System Testing User verifies banking transfer works Functional Testing Type (Black Box) Checks features work as required QA Testers Any testing level Login, Signup, Payment works Regression Testing Type Ensures new changes didn’t break old features QA + Automation After bug fix / new feature Password reset fix → Login still works Smoke Testing Type Checks build stability (basic critical functions) QA / Dev After new build deployment App opens, Login works Sanity Testing Type Checks specific fix/change works correctly QA Testers After small bug fix Discount bug fixed → verify coupon works Retesting Type Confirms a specific bug is fixed QA Testers After defect fix Test same failed case again ⭐ Quick Interview Comparison Table Feature Smoke Sanity Regression Scope Broad & basic Narrow & focused Wide & deep Done After New build Small change/bug fix Any code change Goal Build is stable? Fix works correctly? Old features still work? Test Depth Shallow Medium Deep Software testing is divided: in 3 main ways 1. Testing Techniques/ Approaches (HOW you test): 3 techniques Describe how test cases are designed. ...
🏦 ONE COMPLETE EXAMPLE Online Banking – Money Transfer Feature Scenario: A bank application allows users to log in and transfer money to another account. 🧠 STEP-BY-STEP: ALL TESTING IN ONE FLOW 1️⃣ Testing Techniques (HOW you test) 🔹 White Box Testing (Developer side) What: Developer tests internal code logic of money transfer. Example: Check if balance >= transferAmount Check error handling when DB connection fails Loop validation for retry attempts 👉 Focus: code paths, conditions, loops ...
Your “Project Pitch” Template/ Tell me about your last project In my last role, I worked on a [Type of App, e.g., E-commerce or Healthcare] application. We worked in an Agile-Scrum environment with a team of 5 Developers and 2 QA Engineers. Our total test bank consisted of about 600 test cases. Because we were moving fast with 2-week sprints, we automated the most critical 200 cases using [Tool, e.g., Selenium/Java] to handle our Regression Suite. This allowed us to focus our manual efforts—usually 10 to 15 cases per day—on testing new features and complex edge cases. ...