All-in-One Software Testing Interview Q&A
Guide
Complete Resource for Freshers & Experienced Testers (80 Questions)
1. Basic Concepts
1. What is software testing?
Answer: Software testing is the process of evaluating a software application to verify it meets
specified requirements and is free from defects. It ensures quality by identifying bugs early, reducing
risks, and improving user satisfaction.
2. Differentiate between verification and validation.
Answer:
Verification: Checks if the product is built right (process‑oriented). Examples: reviews,
walkthroughs, inspections.
Validation: Ensures the right product is built (product‑oriented). Examples: functional and
non‑functional testing.
Key difference: Verification = "Are we building it right?" | Validation = "Are we building the right
thing?"
3. What are the principles of testing?
Answer:
1. Testing shows presence of defects, not their absence.
2. Exhaustive testing is impossible.
3. Early testing saves time and cost.
4. Defects cluster in a small number of modules (80/20 rule).
5. Pesticide paradox: same tests stop finding new bugs over time.
6. Testing is context dependent.
, 7. Absence of errors fallacy: a defect‑free system can still fail user needs.
4. Difference between Quality Assurance (QA) and Quality Control (QC)?
Answer:
QA: Process‑focused and proactive; aims to prevent defects by improving processes (reviews,
audits, standards).
QC: Product‑focused and reactive; aims to find defects in the actual product (testing,
inspections).
Simple view: QA prevents defects; QC finds defects.
5. What are the different levels of testing?
Answer:
Unit Testing: Individual components or functions (usually by developers).
Integration Testing: Interactions between integrated modules.
System Testing: End‑to‑end testing of the complete system.
Acceptance Testing: Validation by users or clients (UAT).
2. SDLC & STLC
6. Explain SDLC phases.
Answer: The Software Development Life Cycle typically includes:
1. Requirement Analysis – understand and document what needs to be built.
2. Design – create architecture and technical designs.
3. Implementation (Coding) – developers write code.
4. Testing – QA validates the application.
5. Deployment – release to production.
6. Maintenance – bug fixes, improvements, and support.
7. What is STLC?
Answer: The Software Testing Life Cycle is a structured process for testing:
1. Requirement Analysis – identify testable requirements.
, 2. Test Planning – define strategy, scope, resources, schedule, risks.
3. Test Case Development – write and review test cases + test data.
4. Environment Setup – prepare hardware, software, and test environment.
5. Test Execution – run test cases, log results and defects.
6. Test Closure – evaluate exit criteria, prepare closure report, lessons learned.
8. What is a Test Plan?
Answer: A test plan is a document that describes:
Testing objectives and scope
Test strategy and approach
Resources (people, tools, environment)
Schedule and milestones
Entry and exit criteria
Risks and mitigation
Deliverables and responsibilities
9. What is Requirements Traceability Matrix (RTM)?
Answer: RTM is a document that maps requirements to test cases to ensure:
Every requirement has at least one test case.
No test case exists without a requirement.
Easy impact analysis when requirements change.
10. What are entry and exit criteria in testing?
Answer:
Entry Criteria: Conditions that must be met to start testing (approved test plan, stable build, test
environment ready, test data prepared).
Exit Criteria: Conditions to stop testing (all planned tests executed, critical defects fixed,
acceptable defect levels, coverage goals met, closure report prepared).
3. Manual Testing Fundamentals
11. What is manual testing?
Guide
Complete Resource for Freshers & Experienced Testers (80 Questions)
1. Basic Concepts
1. What is software testing?
Answer: Software testing is the process of evaluating a software application to verify it meets
specified requirements and is free from defects. It ensures quality by identifying bugs early, reducing
risks, and improving user satisfaction.
2. Differentiate between verification and validation.
Answer:
Verification: Checks if the product is built right (process‑oriented). Examples: reviews,
walkthroughs, inspections.
Validation: Ensures the right product is built (product‑oriented). Examples: functional and
non‑functional testing.
Key difference: Verification = "Are we building it right?" | Validation = "Are we building the right
thing?"
3. What are the principles of testing?
Answer:
1. Testing shows presence of defects, not their absence.
2. Exhaustive testing is impossible.
3. Early testing saves time and cost.
4. Defects cluster in a small number of modules (80/20 rule).
5. Pesticide paradox: same tests stop finding new bugs over time.
6. Testing is context dependent.
, 7. Absence of errors fallacy: a defect‑free system can still fail user needs.
4. Difference between Quality Assurance (QA) and Quality Control (QC)?
Answer:
QA: Process‑focused and proactive; aims to prevent defects by improving processes (reviews,
audits, standards).
QC: Product‑focused and reactive; aims to find defects in the actual product (testing,
inspections).
Simple view: QA prevents defects; QC finds defects.
5. What are the different levels of testing?
Answer:
Unit Testing: Individual components or functions (usually by developers).
Integration Testing: Interactions between integrated modules.
System Testing: End‑to‑end testing of the complete system.
Acceptance Testing: Validation by users or clients (UAT).
2. SDLC & STLC
6. Explain SDLC phases.
Answer: The Software Development Life Cycle typically includes:
1. Requirement Analysis – understand and document what needs to be built.
2. Design – create architecture and technical designs.
3. Implementation (Coding) – developers write code.
4. Testing – QA validates the application.
5. Deployment – release to production.
6. Maintenance – bug fixes, improvements, and support.
7. What is STLC?
Answer: The Software Testing Life Cycle is a structured process for testing:
1. Requirement Analysis – identify testable requirements.
, 2. Test Planning – define strategy, scope, resources, schedule, risks.
3. Test Case Development – write and review test cases + test data.
4. Environment Setup – prepare hardware, software, and test environment.
5. Test Execution – run test cases, log results and defects.
6. Test Closure – evaluate exit criteria, prepare closure report, lessons learned.
8. What is a Test Plan?
Answer: A test plan is a document that describes:
Testing objectives and scope
Test strategy and approach
Resources (people, tools, environment)
Schedule and milestones
Entry and exit criteria
Risks and mitigation
Deliverables and responsibilities
9. What is Requirements Traceability Matrix (RTM)?
Answer: RTM is a document that maps requirements to test cases to ensure:
Every requirement has at least one test case.
No test case exists without a requirement.
Easy impact analysis when requirements change.
10. What are entry and exit criteria in testing?
Answer:
Entry Criteria: Conditions that must be met to start testing (approved test plan, stable build, test
environment ready, test data prepared).
Exit Criteria: Conditions to stop testing (all planned tests executed, critical defects fixed,
acceptable defect levels, coverage goals met, closure report prepared).
3. Manual Testing Fundamentals
11. What is manual testing?
