1. What is Software Testing?

Answer: It is the process of checking if the software works as expected and

finding bugs.

2. What is the difference between Verification and Validation?

Answer:

 Verification: Are we building the product right?

 Validation: Are we building the right product?

3. What is a Test Case?

Answer: A set of steps and conditions to test a specific function of the

application.

4. What is the difference between Bug, Defect, and Error?

Answer:

 Error: Mistake by developer.

 Defect/Bug: Found by tester in testing.

 Failure: When the defect appears during execution.

5. What is Black Box Testing?

Answer: Testing without looking at the internal code, only checking the input
and output.

6. What is a Test Plan?

Answer: A document that describes the scope, approach, and schedule of

testing activities.

7. What is Regression Testing?

Answer: Testing to ensure that new changes didn’t break existing features.

8. What is the SDLC and STLC?

Answer:

 SDLC: Software Development Life Cycle.

 STLC: Software Testing Life Cycle.

9. What is Severity and Priority?

Answer:

 Severity: How serious the bug is.

 Priority: How soon it should be fixed.

10. What is the Difference Between Functional and Non-functional

Testing?

Answer:

 Functional: Checks features (e.g., login).

 Non-functional: Checks performance, usability, etc.

11. What is a Test Scenario?

Answer: A high-level idea of what to test, like "Verify login functionality."

12. What is a Test Case ID?

Answer: A unique identifier given to each test case for easy tracking.

13. What is Exploratory Testing?

Answer: Testing without test cases, exploring the application to find defects.
14. What is Ad-hoc Testing?

Answer: Informal testing without planning or documentation.

15. What is a Use Case?

Answer: A description of how a user uses the system to achieve a goal.

16. What is the Difference Between Smoke and Sanity Testing?

Answer:

 Smoke: Basic tests to check if the build is stable.

 Sanity: Specific tests to verify new functionality works.

17. What is Boundary Value Analysis?

Answer: Testing at the edges (min, max values) of input ranges.

18. What is Equivalence Partitioning?

Answer: Dividing inputs into valid and invalid groups to reduce test cases.

19. What is Defect Life Cycle?

Answer: The stages a defect goes through: New → Assigned → Fixed →

Retested → Closed.

20. What is a Requirement Traceability Matrix (RTM)?

Answer: A document that maps test cases to requirements to ensure

coverage.

21. What is Static Testing?

Answer: Testing without executing the code – like reviewing documents.

22. What is Dynamic Testing?

Answer: Testing by executing the code or application.

23. What is the Difference Between Retesting and Regression

Testing?

Answer:

 Retesting: Checking if a specific bug is fixed.

 Regression: Checking if other features still work.

24. What is Compatibility Testing?

Answer: Checking if the app works on different browsers, devices, or OS.

25. What is Usability Testing?

Answer: Checking how user-friendly and easy to use the application is.

26. What is End-to-End Testing?

Answer: Testing the entire application flow from start to finish to ensure
everything works together.

27. What is Acceptance Testing?

Answer: Testing done to confirm the system meets business requirements,

often done by the client.

28. What is a Test Data?

Answer: Input data used during testing to check application behavior.

29. What is the role of a Manual Tester?

Answer: To find bugs by manually testing software and ensuring it works as
expected.

30. What is the Difference Between QA and QC?

Answer:

 QA (Quality Assurance): Process-oriented (prevention).

 QC (Quality Control): Product-oriented (detection).

31. What is Installation Testing?

Answer: Testing the installation process of the application.

32. What is Localization Testing?

Answer: Checking if the application works correctly in different languages

and regions.

33. What is Alpha Testing?

Answer: Testing done by internal teams before releasing the product.

34. What is Beta Testing?

Answer: Testing done by actual users in a real environment before final

release.

35. What is GUI Testing?

Answer: Testing the graphical user interface for correctness, layout, and
design.

36. What is Load Testing?

Answer: Testing how the system behaves under expected load.

37. What is Stress Testing?

Answer: Testing the system under extreme load to check its breaking point.

38. What is Soak Testing?

Answer: Running the system for a long time to check stability and memory
leaks.

39. What is a Test Environment?

Answer: A setup of software and hardware where testing is performed.

40. What are Entry and Exit Criteria in Testing?

Answer:

 Entry: Conditions to start testing.

 Exit: Conditions to stop testing.

1. What is STLC?

Answer: STLC stands for Software Testing Life Cycle. It is a sequence of

activities performed during the testing process to ensure software quality.

2. What are the phases of STLC?

Answer:

1. Requirement Analysis

2. Test Planning

3. Test Case Design

4. Test Environment Setup

5. Test Execution
 6. Test Closure

3. What happens in the Requirement Analysis phase?

Answer: Testers understand and analyze the requirements to identify what

needs to be tested.

4. What is done in the Test Planning phase?

Answer: A test strategy is created, and resources, timelines, and

responsibilities are defined.

5. What is created in the Test Case Design phase?

Answer: Detailed test cases and test data are prepared based on
requirements.

6. What is the purpose of Test Environment Setup?

Answer: To prepare the hardware and software environment where tests will
be executed.

7. What happens during Test Execution?

Answer: Test cases are run, and results are recorded. Defects are reported if
any.

8. What is Test Closure?

Answer: Final phase where test results are analyzed, reports are created,
and lessons learned are documented.

9. Is STLC a part of SDLC?

Answer: Yes, STLC is a subset of SDLC focused on testing activities.

10. Who is involved in STLC?

Answer: Mainly testers, but also developers, project managers, and

business analysts during reviews or defect discussions.

1. What is a Defect Life Cycle?

Answer:
It is the process a defect goes through from discovery to closure during
testing.

2. What are the common stages of the Defect Life Cycle?

Answer:

1. New

2. Assigned

3. Open

4. Fixed

5. Retest

6. Verified

7. Closed

8. (Optional: Reopened, Deferred, Rejected)

3. What happens in the "New" status?

Answer:
Tester finds a bug and logs it – the defect is in the "New" state.

4. What is the "Assigned" status?

Answer:
The bug is assigned to a developer for fixing.
5. What is the "Fixed" status?

Answer:
Developer has fixed the defect and marked it as "Fixed" for testing.

6. What is "Retest"?

Answer:
Tester retests the fixed defect to confirm if it is resolved.

7. What is "Verified"?

Answer:
Tester confirms the defect is resolved and marks it as verified.

8. What is "Closed"?

Answer:
The verified defect is closed after final approval.

9. What is a "Reopened" defect?

Answer:
If the issue still exists after a fix, the tester reopens the defect.

10. What is a "Deferred" defect?

Answer:
The defect is postponed for future release due to low priority or other
reasons.

11. What is a "Rejected" defect?

Answer:
The developer denies it as a bug due to invalid, duplicate, or not
reproducible issue.
1. What is Quality Assurance (QA)?

Answer: QA focuses on improving the software development process to

prevent defects.

2. What is Quality Control (QC)?

Answer: QC is about finding defects in the actual product through testing.

3. What is Severity and Priority in Defects?

Answer:

 Severity: Impact of the defect on the system.

 Priority: Urgency of fixing the defect.

4. What is a Test Plan?

Answer: A document that describes the scope, approach, resources, and

schedule of testing activities.

5. Difference between Functional and Non-functional Testing?

Answer:

 Functional: Tests what the system does (features, business logic).

 Non-functional: Tests how the system performs (speed, usability,

security).

🔹 Test Techniques & Types

6. What is Black Box Testing?

Answer: Testing without looking at the internal code – focus is on input and
output.
7. What is White Box Testing?

Answer: Testing with knowledge of the internal code structure.

8. What is Integration Testing?

Answer: Testing the interaction between integrated modules or

components.

9. What is System Testing?

Answer: Testing the complete system as a whole to ensure it meets the

requirements.

10. What is Regression Testing?

Answer: Testing old functionalities after changes to ensure nothing is

broken.

🔹 Test Artifacts & Documentation

11. What is a Test Case?

Answer: A set of actions and expected results used to verify a feature or

functionality.

12. What is a Test Suite?

Answer: A collection of test cases grouped together for testing a module or

system.

13. What is a Test Report?

Answer: A summary of testing activities, defects, and the overall quality of

the software.
🔹 Agile & Tools (Basic)

14. Have you heard of Agile methodology?

Answer: Yes. Agile is a flexible and iterative approach where software is

developed and tested in small increments (sprints).

15. Name any bug tracking tools you know.

Answer: JIRA, Bugzilla, Mantis.

16. Name some test case management tools.

Answer: TestRail, TestLink, Zephyr.

🔹 Real-time Scenario

17. What will you do if you find a bug?

Answer: Reproduce the bug, gather details (steps, screenshots), log it in the
bug tracking tool, and assign it to the developer.

18. What if the developer says it's not a bug?

Answer: Discuss and provide proof (steps, expected vs actual result).

Escalate to the lead if unresolved.

19. How do you handle missing requirements?

Answer: Clarify with the BA or developer, and test based on assumptions

until clarification is received.

20. Why should we hire you as a tester?

Answer: I am a quick learner, detail-oriented, and passionate about quality.
I'm ready to grow and contribute to the team.