1. Scenario: Requirements are incomplete. How will you test?
I will analyze the application flow, refer to similar features, discuss with BA/Product Owner, and perform exploratory testing based on user perspective.
2. Scenario: Developer says the bug is not reproducible.
I will provide exact steps, screenshots, logs, environment details, and demonstrate the issue live if needed.
3. Scenario: Only 1 day is given to test a big feature.
I will focus on critical business flows, high-risk areas, and previously defect-prone modules.
4. Scenario: Client wants release today but there are open bugs.
I will explain the risk and impact of bugs. If they are low severity and business agrees, release can happen. Critical bugs should block release.
5. Scenario: No test data is available.
I will create dummy test data or request DB/admin access to prepare realistic data.
6. Scenario: Same bug appears again after fix.
I will reopen the defect with evidence and check if the fix was partial or regression occurred.
7. Scenario: UI is ready but backend is not.
I will test UI validations and use mock data or APIs to verify integration logic.
8. Scenario: Backend is ready but UI is not.
I will test APIs and database responses directly to validate business logic.
9. Scenario: A feature works in QA but fails in production.
I will compare environment configurations, data, and version differences to identify root cause.
10. Scenario: User reports a bug but you cannot reproduce it.
I will collect logs, device/browser details, and retry with similar conditions.
11. Scenario: Manager asks “Why are there so many bugs?”
I will explain complexity of feature, quality of requirements, and show test coverage with RTM.
12. Scenario: You find a bug very late in testing.
I will log it immediately, inform stakeholders, and analyze impact on release.
13. Scenario: Developer fixed bug but new bug appears.
I will log the new defect and perform regression testing.
14. Scenario: How will you test login when password policy changes?
I will test valid password, invalid length, special characters, and boundary values.
15. Scenario: How will you test file upload?
I will test valid file, invalid format, large file size, and network interruption.
16. Scenario: How will you test search feature?
I will test exact match, partial match, invalid input, special characters, and performance.
17. Scenario: How will you test logout?
I will test session invalidation, back button, and URL access after logout.
18. Scenario: How will you test payment feature manually?
I will test valid payment, insufficient balance, network failure, and duplicate transaction prevention.
19. Scenario: What if production bug occurs at night?
I will collect logs, reproduce in lower environment, and share root cause with team.
20. Scenario: What if two modules depend on each other?
I will test integration flow and validate data consistency between modules.