Prepare for your manual testing interview with this comprehensive guide featuring 30 essential questions and answers. Covering basic, intermediate, and advanced topics, these questions are tailored for freshers, candidates with 1-3 years of experience, and professionals with 3-6 years in manual testing.
Basic Manual Testing Interview Questions (1-10)
1. What is manual testing?
Manual testing is the process of manually executing test cases without using any automation tools to verify that the software application works as expected according to the requirements.
2. Why is manual testing needed?
Manual testing is needed for exploratory testing, usability testing, and ad-hoc testing where human judgment is crucial to identify user experience issues and complex scenarios that automation might miss.
3. Explain the difference between verification and validation in manual testing.
Verification is the process of checking if the product is built right (static analysis like reviews), while validation checks if the right product is built (dynamic testing through execution).
4. What is the Software Testing Life Cycle (STLC)?
STLC includes requirement analysis, test planning, test case design, test environment setup, test execution, and test closure activities.
5. What are test cases?
Test cases are detailed steps with input data, execution conditions, and expected results to verify specific functionality during manual testing.
6. Differentiate between test scenarios and test cases.
A test scenario is a high-level description of what to test, while a test case is a detailed set of steps to execute that scenario.
7. What is black-box testing?
Black-box testing focuses on testing the functionality of the application without knowledge of its internal code structure or implementation details.
8. What is a test plan?
A test plan is a document that outlines the scope, approach, resources, schedule, and deliverables for the testing activities.
9. Explain functional vs. non-functional testing.
Functional testing verifies specific functions work as per requirements, while non-functional testing checks aspects like performance, usability, and reliability.
10. What is exploratory testing?
Exploratory testing is an unscripted approach where testers explore the application simultaneously designing and executing tests based on their experience.
Intermediate Manual Testing Interview Questions (11-20)
11. List the roles and responsibilities of a manual tester.
Key responsibilities include analyzing requirements, creating test cases, executing tests, reporting defects, participating in review meetings, and ensuring test coverage.
12. Describe the manual testing process steps.
The process involves requirement analysis, test plan creation, test case design, test execution, defect reporting, evaluating exit criteria, and test closure.
13. What is a defect or bug?
A defect is any deviation from expected behavior in the software, identified during manual test execution.
14. Explain the bug life cycle.
Bug life cycle includes New, Assigned, Open, Fixed, Retest, Verified, Reopened, Closed, or Deferred states.
15. What skills are required for manual testing?
Required skills include analytical thinking, attention to detail, knowledge of SDLC/STLC, test case design, defect reporting, and familiarity with testing techniques.
16. What is test data?
Test data is the input data used during manual test execution to verify the application’s behavior under various conditions.
17. How do you prioritize test cases?
Prioritize based on risk, business impact, and critical functionality using the 80/20 rule where 20% of test cases cover 80% of the application.
18. What is regression testing?
Regression testing verifies that recent code changes have not adversely affected existing functionalities through re-execution of selected test cases.
19. Differentiate between severity and priority of a defect.
Severity measures the impact on the system (critical, major, minor), while priority indicates urgency for fixing (high, medium, low).
20. What is smoke testing?
Smoke testing is a preliminary test to check if the build is stable enough for further detailed manual testing.
Advanced Manual Testing Interview Questions (21-30)
21. Explain test closure activities.
Test closure involves collecting test completion matrices, preparing test summary reports, documenting lessons learned, and archiving test artifacts.
22. What is boundary value analysis?
Boundary value analysis is a technique testing boundaries between partitions of input data to find errors at edges of valid ranges.
23. Scenario: At Zoho, how would you test a new login feature manually?
I would review requirements, design test cases for valid/invalid credentials, execute functional tests, check UI/UX, test error messages, and verify session management across browsers.
24. What is equivalence partitioning?
Equivalence partitioning divides input data into partitions of equivalent classes where each class is expected to exhibit similar behavior.
25. Scenario: During testing at Paytm payment module, you find intermittent failures. How do you approach?
Reproduce the issue with detailed steps, capture screenshots/logs, test under different conditions (network, devices), categorize as intermittent, and report with evidence for developer investigation.
26. What are entry and exit criteria in testing?
Entry criteria include approved test plan and stable build; exit criteria include achieved test coverage, passed critical test cases, and acceptable defect rates.
27. Scenario: In a Salesforce app update at Adobe, requirements change mid-testing. What do you do?
Update test cases accordingly, get approval for changes, re-prioritize tests, execute impacted areas, and document the change impact on test results.
28. Explain risk-based testing.
Risk-based testing prioritizes testing activities based on the risk level of features, focusing more effort on high-risk, high-impact areas.
29. What is ad-hoc testing?
Ad-hoc testing is informal random testing without test cases to find defects missed by formal testing techniques.
30. Scenario: Testing Swiggy order placement shows UI glitch on mobile at Oracle-hosted app. How to report?
Document exact steps, device/browser details, screenshots/videos, expected vs. actual behavior, severity (high for UI), and steps to reproduce for clear defect logging.
