1. Role Expectations at 3 Years Experience (Manual Testing)
At 3 years of experience, interviewers expect you to function as a strong independent tester or module owner, not just a test executor.
What companies expect from you:
- Deep understanding of manual testing fundamentals
- Strong command of STLC & SDLC
- Independent requirement analysis
- Ability to design optimized test scenarios and test cases
- Clear and confident defect reporting
- Root Cause Analysis (RCA) mindset
- Active participation in Agile ceremonies
- Exposure to API testing, SQL, and performance awareness
- Ability to guide juniors and review test cases
- Clear communication with developers, leads, and product owners
At this level, interviews test how you think, prioritize, and prevent defects, not how well you memorize definitions.
2. Core Manual Testing Interview Questions & Structured Answers
Manual Testing Fundamentals (3-Year Level)
1. What is manual testing? Explain from your experience.
Manual testing is the process of validating application functionality without automation tools, focusing on business logic, user workflows, usability, and edge cases.
At 3 years, manual testing involves:
- Understanding business requirements
- Designing effective test scenarios
- Exploratory testing
- Identifying risk areas
- Preventing defect leakage to production
2. Why is manual testing still relevant even with automation?
Manual testing is still critical because:
- Exploratory testing requires human thinking
- UI/UX and usability issues are best identified manually
- New features initially depend on manual validation
- Domain-specific business rules need human judgment
- Automation scripts depend on stable manual test coverage
3. Explain SDLC and your role as a tester in each phase.
| SDLC Phase | Tester’s Role |
| Requirement Analysis | Identify gaps, ambiguities, risks |
| Design | Review flows, edge cases, testability |
| Development | Prepare test cases & test data |
| Testing | Execute tests, log defects |
| Deployment | Sanity testing & release validation |
| Maintenance | Regression testing & RCA |
4. What is STLC? Explain with real-time relevance.
STLC (Software Testing Life Cycle) focuses on testing activities:
- Requirement Analysis – Identify testable requirements and risks
- Test Planning – Define scope, effort, timelines, strategy
- Test Case Design – Positive, negative, and boundary cases
- Test Environment Setup – QA environment readiness
- Test Execution – Execute tests and log defects
- Test Closure – Metrics, reports, lessons learned
At 3 years, you are expected to optimize test coverage, not just increase test case count.
5. Difference between SDLC and STLC?
| SDLC | STLC |
| Complete software lifecycle | Testing lifecycle only |
| Covers business, dev, QA | QA-focused |
| Ends with maintenance | Ends with test closure |
3. Types of Manual Testing (Frequently Asked)
6. What types of testing have you performed?
- Functional Testing
- Smoke Testing
- Sanity Testing
- Regression Testing
- Integration Testing
- System Testing
- UAT support
7. What is Smoke Testing? Give an example.
Smoke testing validates critical functionalities to ensure build stability.
Example checks:
- Application launches
- Login works
- Dashboard loads
- No major crash
8. What is Sanity Testing?
Sanity testing validates specific fixes or enhancements after a new build.
Example:
- Verifying a fixed login issue after a patch
9. What is Regression Testing?
Regression testing ensures new changes do not break existing functionality.
Example:
- Testing checkout flow after adding a new payment option
10. Difference between Smoke and Sanity Testing?
| Smoke | Sanity |
| Broad coverage | Narrow coverage |
| Build validation | Fix validation |
| Performed initially | Performed after fix |
11. What is Integration Testing? Give a real example.
Integration testing verifies interaction between modules.
Example:
Order placement → Payment → Inventory update → Email notification
4. Test Case Design Interview Questions (3 Years)
12. How do you design test cases for a new feature?
My approach:
- Understand requirement & acceptance criteria
- Identify user flows
- Write positive scenarios
- Add negative and boundary cases
- Consider integration dependencies
- Ensure reusability for regression
13. What is a test case?
A test case is a documented set of steps used to validate a requirement.
Test Case Components:
- Test Case ID
- Test Scenario
- Steps
- Test Data
- Expected Result
- Actual Result
- Status
14. Sample Manual Test Case – Login
| Field | Value |
| Scenario | Invalid login |
| Steps | Enter valid username + wrong password |
| Expected Result | Error message displayed |
15. What is a test scenario?
A test scenario is a high-level testing idea.
Example:
Verify user login functionality
16. Difference between test case and test scenario?
- Test Scenario → What to test
- Test Case → How to test
17. Explain Boundary Value Analysis (BVA) with example.
Allowed amount range: 1,000 – 50,000
- Valid: 1,000, 1,001, 49,999, 50,000
- Invalid: 999, 50,001
18. What is Equivalence Partitioning?
Dividing input data into valid and invalid partitions to reduce test cases.
5. Defect Management & Bug Reporting
19. What is a defect?
A defect is a deviation between expected and actual system behavior.
20. Explain the Bug Life Cycle.
- New
- Assigned
- Open
- Fixed
- Retest
- Closed / Reopened
21. Severity vs Priority with example.
| Severity | Priority |
| Impact on system | Urgency of fix |
| Defined by QA | Defined by business |
Example:
Incorrect tax calculation → High severity, High priority
UI alignment issue → Low severity, Low priority
22. Sample Real-Time Bug Report
Title: Amount debited but order not created
Environment: QA
Steps:
1. Place an order
2. Complete payment
3. Check order history
Expected: Order created
Actual: No order displayed
Severity: Critical
Priority: High
23. What makes a good bug report?
- Clear and meaningful title
- Reproducible steps
- Expected vs actual result
- Screenshots / logs
- Correct severity and priority
6. Agile Manual Testing Interview Questions
24. What is Agile methodology?
Agile is an iterative development approach that focuses on:
- Early and continuous delivery
- Customer feedback
- Collaboration
- Flexibility to change
25. What is a Sprint?
A sprint is a fixed time-boxed iteration (usually 2 weeks) to deliver a set of features.
26. Agile ceremonies you participated in:
- Sprint Planning
- Daily Stand-ups
- Backlog Grooming
- Sprint Review
- Retrospective
27. Role of a manual tester in Agile.
- Understand user stories
- Clarify acceptance criteria
- Write test cases early
- Perform continuous testing within sprint
- Support demo & UAT
7. Scenario-Based Questions + RCA
28. A defect you logged was rejected. What will you do?
- Recheck requirement
- Reproduce the issue
- Share screenshots/logs
- Discuss professionally with developer
29. A critical defect escaped to production. What is your responsibility?
- Understand business impact
- Reproduce issue in lower environment
- Identify missed test scenario
- Perform RCA
- Add preventive test cases
30. Explain RCA with a real example.
Issue: Duplicate orders created
Root Cause: Retry scenario not tested
Preventive Action: Added retry and network-failure test cases
31. How do you test under tight deadlines?
- Risk-based prioritization
- Focus on critical business flows
- Smoke + targeted regression
- Clear communication of risks
8. Test Case Examples (Hands-On)
UI Test Case – Registration
Scenario: Mandatory field validation
Steps:
1. Leave email blank
2. Click Submit
Expected: Error message displayed
API Awareness Test Case (Manual – Postman)
- Method: POST
- Endpoint: /api/login
- Validate:
- Status code
- Error message
- Status code
Database Validation (SQL)
SELECT status
FROM orders
WHERE order_id = 78901;
Expected result: SUCCESS
Performance Awareness Scenario
- Multiple users login simultaneously
- Application should respond within acceptable time
9. Tools Knowledge (3 Years Manual Testing)
| Tool | Usage |
| Jira | Bug & story tracking |
| TestRail | Test case management |
| Postman | API testing basics |
| Selenium | Automation awareness |
| SQL | Backend data validation |
| JMeter | Performance awareness |
10. Domain Exposure Examples
Banking
- Fund transfers
- Interest calculation
- Account statements
Insurance
- Policy creation
- Premium calculation
- Claims processing
E-Commerce
- Cart
- Checkout
- Payment gateway
11. Common Mistakes at 3 Years Experience
- Giving fresher-level answers
- Not explaining end-to-end project flow
- Weak RCA explanations
- Poor defect justification
- Ignoring API and SQL basics
12. Quick Revision Cheat Sheet
- SDLC & STLC ✔
- Smoke vs Sanity ✔
- Regression testing ✔
- Test case design ✔
- Bug life cycle ✔
- Severity vs Priority ✔
- Agile basics ✔
- RCA mindset ✔
13. FAQs – 3 Years Manual Testing Interview Questions
Q: Is automation mandatory at 3 years?
Not mandatory, but awareness is expected.
Q: How deep should SQL knowledge be?
Basic SELECT queries and simple joins.
Q: What matters most at this level?
Project clarity, logical thinking, and defect prevention mindset.