Scribd
Upload
12 views2 pages

Software Testing Interview Questions Answers

The document provides a comprehensive list of software testing interview questions and answers suitable for freshers. Key topics include definitions of software testing, differences between verification and validation, and various testing methodologies such as SDLC, STLC, and different testing types. It also covers concepts like bug vs defect, severity vs priority, and agile testing frameworks.

Uploaded by

w9qxfpc28r
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
12 views2 pages

Software Testing Interview Questions Answers

The document provides a comprehensive list of software testing interview questions and answers suitable for freshers. Key topics include definitions of software testing, differences between verification and validation, and various testing methodologies such as SDLC, STLC, and different testing types. It also covers concepts like bug vs defect, severity vs priority, and agile testing frameworks.

Uploaded by

w9qxfpc28r
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Software Testing Interview Questions & Answers

(Freshers Friendly)

Q: What is Software Testing? Why is it needed?


A: Software Testing is the process of evaluating a software application to find defects and ensure it
meets the requirements. It is needed to ensure quality and prevent failures.

Q: Difference between Verification and Validation.


A: Verification: Ensures the product is built correctly (process check). Validation: Ensures the right
product is built (meets user needs).

Q: What is SDLC?
A: Software Development Life Cycle – a process for planning, creating, testing, and deploying
software.

Q: What is STLC?
A: Software Testing Life Cycle – a process defining testing activities from requirement analysis to
test closure.

Q: What is a Test Case?


A: A document with inputs, execution steps, and expected results to verify a functionality.

Q: Bug vs Defect vs Error.


A: Error: Human mistake. Defect: Deviation found during testing. Bug: Defect accepted by the
development team.

Q: Severity vs Priority.
A: Severity: Impact on the system. Priority: Order in which it should be fixed.

Q: Sanity Testing vs Smoke Testing.


A: Smoke: Checks basic functionality after build. Sanity: Checks specific functionality after minor
changes.

Q: Regression Testing.
A: Testing existing functionality after changes to ensure nothing is broken.

Q: Black Box vs White Box Testing.


A: Black Box: Test without internal code knowledge. White Box: Test with code knowledge.

Q: Unit, Integration, System, UAT.


A: Unit: Small code modules. Integration: Combined modules. System: Entire application. UAT:
User validation.
Q: Boundary Value Analysis (BVA).
A: Testing at boundary limits of input values.

Q: Equivalence Partitioning.
A: Dividing inputs into valid/invalid groups to reduce test cases.

Q: Defect Life Cycle.


A: Steps from defect identification to closure.

Q: Agile Testing.
A: Testing in an Agile development process with continuous collaboration.

Q: Scrum.
A: Agile framework with roles (Scrum Master, Product Owner, Team) and sprints.

Q: Performance Testing.
A: Checks system speed, scalability, and stability.

Q: API Testing.
A: Validates APIs for correctness, performance, and security using tools like Postman.

Q: Example critical bug scenario.


A: Found payment gateway failure just before release – reported immediately, prioritized fix.

Q: Handling dev disagreement.


A: Use defect evidence (logs/screenshots) and discuss calmly with facts.

Q: Prioritizing test cases in less time.


A: Focus on high-risk, high-impact functionalities first.

You might also like