1 Year Experience Manual Testing Interview Questions -

1. Role Expectations at 1 Year Experience (Manual Testing)

At 1 year of experience, interviewers consider you a junior-to-mid level QA engineer who has already worked on at least one real project.

What companies expect from you:

Strong understanding of manual testing fundamentals
Ability to read & understand requirements
Write and execute clear test cases
Log high-quality defects
Understand STLC, SDLC, Agile
Work with tools like Jira, TestRail
Basic knowledge of API & SQL (even if mostly manual)
Clear communication with developers and leads

At this level, interviewers check clarity of thinking, not automation depth.

2. Core Manual Testing Interview Questions & Answers (1 Year)

Fundamentals of Manual Testing

1. What is manual testing?

Manual testing is the process of verifying software functionality without using automation tools, by executing test cases manually to identify defects.

It focuses on:

User behavior
Business flows
Usability
Visual and logical correctness

2. Why is manual testing important even today?

Manual testing is important because:

Exploratory testing needs human thinking
UI/UX issues are better identified manually
Early project stages rely heavily on manual testing
Automation cannot replace domain understanding

3. What is SDLC? Explain its phases.

SDLC (Software Development Life Cycle) defines how software is built:

Phase	Description
Requirement	Business needs are defined
Design	Architecture & UI are designed
Development	Code is written
Testing	Application is validated
Deployment	Software is released
Maintenance	Fixes & enhancements

4. What is STLC?

STLC (Software Testing Life Cycle) focuses only on testing activities.

Phases:

Requirement Analysis
Test Planning
Test Case Design
Test Environment Setup
Test Execution
Test Closure

5. Difference between SDLC and STLC?

SDLC	STLC
Full software lifecycle	Testing lifecycle
Business + dev + QA	QA focused
Ends at maintenance	Ends at 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?

Smoke testing checks critical functionalities to verify build stability.

Example:

Login
Dashboard loading
Core navigation

8. What is Sanity Testing?

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

9. What is Regression Testing?

Regression testing ensures new changes do not break existing functionality.

10. Difference between Smoke and Sanity?

Smoke	Sanity
Broad coverage	Narrow coverage
Build validation	Change validation
Done before regression	Done after fix

4. Test Case Design Interview Questions

11. What is a test case?

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

Test Case Components:

Test Case ID
Scenario
Steps
Test Data
Expected Result
Actual Result
Status

12. Sample Manual Test Case – Login

Field	Value
Scenario	Valid login
Steps	Enter valid username & password
Expected	User logged in successfully

13. What is a test scenario?

A test scenario is a high-level testing idea.

Example:

Verify login functionality

14. Difference between test case and test scenario?

Scenario → What to test
Test case → How to test

15. What is Boundary Value Analysis (BVA)?

BVA focuses on testing edge values.

Example:
If allowed age = 18–60
Test: 17, 18, 19, 59, 60, 61

16. What is Equivalence Partitioning?

Dividing input data into valid and invalid groups to reduce test cases.

5. Defect Management & Bug Reporting

17. What is a defect?

A defect is a deviation between expected and actual behavior.

18. What is a bug life cycle?

New
Assigned
Open
Fixed
Retest
Closed / Reopened

19. Severity vs Priority

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

20. Sample Real-Time Bug Report

Title: Submit button not working on registration page

Environment: QA

Steps:

1. Open registration page

2. Fill all mandatory fields

3. Click Submit

Expected: Form submitted

Actual: No response

Severity: High

Priority: High

21. What makes a good bug report?

Clear title
Reproducible steps
Screenshots/logs
Correct severity & priority

6. Agile Manual Testing Questions

22. What is Agile?

Agile is an iterative methodology that delivers software in small increments with continuous feedback.

23. What is a Sprint?

A sprint is a fixed time period (1–3 weeks) to deliver a set of features.

24. Agile ceremonies you attended:

Sprint Planning
Daily Stand-ups
Sprint Review
Retrospective

25. Role of manual tester in Agile:

Understand user stories
Clarify acceptance criteria
Write test cases early
Continuous testing

7. Scenario-Based Manual Testing Questions + RCA

26. A defect you logged is rejected. What will you do?

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

27. A bug escaped to production. What is your responsibility?

Understand issue
Identify missed test scenario
Perform RCA
Add preventive test cases

28. Explain RCA with example.

Issue: Payment failed for some users
Root Cause: Negative scenario not tested
Fix: Added boundary & error-handling test cases

29. How do you handle tight deadlines?

Prioritize critical scenarios
Focus on business flows
Communicate risks clearly

8. Test Case Examples (Real Project)

UI Test Case – Registration

Scenario: Mandatory field validation