Here’s your full Manual QA Interview Answer Key (Q1–30) in Mock Interview Preparation
Format — clean, crisp, and bullet-pointed for easy memorization or revision. You can copy
this into a Word/Google Doc to turn it into your final prep guide or PDF.
✅ Manual QA Interview Answer Key (Q1–
Q30) – Mock Interview Format
1. What is software testing and why is it important?
• Verifies software works as intended
• Catches bugs early
• Improves reliability, user trust, and compliance
2. Difference between verification and validation
• Verification: Are we building the product right? (Design/spec review)
• Validation: Are we building the right product? (Actual testing)
3. Types of software testing
• Functional, Non-Functional
• Manual, Automation
• Unit, Integration, System, Acceptance
• Regression, Smoke, Sanity
4. Smoke vs Sanity vs Regression
• Smoke: Basic stability test after build
• Sanity: Verify a specific fix or feature
• Regression: Re-test old features after changes
5. What is exploratory testing?
• Unscripted testing based on intuition
• Done when time/docs are limited
• Good for uncovering hidden bugs
6. Key components of a test case
• ID, Title
• Preconditions
• Test Steps & Data
• Expected vs Actual Result
• Status, Comments
7. BVA vs Equivalence Partitioning
• BVA (Boundary Value Analysis): Test min/max and edge cases
• EP (Equivalence Partitioning): Divide data into valid/invalid partitions
8. Test cases for a login page
• Valid login
• Invalid username/password
• Blank fields
• SQL injection
• Forgot password
• Password masking
9. Test Scenario vs Test Case
• Scenario: High-level objective ("Test login")
• Case: Detailed steps to execute scenario
10. How to ensure full test coverage
• Trace to requirements
• Include edge/negative/positive flows
• Use BVA, EP
• Review test plan with dev/BA
11. What makes a good bug report?
• Clear title and ID
• Reproduction steps
• Expected vs Actual result
• Severity/Priority
• Attach screenshots/logs
12. Severity vs Priority
• Severity: Technical impact
• Priority: Business urgency
13. Bug tracking tools
• JIRA
• Azure DevOps
• Bugzilla, Trello (for simple workflows)
14. Bug life cycle
• New → Assigned → Open → Fixed → Retest → Verified → Closed
• May also be: Reopened, Deferred, Duplicate
15. Developer disagrees with bug?
• Reproduce and re-confirm
• Attach evidence
• Escalate with context if needed
16. Steps to reproduce customer issue
• Get steps/environment
• Use session logs or replay tools
• Reproduce and document
17. Wireshark/CleverTap usage
• Wireshark: Packet-level/API debugging
• CleverTap: Session replays, user behavior
18. Resolved a production issue example
• Used logs/session to trace issue
• Validated root cause
• Retested and closed after fix
19. Bug not reproducible?
• Try variations or different setups
• Ask for additional info/screenshots
• Mark with notes and defer if needed
20. How to escalate unresolved issues
• Use comments and assign to leads
• Mark severity clearly
• Follow up regularly
21. Gathering requirements
• Attend grooming/standups
• Review Figma, BRDs
• Clarify via call/email
• Document understanding
22. Explaining technical issues simply
• Use analogies
• Focus on what broke and user impact
• Skip jargon
23. Coordinating with teams
• Sync via standups/JIRA
• Raise risks/blockers early
• Align on priorities
24. Cross-team bug handling
• One central ticket
• Assign roles per team
• Sync meeting if urgent
25. Conflicting priorities
• Clarify with PO/BA
• Prioritize based on risk
• Document decisions
26. Critical bug before release
• Escalate immediately
• Support rollback/hotfix
• Retest after fix
• Delay release if needed
27. Limited time to test
• Do sanity/smoke
• Focus on core features
• Log untested parts
28. Business ignores critical bug
• Show user/business impact
• Suggest phased fix
• Escalate with data
29. Triage multiple escalations
• Sort by severity
• Handle blockers first
• Communicate progress
30. Blocked by incomplete requirements
• Raise blocker
• Test available scope
• Document assumptions
