1. Overview: Why Manual Software Testing Still Matters
Despite the rise of automation, manual software testing remains the backbone of quality assurance. Every project—whether Agile, DevOps, automation-heavy, or AI-driven—still begins with manual testing.
Companies rely on manual testers to:
- Understand business requirements deeply
- Identify edge cases and usability issues
- Perform exploratory and scenario-based testing
- Validate features before automation
- Support UAT, production issues, and RCA
That is why manual software testing interview questions focus heavily on:
- Core testing fundamentals
- Real-time scenario handling
- Test case writing
- Defect reporting and RCA
- Domain understanding
2. Manual Software Testing Interview Questions & Answers (Basic → Advanced)
🔹 BASIC MANUAL SOFTWARE TESTING INTERVIEW QUESTIONS
Q1. What is manual testing?
Answer:
Manual testing is the process of testing software without using automation tools, where testers execute test cases manually to identify defects.
Q2. Why is manual testing important?
- Understands user behavior
- Finds UI/UX issues
- Required for exploratory testing
- Foundation for automation
Q3. What is software testing?
Answer:
Software testing verifies and validates that a software application meets functional, non-functional, and business requirements.
Q4. Difference between verification and validation?
| Verification | Validation |
| Are we building the product right? | Are we building the right product? |
| Static testing | Dynamic testing |
| Reviews | Test execution |
Q5. What is a test case?
Answer:
A test case is a document containing preconditions, steps, test data, and expected results to verify a requirement.
Q6. What is a defect or bug?
Answer:
A defect is a mismatch between expected behavior and actual behavior of the application.
🔹 TYPES OF MANUAL TESTING QUESTIONS
Q7. What are different types of testing?
- Functional testing
- Smoke testing
- Sanity testing
- Regression testing
- Integration testing
- System testing
- UAT
Q8. What is smoke testing?
Answer:
Smoke testing verifies whether the critical functionalities of a build are working before detailed testing.
Q9. What is sanity testing?
Answer:
Sanity testing ensures that specific functionality or bug fixes work correctly after minor changes.
Q10. Difference between smoke and sanity testing?
| Smoke | Sanity |
| Broad coverage | Narrow coverage |
| Build verification | Feature verification |
| Initial testing | After bug fix |
Q11. What is regression testing?
Answer:
Regression testing ensures that existing functionality is not broken after new changes or fixes.
Q12. Difference between retesting and regression?
| Retesting | Regression |
| Tests fixed defects | Tests existing features |
| Bug-specific | Feature-based |
🔹 TEST DESIGN TECHNIQUES (MANUAL)
Q13. What is boundary value analysis?
Answer:
Testing at minimum, maximum, and boundary values, as errors often occur at edges.
Example:
Age (18–60) → test 17, 18, 19, 59, 60, 61
Q14. What is equivalence partitioning?
Answer:
Dividing inputs into valid and invalid groups and testing one value from each group.
Q15. What is negative testing?
Answer:
Negative testing checks system behavior with invalid or unexpected inputs.
3. Scenario-Based Manual Software Testing Interview Questions
Q16. Login works for some users but not for others. How will you test?
Thought Process:
- Validate user account status
- Check credentials
- Test across browsers/devices
- Verify network issues
Conclusion: Likely a data or role-based issue.
Q17. Forgot-password email is not received.
Steps:
- Check correct email entered
- Verify spam/junk folder
- Validate success message
- Raise defect if needed
Q18. Application crashes after clicking Submit.
Approach:
- Reproduce consistently
- Check input values
- Capture screenshots/logs
- Log defect with steps
Q19. UI shows success message but data is not saved.
Checks:
- Backend response
- Database update
- Error handling
Q20. Bug occurs only in production.
Possible Causes:
- Data differences
- Configuration mismatch
- Load issues
4. Real-Time Project Scenario Questions (Manual Testing)
Q21. Payment successful but order not created.
Impact: Revenue loss
Steps to Debug:
- Verify payment confirmation
- Check order history
- Validate DB entry
- Inform backend team
Severity: Critical
Priority: High
Q22. Cart total mismatch in eCommerce application.
Possible Causes:
- Discount calculation
- Tax logic
- Rounding issues
Q23. Banking app shows wrong balance.
Checks:
- Debit/credit sequence
- Pending transactions
- Rounding precision
Q24. Video buffering in OTT platform.
Reasons:
- Network bandwidth
- CDN issues
- Device limitations
5. Test Case Writing Examples (Manual Testing)
🔹 Login Test Case Example
| Field | Description |
| Test Case ID | TC_Login_01 |
| Scenario | Valid login |
| Preconditions | User registered |
| Steps | Enter valid credentials |
| Expected Result | User logged in |
🔹 Payment Test Case Example
| Scenario | Expected Result |
| Successful payment | Order created |
| Failed payment | Error shown |
| Timeout | Retry option |
6. Bug Report Example + Root Cause Analysis (RCA)
Bug Example
Title: Login fails with valid credentials
Severity: High
Priority: Medium
RCA
- Incorrect backend validation
- Missing error handling
Fix: Code update + retesting
7. SDLC, STLC & Agile Concepts (Manual Tester View)
SDLC (Software Development Life Cycle)
- Requirement analysis
- Design
- Development
- Testing
- Deployment
- Maintenance
STLC (Software Testing Life Cycle)
- Requirement analysis
- Test planning
- Test case design
- Test execution
- Defect tracking
- Test closure
Agile Testing
- Sprint-based development
- Continuous testing
- Daily stand-ups
- Retrospectives
8. Tools Used in Manual Software Testing
| Tool | Purpose |
| Jira | Bug tracking |
| TestRail | Test case management |
| Selenium | Automation (future scope) |
| Postman | API validation |
| Jenkins | CI/CD awareness |
9. Domain-Based Manual Testing Examples
Banking
- Login
- Balance check
- Transactions
Insurance
- Policy creation
- Premium calculation
E-Commerce
- Cart
- Payment
- Discounts
Healthcare
- Data accuracy
- Privacy compliance
10. Quick Revision Sheet – Manual Software Testing
| Area | Focus |
| Manual Testing | Fundamentals |
| Scenarios | Real-world |
| Test Cases | Clarity |
| Bugs | Severity/Priority |
| Agile | Collaboration |
11. FAQs – Manual Software Testing Interview Questions
Q. Is manual testing still a good career?
Yes. Manual testing is the foundation of QA, and strong manual testers grow into automation, API, or lead roles.
Q. How many questions should I prepare?
Prepare 70–120 manual software testing interview questions including scenarios.