Manual Testing Interview Questions for All Experience Levels
This interview preparation guide covers 80 Manual Testing interview questions, divided into four experience levels: Freshers, 1–3 years, 3–6 years, and 6–12 years. The questions progress from basic testing concepts to real-time scenarios, test strategy, defect management, and QA leadership.
1. Manual Testing Interview Questions for Freshers (0 Experience)
What is software testing, and why is it important?
What is manual testing?
What is the difference between quality assurance (QA) and quality control (QC)?
What is the difference between verification and validation?
What is SDLC? Explain its phases.
What is STLC? Explain its phases.
What is the difference between SDLC and STLC?
What is a test case? What are its main components?
What is a test scenario? How is it different from a test case?
What is a bug or defect?
Explain the bug life cycle.
What is the difference between severity and priority?
What is the difference between functional and non-functional testing?
What is the difference between smoke testing and sanity testing?
What is regression testing?
What is retesting, and how is it different from regression testing?
What is exploratory testing?
What is the difference between positive and negative testing?
What is the difference between a test plan and a test strategy?
How would you test a login page manually?
2. Manual Testing Interview Questions for 1–3 Years of Experience
How do you analyze a requirement before starting testing?
How do you write effective test cases from a user story?
What is the difference between a test case, test scenario, and test script?
Explain boundary value analysis with a real-time example.
Explain equivalence partitioning with an example.
What is decision table testing, and when would you use it?
What is state transition testing? Give an example.
How do you decide which test cases should be included in regression testing?
What would you do if requirements were incomplete or unclear?
How do you report a defect in Jira?
What details should be included in a good bug report?
What would you do if a developer rejected your defect?
How do you differentiate an actual defect from an expected behavior?
How would you test an e-commerce website’s checkout process?
How would you test a password reset or forgot-password feature?
What is end-to-end testing? Give a real-time example.
How do you perform cross-browser testing?
What is risk-based testing, and how would you apply it?
How do you prioritize testing when you have limited time?
What testing activities do you perform during a sprint in Agile?
3. Manual Testing Interview Questions for 3–6 Years of Experience
How do you prepare a test plan for a new application or major feature?
How do you identify testing scope when requirements are large and complex?
How do you create and maintain an effective regression test suite?
How do you measure test coverage, and what are its limitations?
What is requirements traceability, and how do you maintain an RTM?
How do you conduct risk-based testing for a business-critical application?
How would you test a payment gateway involving multiple payment methods?
How would you test a file upload feature with different file types and sizes?
How would you investigate a defect that occurs intermittently?
How do you handle defects that cannot be reproduced in your environment?
How do you validate data consistency between the UI and database?
What database testing activities can be performed using SQL queries?
How would you test REST APIs manually using Postman?
How do you test an application when multiple teams deliver changes simultaneously?
How do you determine whether an application is ready for release?
What is defect leakage, and how can it be reduced?
How do you analyze escaped defects found in production?
How would you test an application after a major database migration?
How do you manage dependencies between test cases, services, and third-party systems?
How do you estimate testing effort for a new feature or release?
4. Manual Testing Interview Questions for 6–12 Years of Experience
How would you develop a QA strategy for a large enterprise application?
How do you establish quality standards across multiple teams and projects?
How do you determine the right balance between manual testing and automation?
How do you assess and communicate release risks to stakeholders?
What quality metrics do you track, and how do you ensure they lead to meaningful decisions?
How do you reduce defect leakage and improve production quality over time?
How would you handle a critical production defect discovered just before release?
How do you make a release recommendation when significant defects remain open?
How do you prioritize testing when deadlines are fixed and resources are limited?
How do you design a risk-based testing approach for a banking or financial application?
How do you evaluate whether the existing regression suite is effective?
How do you conduct root cause analysis for recurring defects?
How do you handle disagreements with developers, product managers, or business stakeholders about defects?
How do you improve a testing process that produces frequent escaped defects?
How do you plan QA activities for a project with distributed teams and multiple releases?
How do you ensure adequate test coverage when requirements change frequently?
How do you mentor junior testers and assess their testing skills?
How do you manage dependencies on third-party services and unstable test environments?
How do you present a quality assessment and release-readiness report to senior management?
Describe a major quality issue you handled. What decisions did you make, and what did you learn?
30 Real-Time Manual Testing Interview Scenario Questions
These questions are based on real project situations commonly used in Manual Testing interviews, from freshers to experienced QA professionals. Focus on how you would test, investigate defects, identify edge cases, and make testing decisions.
1. Login and Authentication Scenarios
1. Login Page: You enter a valid username and password, but the application does not allow you to log in. How would you investigate and test this issue?
2. Forgot Password: A user clicks the forgot-password link but does not receive the reset email. What scenarios would you test?
3. Account Lockout: After five incorrect password attempts, the account should be locked. How would you verify this functionality?
4. Session Timeout: A user leaves the application idle for 15 minutes and then tries to submit a form. What should happen, and how would you test it?
5. Remember Me: A user selects the “Remember Me” checkbox, closes the browser, and opens the application again. What scenarios would you verify?
2. E-commerce Application Scenarios
6. Shopping Cart: A customer adds three products to the cart, changes the quantity of one product, and removes another. How would you verify the cart and total amount?
7. Price Mismatch: A product displays ₹1,000 on its details page but ₹1,200 in the shopping cart. How would you investigate the issue?
8. Out-of-Stock Product: A product becomes out of stock after the customer adds it to the cart. What should happen when the customer tries to place the order?
9. Discount Coupon: A coupon offers a 20% discount on eligible products. How would you test valid, invalid, expired, and partially eligible coupon scenarios?
10. Order Placement: The customer clicks “Place Order,” but the page keeps loading. The customer clicks the button again and receives two order confirmations. How would you test and report this issue?
3. Payment and Banking Scenarios
11. Payment Failure: Money is deducted from the customer’s bank account, but the application displays “Payment Failed.” How would you investigate this scenario?
12. Duplicate Payment: A customer clicks the Pay button twice and is charged twice for the same order. How would you reproduce, document, and verify the fix?
13. ATM Withdrawal: A customer requests ₹5,000 from an ATM, but the machine dispenses only ₹3,000. What validations and test scenarios would you consider?
14. Money Transfer: A user transfers money to another account, but the sender’s balance decreases while the receiver’s balance remains unchanged. How would you investigate it?
15. Transaction History: A successful payment is displayed in the confirmation message but is missing from the transaction history. What would you verify?
4. Form and Data Validation Scenarios
16. Registration Form: A registration form accepts an invalid email address, such as
user@. How would you test email validation?17. Mandatory Fields: A form contains ten fields, five of which are mandatory. How would you verify that the form handles missing values correctly?
18. File Upload: An application allows users to upload documents up to 5 MB. How would you test file size, file type, empty files, and invalid files?
19. Search Functionality: A search feature returns no results for a product that exists in the database. What possible causes would you investigate?
20. Duplicate Registration: Two users register using the same email address at nearly the same time. What should the expected behavior be, and how would you test it?
5. Real-Time Project and Defect Scenarios
21. Requirement Changes: A requirement changes two days before the release. How would you identify the affected test cases and decide what to retest?
22. Developer Rejects a Bug: You report a defect, but the developer says it is working as designed. How would you handle the disagreement?
23. Intermittent Defect: A defect occurs only sometimes and cannot be reproduced consistently. How would you investigate it?
24. Production Bug: A critical defect is reported by a customer after the application goes live. What steps would you take as a QA tester?
25. Limited Testing Time: You have 100 test cases to execute, but only two hours remain before release. How would you prioritize your testing?
6. Mobile, API, and Advanced Scenarios
26. Mobile Network Interruption: A user submits a payment using a mobile application, and the internet connection drops during processing. What scenarios would you test?
27. Cross-Browser Issue: A website works correctly in Chrome but the Submit button does not work in Firefox. How would you investigate and report the defect?
28. API and UI Mismatch: An API response returns the correct customer details, but the UI displays incorrect information. How would you isolate the problem?
29. Database Mismatch: A user updates their address successfully, and the UI displays the new address, but the database contains the old address. How would you validate the issue?
30. Release Readiness: Your testing is complete, but three medium-severity defects remain open. How would you assess the risk and communicate whether the application is ready for release?