Scenario-Based Manual Testing Interview Questions & Answers
1. Developer says bug is not reproducible. What will you do?
I will recheck the steps carefully, verify test data, environment, browser, and build version. I will record screen or take screenshots and provide exact steps with logs to developer.
2. A defect is fixed but still failing. What will you do?
I will do retesting with same steps. If still failing, I will reopen the bug with evidence and mention build number.
3. Requirement is unclear. How will you test?
I will clarify with BA or developer. Meanwhile, I will prepare test cases based on assumptions and confirm with team.
4. How will you test Login page manually?
Valid username & password, invalid username, invalid password, blank fields, boundary values, error messages, UI alignment.
5. Build is given late and release is today. What will you do?
I will perform smoke testing on critical functionalities and report high severity bugs immediately.
6. Developer says it works on his machine. What will you do?
I will check environment difference, browser version, data and configuration. I will share screenshots or video proof.
7. Bug found in production. Who is responsible?
It is a team responsibility. I will analyze why it was missed and improve test coverage.
8. How will you decide test cases without requirements?
I will use exploratory testing and past experience to create scenarios and confirm with stakeholders.
9. What will you do if developer rejects your bug?
I will recheck, provide proper steps, screenshots, logs and explain impact clearly.
10. How will you test a form manually?
Field validations, mandatory fields, boundary values, negative inputs, error messages, UI and data saving.
11. What will you do if you have no test cases?
I will perform exploratory testing and create test cases simultaneously.
12. How will you test Search functionality?
Valid search, invalid search, partial keyword, special characters, blank search, performance.
13. A feature works but UI is ugly. Is it a bug?
Yes, it is usability defect and should be reported.
14. What will you do if same bug keeps coming?
I will check root cause, improve regression test cases and discuss with dev team.
15. How will you test a payment module manually?
Valid payment, invalid card, expired card, wrong CVV, network failure, duplicate payment, receipt generation.
16. How will you test error messages?
Check correctness, clarity, grammar and if it guides user properly.
17. What will you do if tester and developer disagree?
I will show proof and discuss politely. Final decision will be taken by lead or product owner.
18. How will you test file upload?
Valid file, invalid format, large size, zero size, cancel upload, upload interruption.
19. How will you test logout functionality?
Click logout, check session end, browser back button, direct URL access.
20. What is your approach when you get new module?
Understand requirement, explore application, write test cases, perform testing, log defects, do regression.