Manual Testing Interview Questions and Answers for 1 Year Experienced

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

At 1 year of experience, you are no longer treated as a fresher.
Interviewers expect you to be a junior QA engineer with real project exposure who understands how testing works in real time.

What companies expect at this level:

  • Clear understanding of manual testing fundamentals
  • Ability to read and understand requirements
  • Writing basic but correct test cases
  • Executing functional, smoke, sanity, and regression testing
  • Raising clear defect reports
  • Understanding STLC, SDLC, and Agile basics
  • Awareness of real-time project issues
  • Basic Root Cause Analysis (RCA)
  • Exposure to tools like Jira and TestRail
  • Basic SQL and API testing awareness
  • Good communication and learning attitude

At this stage, interviews test clarity, fundamentals, and honesty about experience.


2. Core Manual Testing Interview Questions & Structured Answers

Manual Testing Fundamentals (1-Year Level)

1. What is manual testing?

Manual testing is the process of verifying software functionality manually without using automation tools, by comparing actual results with expected results.

At 1 year, manual testing means:

  • Understanding what to test
  • Executing test cases correctly
  • Identifying visible defects

2. Why is manual testing important?

Manual testing is important because:

  • It validates business logic
  • It helps find usability issues
  • It is required for exploratory testing
  • Automation cannot replace human thinking

3. What types of testing have you performed?

  • Functional testing
  • Smoke testing
  • Sanity testing
  • Regression testing
  • Integration testing (basic)

4. What is functional testing?

Functional testing verifies that the application works according to the business requirements.

Examples:

  • Login functionality
  • Registration
  • Add to cart
  • Checkout

5. Smoke testing vs Sanity testing?

Smoke TestingSanity Testing
Checks build stabilityChecks specific fix
Broad coverageNarrow coverage
Performed on new buildPerformed after minor change

6. What is regression testing?

Regression testing ensures that existing functionality is not broken after:

  • Bug fixes
  • New features
  • Configuration changes

At 1 year, you should know how to:

  • Identify important regression scenarios
  • Execute regression checklist

7. Difference between verification and validation?

VerificationValidation
Static testingDynamic testing
Reviews & walkthroughsActual execution
Are we building it right?Are we building the right product?

3. SDLC & STLC Interview Questions (1 Year)

8. What is SDLC?

SDLC (Software Development Life Cycle) defines the stages involved in developing software.

PhaseDescription
RequirementBusiness needs
DesignSystem design
DevelopmentCoding
TestingValidation
DeploymentRelease
MaintenanceBug fixes

9. What is your role in SDLC as a tester?

  • Understand requirements
  • Write test cases
  • Execute test cases
  • Log defects
  • Support regression and UAT

10. What is STLC?

STLC (Software Testing Life Cycle) defines the testing-specific phases.

Steps:

  1. Requirement Analysis
  2. Test Planning
  3. Test Case Design
  4. Test Environment Setup
  5. Test Execution
  6. Test Closure

11. Difference between SDLC and STLC?

SDLCSTLC
Product lifecycleTesting lifecycle
Covers all activitiesQA-focused
Ends at maintenanceEnds at closure

4. Test Case Design Interview Questions (1 Year)

12. What is a test case?

A test case is a document containing:

  • Preconditions
  • Test steps
  • Test data
  • Expected result

Used to validate a requirement.


13. How do you write test cases?

I write test cases by:

  • Understanding the requirement
  • Identifying scenarios
  • Writing steps clearly
  • Defining expected results

14. Sample Manual Test Case – Login

FieldValue
Test Case IDTC_Login_01
ScenarioValid login
StepsEnter valid credentials
Expected ResultUser logs in successfully

15. What are positive and negative test cases?

  • Positive test case: Valid input, expected behavior
  • Negative test case: Invalid input, error handling

Example:

  • Negative: Wrong password
  • Negative: Empty username

16. What is boundary value analysis?

Boundary Value Analysis tests minimum and maximum values.

Example:

  • Password length allowed: 8–16
    Test values: 7, 8, 16, 17

5. Defect Management & Bug Reporting

17. What is a defect?

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


18. Defect life cycle.

  1. New
  2. Assigned
  3. Open
  4. Fixed
  5. Retest
  6. Closed / Reopened

19. Severity vs Priority.

SeverityPriority
Impact on systemUrgency to fix
Defined by QADefined by business

20. Sample Bug Report (Real Project Example)

Title: Login allowed with invalid password

Environment: QA

Steps:

1. Open login page

2. Enter valid username and invalid password

3. Click Login

Expected: Error message

Actual: User logged in

Severity: High

Priority: High


21. What is Root Cause Analysis (RCA)?

RCA identifies why a defect occurred.

At 1 year, RCA usually involves:

  • Missed test scenario
  • Requirement misunderstanding
  • Incorrect test data

6. Scenario-Based Interview Questions (1 Year)

22. Developer says “Not a bug.” What will you do?

  • Re-check requirement
  • Reproduce the issue
  • Share screenshots or steps
  • Discuss politely with developer

23. Bug found in UAT but not in QA. Why?

  • Environment difference
  • Test data difference
  • Missed scenario
  • Role/permission issue

24. Production bug reported. What is your action?

  • Inform lead
  • Try to reproduce
  • Help with RCA
  • Add regression test case

25. Real-Time RCA Example

Issue: Discount not applied for exact cart value
Root Cause: Boundary value not tested
Action: Added boundary test case


7. Tools Knowledge (1 Year Level)

26. What tools have you used?

  • Jira – defect tracking
  • TestRail – test case management
  • Postman – basic API testing
  • SQL – basic queries
  • Selenium – automation awareness

27. Sample SQL Query (Basic)

SELECT order_status, total_amount

FROM orders

WHERE order_id = 1234;


28. Why should manual testers know SQL?

  • Validate backend data
  • Verify transactions
  • Support defect analysis

29. What is API testing?

API testing verifies backend functionality without UI.

Example checks:

  • Status code
  • Response message

8. Agile & Manual Testing (1 Year)

30. What is Agile testing?

Agile testing follows iterative development, where testing happens in every sprint.


31. Role of tester in Agile.

  • Attend sprint planning
  • Understand acceptance criteria
  • Test user stories
  • Execute regression
  • Support sprint review

32. Agile ceremonies you attended:

  • Sprint Planning
  • Daily Stand-ups
  • Sprint Review
  • Retrospective

9. Domain Exposure (Basic Examples)

Banking

  • Login
  • Account summary

Insurance

  • Policy creation
  • Premium calculation

E-Commerce

  • Product search
  • Cart
  • Checkout

10. Common Mistakes at 1 Year Experience

  • Giving textbook definitions
  • No real project examples
  • Poor defect explanation
  • Not knowing defect life cycle
  • Ignoring basics of STLC

11. Quick Revision Cheat Sheet

  • Manual testing basics ✔
  • Functional testing ✔
  • SDLC & STLC ✔
  • Test case writing ✔
  • Defect life cycle ✔
  • Basic RCA ✔
  • Agile basics ✔

12. FAQs – Manual Testing Interview Questions and Answers for 1 Year Experienced

Q: Is automation required at 1 year?
No, only awareness is expected.

Q: Is SQL mandatory?
Basic SQL knowledge is preferred.

Q: What matters most in interviews?
Clarity, honesty, fundamentals, and real-time examples.

Leave a Comment

Your email address will not be published. Required fields are marked *