100 Manual testing interview questions with their answers:

1. What is Manual Testing?

Manual Testing is the process of manually verifying whether a software application functions as expected. A tester performs test cases and logs defects without using automation tools.

2. What is the difference between Manual Testing and Automation Testing?

• Manual Testing: Involves human intervention where test cases are executed manually.
• Automation Testing: Involves using scripts and tools to perform tests.

3. What are the types of Testing?

There are several types of testing, such as:

• Functional Testing
• Non-Functional Testing
• Regression Testing
• User Acceptance Testing (UAT)
• Integration Testing
• System Testing

4. What is the SDLC?

The Software Development Life Cycle (SDLC) is a framework that defines the steps involved in software development, from planning to delivery and maintenance.

5. What are the different SDLC models?

Some common SDLC models include:

• Waterfall Model
• V-Model
• Agile Model
• Spiral Model

6. What is the difference between Verification and Validation?

• Verification: Ensures the product is being built correctly as per the requirements.
• Validation: Ensures the product meets user requirements and expectations.

7. What is the purpose of testing?

The purpose of testing is to identify defects in software, improve its quality, ensure it meets requirements, and ensure the product is free of critical issues before release.

8. What is the STLC?

The Software Testing Life Cycle (STLC) refers to the phases of testing that include test planning, test case development, test execution, defect reporting, and test closure.

9. What is the difference between a Bug and a Defect?

• Bug: A flaw in the software that causes it to behave unexpectedly.
• Defect: A deviation from expected behavior as per the requirements.

10. What are the different levels of testing?

The main levels of testing are:

• Unit Testing
• Integration Testing
• System Testing
• Acceptance Testing

11. What is the difference between Functional and Non-Functional Testing?

• Functional Testing: Verifies the functionality of the software (e.g., what the system does).
• Non-Functional Testing: Verifies the attributes like performance, security, and usability.

12. What is Regression Testing?

Regression Testing ensures that new code changes have not negatively impacted the existing functionality of the software.

13. What is Smoke Testing?

Smoke Testing is a quick set of tests performed to ensure the basic functionality of an application is working before proceeding with more detailed testing.

14. What is Sanity Testing?

Sanity Testing is a quick evaluation to ensure that a specific function or feature works after a change or bug fix.

15. What is User Acceptance Testing (UAT)?

UAT is the final phase of testing where the intended users test the software to verify that it meets their needs and requirements.

16. What is the difference between Test Case and Test Scenario?

• Test Case: A set of conditions or actions used to verify a specific functionality of the application.
• Test Scenario: A high-level concept that describes the functionality to be tested.

17. What is a Test Plan?

A Test Plan is a document detailing the strategy, objectives, resources, and schedule for the testing process.

18. What is a Test Case?

A Test Case is a set of conditions or variables under which a tester will determine whether an application or system is working correctly.

19. What is the Bug Life Cycle?

The Bug Life Cycle includes stages like New, Assigned, Open, Fixed, Retested, Closed, and Rejected.

20. What are the different types of Testing techniques?

The main types of testing techniques are:

• Black-box Testing
• White-box Testing
• Grey-box Testing

21. What is Black-box Testing?

Black-box Testing focuses on the outputs based on various inputs, without knowledge of the internal workings of the application.

22. What is White-box Testing?

White-box Testing involves testing the internal structure of the application, including code paths, logic, and system architecture.

23. What is the difference between Priority and Severity?

• Priority: Determines the importance of fixing a defect based on business needs.
• Severity: Defines the impact of the defect on the application's functionality.

24. What is Boundary Value Analysis?

Boundary Value Analysis is a technique used to test the boundaries of input values (e.g., testing the minimum and maximum values).

25. What is Equivalence Partitioning?

Equivalence Partitioning is a technique to divide input data into equivalent partitions to reduce the number of test cases.

26. What is State Transition Testing?

State Transition Testing is a technique used when the system can be in different states. It tests the transitions between those states.

27. What is the Decision Table Testing?

Decision Table Testing uses a table to represent combinations of conditions and the corresponding actions.

28. What is Path Testing?

Path Testing involves testing all possible paths in a program to ensure they are working as expected.

29. What is the difference between Alpha and Beta Testing?

• Alpha Testing: Performed by internal teams before the product is released to external users.
• Beta Testing: Performed by external users before the final release.

30. What is Pair Testing?

Pair Testing involves two testers working together on the same test case to identify potential issues more effectively.

31. What is the difference between a Test Environment and a Test Bed?

• Test Environment: The hardware and software configuration where testing is performed.
• Test Bed: The environment including hardware, software, and other configurations needed for test execution.

32. What is the difference between Validation and Verification?

• Validation: Ensures the product is what the user needs.
• Verification: Ensures the product has been built according to specifications.

33. What is Exploratory Testing?

Exploratory Testing is an informal and flexible testing approach where testers explore the application to identify defects without predefined test cases.

34. What is the difference between Retesting and Regression Testing?

• Retesting: Testing specific defects to verify if they are fixed.
• Regression Testing: Ensures that new changes do not break the existing functionality.

35. What is the difference between Test Strategy and Test Plan?

• Test Strategy: A high-level document that defines the overall testing approach for the project.
• Test Plan: A detailed document that describes specific testing activities, including schedules, resources, and deliverables.

36. What is the role of a Test Lead?

A Test Lead is responsible for managing the testing team, creating the test strategy, and ensuring the overall testing process runs smoothly.

37. What is the difference between a Bug and an Issue?

• Bug: A defect in the application.
• Issue: A broader term that refers to any problem that may arise during the software lifecycle, including bugs, questions, or risks.

38. What is Test Data?

Test Data is the input data used during test execution to validate the behavior and functionality of the application.

39. What is the purpose of a Test Report?

A Test Report provides the outcomes of testing, including pass/fail status, defect details, and recommendations for improvement.

40. What is Load Testing?

Load Testing measures the system’s performance under normal and peak load conditions to identify potential bottlenecks.

41. What is Stress Testing?

Stress Testing checks how the system performs under extreme or excessive load conditions.

42. What is Performance Testing?

Performance Testing checks the speed, responsiveness, and stability of an application under load.

43. What is Usability Testing?

Usability Testing evaluates the user interface and user experience of the application.

44. What is Compatibility Testing?

Compatibility Testing ensures that the application works as expected across different devices, browsers, and operating systems.

45. What is the difference between System Testing and Acceptance Testing?

• System Testing: A complete testing of the entire application.
• Acceptance Testing: Ensures that the application meets user requirements.

46. What is Security Testing?

Security Testing ensures that the software is free from vulnerabilities and protects data from unauthorized access.

47. What is Localization Testing?

Localization Testing ensures that the application works as expected in different languages and regions.

48. What is Globalization Testing?

Globalization Testing checks if the application can be adapted to different languages, currencies, and cultures.

49. What is the role of a QA Engineer?

A QA Engineer is responsible for ensuring the quality of the software by performing testing, identifying defects, and collaborating with development teams.

50. What is Test Coverage?

Test Coverage measures the extent to which the code or functionality of the application is covered by test cases.

51. What are the different types of defects?

Types of defects include:

• Functional Defects
• Performance Defects
• Security Defects
• Usability Defects

52. What is Test Automation?

Test Automation involves using tools and scripts to automatically perform testing tasks.

53. What are the different phases in the STLC (Software Testing Life Cycle)?

The STLC phases are:

• Requirement Analysis
• Test Planning
• Test Design
• Test Execution
• Defect Reporting
• Test Closure

54. What is a Test Case Template?

A Test Case Template is a standardized format that includes the steps to execute, expected results, and other details for each test case.

55. What is a Traceability Matrix?

A Traceability Matrix ensures that all requirements are covered by test cases.

56. What is Risk-based Testing?

Risk-based Testing focuses on testing the areas of the application that have the highest risk of failure.

57. What is the difference between a Test Log and a Test Report?

• Test Log: A record of each step executed during testing.
• Test Report: A summary of testing results, including the pass/fail status and defect details.

58. What is a Validation Test Case?

Validation Test Cases are designed to ensure that the application works as expected and meets the user's needs.

59. What is a Verification Test Case?

Verification Test Cases verify that the application complies with the specified requirements and standards.

60. What is the difference between Alpha and Beta Testing?

• Alpha Testing: Conducted by internal teams before releasing the software to customers.
• Beta Testing: Performed by end-users after the alpha phase to gather feedback before final release.

61. What is a Test Environment?

A Test Environment is the setup required for testing the application, including hardware, software, and network configurations.

62. What is Traceability in testing?

Traceability refers to tracking requirements through test cases to ensure that all requirements are covered.

63. What is Manual Test Execution?

Manual Test Execution involves running the test cases manually without the use of automation tools.

64. What is the purpose of Smoke Testing?

Smoke Testing verifies that the most critical functionalities of the application work correctly after a build or update.

65. What is the difference between Test Case Design and Test Execution?

• Test Case Design: Creating detailed steps to validate a functionality.
• Test Execution: Running the test cases on the application and comparing the actual results with the expected results.

66. What is Test Scenario Design?

Test Scenario Design involves defining high-level testing objectives and ensuring they align with the project requirements.

67. What is a Test Suite?

A Test Suite is a collection of test cases or test scripts designed to test the system under different conditions.

68. What is the difference between Quality Assurance and Quality Control?

• Quality Assurance (QA): Focuses on preventing defects by improving the processes and methodologies.
• Quality Control (QC): Focuses on identifying defects after the product is developed.

69. What is an Incident in Manual Testing?

An incident is an event or occurrence that disrupts the testing process, often leading to the identification of a defect.

70. What is Exploratory Testing?

Exploratory Testing is an informal testing approach where testers explore the application to identify defects without predefined test cases. Here are the Manual Testing interview questions numbered from 70 to 100, including brief answers:

70. What is Test Design?

Test Design is the process of creating test cases and test scenarios based on the requirements and specifications of the software. It involves identifying test conditions, test data, and expected results.

71. What is Mutation Testing?

Mutation Testing involves modifying the source code by introducing small changes (mutations) and running tests to check if they can catch these mutations. This helps in evaluating the effectiveness of the test suite.

72. What is the difference between Load Testing and Stress Testing?

• Load Testing: Determines the system’s behavior under normal and expected conditions.
• Stress Testing: Tests the system under extreme load conditions to see how it behaves under stress or peak traffic.

73. What is the purpose of Performance Testing?

Performance Testing evaluates the system’s performance to ensure it meets speed, stability, scalability, and responsiveness requirements under varying loads.

74. What is a Test Harness?

A Test Harness is a software environment or tool that automates the execution of test cases and manages test data, simplifying the process of running tests.

75. What are the key components of a Test Case?

Key components of a test case include:

• Test Case ID
• Test Description
• Test Steps
• Expected Results
• Actual Results
• Pass/Fail Status

76. What is the difference between a Test Case and a Test Scenario?

• Test Case: A detailed step-by-step procedure to verify a specific functionality.
• Test Scenario: A higher-level description of what needs to be tested, often covering broader functionality.

77. What is Defect Density?

Defect Density is a metric used to measure the number of defects identified per unit of code, often expressed as defects per thousand lines of code (KLOC).

78. What is a Test Cycle?

A Test Cycle refers to the full testing process, from planning to execution, defect identification, and reporting, and ends with the final test report.

79. What is a Severity Level?

Severity Level indicates how critical a defect is, based on its impact on the system. Common severity levels include:

• Critical
• Major
• Minor
• Trivial

80. What is the purpose of a Test Summary Report?

A Test Summary Report consolidates test results, including test case execution status, defect information, and a summary of the overall testing process.

81. What is Configuration Management in Testing?

Configuration Management in Testing refers to the process of managing and tracking changes to software, test scripts, and documentation to maintain consistency and traceability.

82. What is a Defect Tracking Tool?

A Defect Tracking Tool is a software tool used to log, track, and manage defects during the testing process. Examples include JIRA, Bugzilla, and Quality Center.

83. What is the difference between Re-testing and Regression Testing?

• Re-testing: Testing a specific defect after it has been fixed to verify that it is resolved.
• Regression Testing: Ensuring that new code changes have not adversely affected the existing functionality.

84. What is the difference between Manual and Automated Testing?

• Manual Testing: Testing performed by human testers without the use of automation tools.
• Automated Testing: Using scripts or tools to automatically execute test cases.

85. What is an End-to-End Test?

An End-to-End test validates the complete flow of the application, from start to finish, to ensure that all components function together as expected.

86. What is the difference between a Test Case and a Test Plan?

• Test Case: A document specifying test steps, inputs, expected outputs, and actual results.
• Test Plan: A document that outlines the strategy, scope, objectives, resources, and schedule for testing.

87. What is the difference between Manual Testing and Unit Testing?

• Manual Testing: Involves human testers manually performing test cases to verify functionality.
• Unit Testing: A type of testing that verifies individual components or functions of the application, typically performed by developers.

88. What are Test Scripts?

Test Scripts are detailed instructions or steps that are followed during testing. These could be manual steps or automated scripts that test a specific functionality.

89. What is a Build in Testing?

A Build is a version of the software that is ready for testing. It typically includes code, libraries, and other necessary resources.

90. What is a Critical Bug?

A Critical Bug is a defect that severely impacts the functionality of the software, such as causing system crashes, data loss, or complete failure of core features.

91. What is a Test Deliverable?

Test Deliverables are documents and outputs produced during the testing process, such as test cases, test plans, defect logs, and test reports.

92. What is a High Priority but Low Severity Bug?

A defect that is of significant business importance but has low technical impact. For example, a minor cosmetic issue that affects a key part of the UI.

93. What is the difference between White-box and Black-box testing?

• White-box Testing: Testing based on knowledge of the internal structure and logic of the application (code level).
• Black-box Testing: Testing the software’s functionality without knowledge of its internal workings (focuses on inputs and outputs).

94. What are some commonly used tools for Manual Testing?

Some common tools used in manual testing include:

• JIRA (for bug tracking)
• TestRail (for test management)
• Bugzilla (for defect tracking)
• Quality Center (for test management)

95. What are the challenges in Manual Testing?

Challenges include:

• Time-consuming and repetitive tasks
• Human error
• Limited test coverage
• Difficulty performing regression testing for large applications

96. What is Boundary Value Analysis (BVA)?

Boundary Value Analysis is a testing technique that focuses on testing boundary values, as defects often occur at the boundaries of input ranges.

97. What is Test Data?

Test Data refers to the input data used during test execution. It includes both valid and invalid data designed to verify the application’s functionality.

98. What is a Test Case Review?

A Test Case Review is a process where test cases are examined by team members to ensure they are comprehensive, accurate, and effective in covering the functionality.

99. What is Test Case Execution?

Test Case Execution refers to the process of running the test cases to verify if the actual results match the expected results.

100. What is Load Testing?

Load Testing evaluates how the application performs under expected load conditions, checking if it can handle a specific number of users or transactions without degrading performance.