3 Years Experience Interview Questions in Manual Testing -

1. Role Expectations at 3 Years Experience (Manual Testing)

At 3 years of experience, you are expected to perform as a strong independent QA engineer, sometimes acting as a module owner.

What interviewers expect at this level:

Deep understanding of manual testing concepts
Strong grip on STLC & SDLC
Independent requirement analysis
Ability to design high-quality, optimized test cases
Confident defect analysis and RCA
Active role in Agile ceremonies
Ability to guide juniors and review their work
Hands-on experience with Jira, TestRail
Exposure to API testing, SQL, and performance awareness
Clear communication with developers, leads, and product owners

At 3 years, interviews focus on decision-making, test coverage, and defect prevention, not just execution.

2. Core Manual Testing Interview Questions & Structured Answers

Manual Testing Fundamentals (3-Year Level)

1. How do you define manual testing at your experience level?

Manual testing at 3 years is not just executing test cases.
It is about:

Understanding business workflows
Designing effective scenarios
Identifying risk areas
Validating system behavior from an end-user perspective
Preventing defect leakage

2. Why is manual testing still critical in mature projects?

Manual testing remains critical because:

Exploratory testing needs human thinking
UI/UX issues cannot be fully automated
Business rules require domain understanding
Automation depends on stable manual coverage

3. Explain SDLC and your role as a tester in each phase.

SDLC Phase	Tester’s Responsibility
Requirement Analysis	Identify gaps, ambiguities, risks
Design	Review flows, edge cases
Development	Prepare test cases & data
Testing	Execute tests, log defects
Deployment	Sanity testing
Maintenance	Regression & RCA

4. What is STLC? Explain with real project relevance.

STLC focuses on testing activities:

Requirement Analysis – Identify test scenarios & risks
Test Planning – Scope, effort, strategy
Test Case Design – Positive, negative, boundary cases
Test Environment Setup – QA readiness
Test Execution – Execution & defect reporting
Test Closure – Metrics, lessons learned

At 3 years, you are expected to optimize test cases, not just increase count.

5. Difference between SDLC and STLC?

SDLC	STLC
Complete product lifecycle	Testing lifecycle
Covers business & dev	QA focused
Ends with maintenance	Ends with closure

3. Manual Testing Types (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 example.

Smoke testing validates critical functionalities to confirm build stability.

Example:

Application launch
Login
Dashboard loading

8. What is Sanity Testing?

Sanity testing validates specific fixes or enhancements after a new build.

9. What is Regression Testing?

Regression testing ensures that new changes do not impact existing functionality.

10. Difference between Smoke and Sanity Testing?

Smoke	Sanity
Broad coverage	Narrow coverage
Build stability	Fix validation
Initial testing	Post-fix testing

11. What is Integration Testing? Give real example.

Integration testing validates 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?

I follow:

Requirement understanding
User flow identification
Positive scenarios
Negative scenarios
Boundary value analysis
Integration dependencies
Reusability for regression

13. What is a test case?

A test case is a documented set of steps used to verify a requirement.

Components:

Test Case ID
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	Error message displayed

15. What is a test scenario?

A test scenario is a high-level idea of what to test.

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 with example.

Allowed amount: 1,000 – 50,000

Valid: 1,000, 1,001, 49,999, 50,000
Invalid: 999, 50,001

18. What is Equivalence Partitioning?

Dividing input values into valid and invalid groups 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 Bug Life Cycle.

New
Assigned
Open
Fixed
Retest
Closed / Reopened

21. Severity vs Priority with example.

Severity	Priority
Impact on system	Urgency of fix
Decided by QA	Decided by business

Example:
Wrong 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 shown

Severity: Critical

Priority: High

23. What makes a good defect report?

Clear and meaningful title
Reproducible steps
Expected vs actual result
Screenshots/logs
Correct severity & priority

6. Agile Manual Testing Interview Questions

24. What is Agile methodology?

Agile is an iterative development approach focusing on:

Early delivery
Continuous feedback
Collaboration
Adaptability

25. What is a Sprint?

A sprint is a fixed time-boxed iteration (usually 2 weeks).

26. Agile ceremonies you participated in:

Sprint Planning
Daily Stand-ups
Backlog Grooming
Sprint Review
Retrospective

27. Role of a manual tester in Agile.

Clarify user stories
Define acceptance criteria
Write test cases early
Continuous testing during sprint

7. Scenario-Based Questions + RCA

28. A defect you logged was rejected. What will you do?

Recheck requirement
Reproduce issue
Provide screenshots/logs
Discuss professionally with developer

29. A critical defect escaped to production. What is your responsibility?

Understand business impact
Reproduce issue
Identify missed test scenario
Perform RCA
Add preventive test cases

30. Explain RCA with real example.

Issue: Duplicate orders created
Root Cause: Retry scenario not tested
Preventive Action: Added retry & network-failure test cases

31. How do you test under tight timelines?

Risk-based prioritization
Focus on critical flows
Smoke + targeted regression
Clear risk communication

8. Test Case Examples (Hands-On)

UI Test Case – Registration

Scenario: Mandatory field validation