Top 30 Interview Questions for Software Testing Fundamentals

If you are preparing for a manual software testing interview, strong fundamentals are your biggest advantage. Most interviewers check whether you clearly understand core concepts like STLC, defect lifecycle, test design techniques, and practical QA thinking. This article gives you 30 important manual testing fundamental questions with simple and clear answers so you can build confidence and answer in a structured way.

This guide is created for beginners and early-career testers who want strong basics in manual testing. The answers are simple, practical, and slightly elaborated for easy understanding.

1. What is software testing? Why is it important?

Software testing is the process of checking whether an application behaves as expected under different conditions. It helps identify defects before release and reduces production failures. Good testing improves user trust, product quality, and business confidence.

2. What is the difference between QA and QC?

QA (Quality Assurance) focuses on improving process so defects can be prevented early. QC (Quality Control) focuses on identifying defects in the actual product through testing and inspection. In short, QA is preventive and QC is detective.

3. What is SDLC?

SDLC stands for Software Development Life Cycle. It includes planning, requirement analysis, design, coding, testing, deployment, and maintenance. It is the full lifecycle followed to build and run software successfully.

4. What is STLC?

STLC stands for Software Testing Life Cycle. It includes requirement analysis, test planning, test design, environment setup, execution, and closure. It helps testing remain organized, measurable, and aligned with product goals.

5. What is the difference between verification and validation?

Verification checks whether we are building the software correctly as per requirements and standards. Validation checks whether the built product actually satisfies user and business needs. A simple line: verification is “build right,” validation is “right build.”

6. What is a test case?

A test case is a documented set of steps, input data, preconditions, and expected results used to verify specific functionality. It helps testers execute checks consistently. Well-written test cases are clear, traceable, and reusable.

7. What is a test scenario?

A test scenario is a high-level statement of what feature or flow should be tested, such as “verify user login.” It does not include step-by-step detail. It helps ensure broad functional coverage before detailed case writing.

8. What is the difference between test scenario and test case?

A test scenario defines what to test at a high level. A test case explains how to test with detailed steps, data, and expected outcome. One scenario can have multiple related test cases.

9. What is a test plan?

A test plan is a formal document that defines testing scope, approach, resources, schedule, risks, and deliverables. It works as a roadmap for the QA team. It also includes entry and exit criteria for decision-making.

10. What is a defect (bug)?

A defect is any mismatch between expected and actual behavior of software. It may happen due to coding issues, requirement gaps, or integration problems. Defects are logged, prioritized, fixed, and retested.

11. What is severity and priority in defects?

Severity tells how much the defect affects system functionality from a technical viewpoint. Priority tells how urgently it should be fixed from a business/release viewpoint. Sometimes low-severity bugs can still be high-priority.

12. What is the defect life cycle?

A common defect lifecycle is New → Assigned → In Progress → Fixed → Retest → Closed. If fix fails in retest, defect becomes Reopened. Teams may also use statuses like Deferred, Duplicate, or Rejected.

13. What is smoke testing?

Smoke testing is a quick and broad check done on a new build to confirm key functionalities are working. It helps decide whether deeper testing should continue. It saves effort by catching major blockers early.

14. What is sanity testing?

Sanity testing is focused testing done after small fixes or minor changes. It validates whether the changed area works correctly and no obvious related issues are present. It is narrower in scope than smoke testing.

15. What is regression testing?

Regression testing checks whether recent code changes have broken existing working functionality. It is essential because software modules are connected and one change can impact other areas. It protects product stability during frequent releases.

16. What is retesting?

Retesting means executing previously failed test cases again after a defect is fixed. Its goal is to confirm the exact defect is resolved. Retesting is defect-specific and different from regression testing.

17. What is exploratory testing?

Exploratory testing is a simultaneous activity of learning, test design, and execution without strictly scripted steps. It depends on tester skill, curiosity, and domain understanding. It is highly useful for uncovering hidden and edge-case defects.

18. What is ad-hoc testing?

Ad-hoc testing is informal testing without documented test cases or planning. Testers quickly explore application behavior to find obvious issues. It is useful for quick checks but should not replace structured testing.

19. What is positive testing?

Positive testing verifies software behavior using valid input and expected user actions. It confirms normal business flows are functioning correctly. This is the basic layer of confidence in application functionality.

20. What is negative testing?

Negative testing validates how software behaves with invalid data, incorrect actions, or unexpected conditions. It ensures proper validation and graceful error handling. This improves stability and user experience.

21. What is black-box testing?

Black-box testing checks functionality without looking at internal code logic. The tester focuses on input, output, and expected behavior as per requirements. Most manual functional testing follows this approach.

22. What is white-box testing (high level)?

White-box testing evaluates internal code logic, branches, and execution paths. It is usually performed by developers or automation engineers with coding knowledge. It helps catch logic-level defects that may not appear in UI tests.

23. What is boundary value analysis?

Boundary value analysis focuses on testing edge values where defects commonly occur. For example, if valid input range is 1 to 100, boundary tests include 0, 1, 2, 99, 100, and 101. It gives strong coverage with limited tests.

24. What is equivalence partitioning?

Equivalence partitioning divides input values into groups expected to behave similarly (valid and invalid sets). One representative value from each group is tested instead of all values. This improves efficiency while maintaining quality coverage.

25. What is RTM (Requirement Traceability Matrix)?

RTM maps each requirement to corresponding test cases and sometimes defects. It ensures every requirement is covered and nothing important is missed. RTM is very useful during audits and requirement change analysis.

26. What are entry and exit criteria in testing?

Entry criteria are conditions that must be met before testing begins, such as stable build and approved requirements. Exit criteria are conditions for completing testing, such as critical defect closure and required pass rate. These criteria make release decisions objective.

27. What is UAT (User Acceptance Testing)?

UAT is performed by end users or business stakeholders to verify that software meets real business needs. It typically happens near final release stages. Successful UAT indicates product readiness for real-world use.

28. What should a good bug report include?

A strong bug report should contain title, environment, build version, exact steps, expected result, actual result, severity, priority, and supporting evidence like screenshots/logs. Good reporting reduces communication gaps. It helps developers fix issues faster and accurately.

29. How do you prioritize test cases when time is limited?

I start with smoke checks and critical business user journeys first. Then I cover high-risk modules, recent code changes, and historically unstable areas. Lower-risk scenarios are tested later or deferred with clear communication.

30. What qualities make a strong manual tester?

A strong manual tester is detail-oriented, curious, and user-focused. They communicate clearly, write high-quality defects, and understand business impact of issues. Good testers do not just find bugs, they improve product confidence.

Conclusion

To succeed in interviews, do not just memorize definitions—focus on understanding when and why each concept is used in real projects. When you explain basics with practical logic and clear communication, you automatically stand out from other candidates. Use these questions regularly for revision, and you will be better prepared for entry-level and early mid-level manual testing roles.