1 Year Experience Manual Testing Software Testing Interview Questions -

1. Role Expectations – Manual Tester with 1 Year Experience

At 1 year of experience, interviewers expect you to function as a Junior Software Test Engineer who can test assigned modules independently with minimal supervision.

What interviewers realistically expect:

Strong understanding of manual testing fundamentals
Clear knowledge of STLC and SDLC
Ability to write and execute test cases
Experience in functional, smoke, sanity, regression testing
Ability to log clear, reproducible defects
Basic understanding of Agile/Scrum
Hands-on usage of JIRA, TestRail
Exposure (not mastery) to API, SQL, automation awareness
Good communication with developers and test leads

2. Core Manual Testing Interview Questions & Structured Answers

1. What is manual testing?

Manual testing is the process of testing a software application without using automation tools, where test cases are executed manually to identify defects and verify requirements.

2. Why is manual testing still important?

Helps understand business logic
Useful for exploratory and usability testing
Required when UI changes frequently
Essential before automation is implemented

3. Explain SDLC and tester involvement

SDLC Phase	Tester Responsibility
Requirement	Requirement understanding & review
Design	Test scenario identification
Development	Test case preparation
Testing	Test execution & defect reporting
Deployment	Sanity testing
Maintenance	Regression testing

4. Explain STLC with real activity examples

STLC (Software Testing Life Cycle):

Requirement Analysis – Understand requirements, clarify doubts
Test Planning – Decide scope, approach, timelines
Test Case Design – Write test cases & scenarios
Environment Setup – Verify test environment readiness
Test Execution – Execute test cases, log defects
Test Closure – Prepare test summary report

At 1 year, interviewers expect you to explain what you actually did, not textbook definitions.

5. Difference between verification and validation

Verification	Validation
Static activity	Dynamic activity
Reviews & walkthroughs	Actual testing
Are we building it right?	Are we building the right product?

6. What types of testing have you performed?

Functional testing
Smoke testing
Sanity testing
Regression testing
System testing
Basic UAT support

7. Smoke testing vs Sanity testing

Smoke Testing	Sanity Testing
Build stability check	Bug-fix verification
Broad coverage	Narrow & focused
Done before detailed testing	Done after small changes

8. What is a test case?

A test case is a documented set of steps, test data, and expected results used to verify a specific requirement.

9. Components of a test case

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

10. How do you write good test cases?

Understand business flow
Cover positive and negative scenarios
Add boundary conditions
Write clear, reusable steps

11. What is a defect (bug)?

A defect is a difference between expected behavior and actual behavior of the application.

12. Explain defect life cycle

Status	Description
New	Defect logged by tester
Assigned	Assigned to developer
Open	Developer starts fixing
Fixed	Code fixed
Retest	Tester verifies
Closed	Issue resolved
Reopened	Issue still exists

13. Severity vs Priority

Severity	Priority
Impact on application	Urgency to fix
Decided by tester	Decided by product
App crash	Business deadline

14. What makes a good bug report?

Clear summary
Steps to reproduce
Actual vs expected result
Screenshots/logs
Correct severity & priority

3. Agile & Process Interview Questions

15. What is Agile testing?

Agile testing is continuous testing performed in short development cycles (sprints) with frequent feedback.

16. What is a sprint?

A sprint is a time-boxed iteration (1–2 weeks) where development and testing happen together.

17. Agile ceremonies you are aware of

Sprint planning
Daily stand-up
Sprint review
Retrospective

18. What is a user story?

A user story describes functionality from an end-user perspective.

Example:
As a user, I want to reset my password so that I can log in again.

19. What are acceptance criteria?

Acceptance criteria define conditions that must be met for a user story to be considered complete.

4. Scenario-Based Interview Questions with RCA

20. Login works for valid users but fails for some users. What will you check?

User status in DB
Role permissions
Configuration issues
Application logs

RCA Example:
Some users were marked inactive in the database.

21. A defect you logged is rejected. What do you do?

Re-test the scenario
Re-check requirements
Attach screenshots/logs
Discuss politely with developer

22. Application crashes during large file upload. RCA?

Missing file size validation
Memory limit exceeded
Timeout handling missing

23. Real-Time Defect Example

Issue: Submit button enabled without mandatory fields
Severity: Medium
RCA: Front-end validation missing

5. Real-Time Project Defects & RCA Examples

Banking Application

Defect: Incorrect balance after fund transfer
RCA: Cache not refreshed after DB update

Insurance Application

Defect: Policy created without document upload
RCA: Backend validation missing

ETL Project

Defect: Data mismatch in reports
RCA: Date format conversion issue

6. Test Case Examples

UI Test Case – Login Page

Field	Value
Scenario	Valid login
Steps	Enter valid credentials
Expected	Dashboard displayed

API Test Case – Login

Using Postman:

POST /login

{

“username”: “testuser”,

“password”: “pass123”

}

Database Validation (SQL)

SELECT status

FROM users

WHERE username = ‘testuser’;

Basic Performance Awareness

Using JMeter:

50 concurrent users
Response time < 3 seconds

7. Tools Knowledge (1 Year Manual Tester Level)

JIRA

Bug creation
Status updates
Attachments & comments

TestRail

Test case creation
Test execution tracking

Selenium

Automation awareness
Understanding why automation is used

SQL

Basic SELECT queries
Data validation

8. Domain Exposure (Basic)

Banking

Login
Account balance
Fund transfer

Insurance

Policy creation
Premium calculation

ETL

Source-to-target data validation

9. Common Mistakes at 1 Year Experience

Memorizing answers without examples
Poor bug descriptions
Confusing severity and priority
Not explaining real project work
Ignoring Agile basics

10. Quick Revision Cheat Sheet

SDLC vs STLC
Smoke vs Sanity
Defect life cycle
Severity vs Priority
Agile basics
SQL basics
RCA fundamentals