How to Use This Guide
These are the Manual Testing interview questions that QA Engineers encounter most frequently during interviews.
Each answer provides a concise explanation suitable for interview revision. For complete explanations, practical examples, and real-world scenarios, refer to the linked tutorial.
For the complete learning path, begin with the Complete Manual Testing Guide.
Testing Fundamentals (Q1–5)
Q1. What is Manual Testing?
Manual Testing is the process of executing test cases manually without using automation tools to verify that an application behaves as expected.
Learn more: Manual & Automation
Q2. What is the difference between Manual Testing and Automation Testing?
- Manual Testing is suitable for exploratory, usability, and one-time testing.
- Automation Testing is suitable for repetitive, stable, and regression testing.
Learn more: Manual vs Automation
Q3. What is the difference between QA and QC?
- QA (Quality Assurance) focuses on improving processes and preventing defects.
- QC (Quality Control) focuses on identifying defects in the product.
Learn more: QA Concepts
Q4. What is the difference between Verification and Validation?
- Verification confirms that the product is being built correctly.
- Validation confirms that the correct product is being built.
Learn more: Black Box, White Box & Grey Box Testing
Q5. What is the difference between Testing and Debugging?
- Testing identifies defects.
- Debugging determines the root cause of defects and fixes them.
Learn more: QA Concepts
Functional Testing Types (Q6–11)
Q6. What is the difference between Smoke Testing and Sanity Testing?
- Smoke Testing verifies whether the build is stable enough for testing.
- Sanity Testing verifies that a specific change or defect fix works correctly.
Learn more: Smoke vs Sanity Testing
Q7. What is Regression Testing?
Regression Testing verifies that newly introduced changes have not affected existing functionality.
It is typically executed for every new build.
Learn more: Functional Testing Types
Q8. What is the difference between Retesting and Regression Testing?
- Retesting verifies the corrected defect.
- Regression Testing ensures that other functionality continues to work correctly.
Learn more: Functional Testing Types
Q9. What is Build Verification Testing (BVT)?
BVT is a set of core functionality tests executed on every new build.
If BVT fails, the build is generally returned to the development team.
Learn more: Functional Testing Types
Q10. What is User Acceptance Testing (UAT)?
UAT is performed by customers or end users to verify that the software satisfies business requirements before release.
Learn more: Functional Testing Types
Q11. What is the typical order of Smoke, Retesting, Sanity, and Regression Testing?
The typical execution order is:
- Smoke Testing
- Retesting
- Sanity Testing
- Regression Testing
Learn more: Functional Testing Types
Defect Management (Q12–17)
Q12. What is the difference between Severity and Priority?
- Severity indicates the impact of the defect.
- Priority indicates how urgently the defect should be fixed.
Learn more: Severity vs Priority
Q13. Give an example of High Severity and Low Priority.
A broken Privacy Notice link affects functionality but usually has a low business priority because relatively few users access it.
Learn more: Defect Management
Q14. What is the Defect Life Cycle?
A typical defect life cycle includes:
- New
- Assigned
- Open
- Fixed
- Retest
- Closed
Additional states may include Reopened, Deferred, or Rejected.
Learn more: Defect Management
Q15. What is the difference between Bug Leakage and Bug Release?
- Bug Leakage is a defect missed during testing and discovered by users.
- Bug Release is a known defect intentionally released after business approval.
Learn more: Defect Management
Q16. What is Defect Triage?
Defect Triage is a review meeting where the team discusses defect severity, priority, ownership, and scheduling.
Learn more: Defect Management
Q17. What is a Showstopper Defect?
A Showstopper Defect is a critical defect that prevents further testing.
Learn more: Defect Management
Agile & Process (Q18–22)
Q18. What is Agile?
Agile is an iterative software development methodology that delivers working software in short development cycles called sprints.
Learn more: Agile & Scrum
Q19. What is the difference between Agile and Waterfall?
- Waterfall follows a sequential development approach.
- Agile delivers software incrementally with testing performed during every sprint.
Learn more: Agile vs Waterfall
Q20. What are the Scrum ceremonies?
The major Scrum ceremonies include:
- Sprint Planning
- Daily Scrum
- Sprint Review
- Sprint Retrospective
Learn more: Agile & Scrum
Q21. What is the difference between SDLC and STLC?
- SDLC is the Software Development Life Cycle.
- STLC is the Software Testing Life Cycle.
Learn more: SDLC & STLC
Q22. What are the phases of STLC?
The STLC phases include:
- Requirement Analysis
- Test Planning
- Test Case Design
- Test Environment Setup
- Test Execution
- Test Closure
Learn more: SDLC & STLC
Test Design & Documentation (Q23–27)
Q23. What is the difference between a Test Plan and a Test Strategy?
- Test Plan is project-specific.
- Test Strategy defines the overall organizational testing approach.
Learn more: Documentation & Planning
Q24. What is a Requirement Traceability Matrix (RTM)?
RTM maps requirements to test cases to ensure complete requirement coverage and simplify impact analysis.
Learn more: Documentation & Planning
Q25. What is Boundary Value Analysis?
Boundary Value Analysis focuses testing on the boundary values of valid input ranges where defects commonly occur.
Learn more: Test Design Techniques
Q26. What is Equivalence Partitioning?
Equivalence Partitioning divides input values into groups that are expected to behave similarly, allowing representative values to be tested.
Learn more: Test Design Techniques
Q27. What is the difference between Black Box, White Box, and Grey Box Testing?
- Black Box Testing evaluates functionality without internal code knowledge.
- White Box Testing validates internal code and logic.
- Grey Box Testing combines characteristics of both approaches.
Learn more: Black Box, White Box & Grey Box Testing
Non-Functional Testing & QA Concepts (Q28–30)
Q28. What is the difference between Load Testing and Stress Testing?
- Load Testing verifies system performance under expected workloads.
- Stress Testing evaluates behavior beyond expected capacity to determine the breaking point.
Learn more: Non-Functional Testing
Q29. What is the difference between Alpha Testing and Beta Testing?
- Alpha Testing is performed internally before product release.
- Beta Testing is performed by real users in real-world environments.
Learn more: Integration & System Testing
Q30. What is the Pesticide Paradox, and when should testing stop?
The Pesticide Paradox states that repeatedly executing the same test cases eventually stops finding new defects, so test cases should be continuously improved.
Testing generally concludes when predefined exit criteria have been satisfied, including acceptable defect levels, required coverage, and agreed project timelines.
Learn more: QA Concepts
Next Steps
Continue your Manual Testing interview preparation with:
- Complete Manual Testing Guide
- Complete Jira Guide
- Complete Selenium Guide
- SDET Interview Guide