Manual testing Frequently asked Questions

Manual testing Frequently asked Questions..

Here are commonly asked interview FAQs for Manual Testing, explained in a clear, student-friendly way 👇

1. What is Manual Testing?

Manual testing is a type of software testing where test cases are executed manually without using automation tools to find defects in an application.

2. What is Software Testing?

Software testing is the process of verifying and validating a software application to ensure it meets requirements and is bug-free.

3. What are the types of testing?

Manual Testing
Automation Testing

4. What is Verification and Validation?

Verification: Are we building the product correctly? (reviews, walkthroughs)
Validation: Are we building the right product? (actual testing)

5. What is SDLC?

Software Development Life Cycle includes:

Requirement Analysis
Design
Development
Testing
Deployment
Maintenance

6. What is STLC?

Software Testing Life Cycle includes:

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

7. What is a Test Case?

A test case is a set of steps, inputs, and expected results used to verify a feature of an application.

8. What is a Test Scenario?

A test scenario is a high-level description of what to test, covering end-to-end functionality.

9. What is a Bug / Defect?

A bug is a difference between expected and actual result.

10. What is Defect Life Cycle?

New
Assigned
Open
Fixed
Retest
Closed
(Rejected / Duplicate / Deferred – optional states)

11. What is Severity and Priority?

Severity: Impact of the defect on the system
Priority: Urgency to fix the defect

12. What is Black Box Testing?

Testing done without knowing internal code, focusing on inputs and outputs.

13. What is White Box Testing?

Testing done with knowledge of internal code (usually by developers).

14. What is Grey Box Testing?

Combination of Black Box and White Box testing.

15. What is Smoke Testing?

Basic testing to ensure critical functionalities work after a new build.

16. What is Sanity Testing?

Quick testing to verify specific functionality after bug fixes.

17. What is Regression Testing?

Testing to ensure existing functionality works after changes.

18. What is Functional Testing?

Testing application features against requirements.

19. What is Non-Functional Testing?

Testing performance, usability, security, etc.

20. What is UAT (User Acceptance Testing)?

Final testing performed by end users to confirm business requirements.

21. What is Test Plan?

A document describing testing scope, approach, resources, schedule, and risks.

22. What is Entry and Exit Criteria?

Entry Criteria: Conditions to start testing
Exit Criteria: Conditions to stop testing

23. What is Exploratory Testing?

Testing without test cases, based on experience and intuition.

24. What is Ad-hoc Testing?

Informal testing without documentation.

25. What is Compatibility Testing?

Testing application behavior across different browsers, devices, OS.

Tags: Manual testing Interview questions