100+ Manual Testing Interview Questions Every Tester Should Know

Here are 100+ manual testing interview questions and answers for testers of all experience levels. If you are preparing for a job change or wish to acquaint yourself with the nitty-gritty of the software testing, do read this post for quick results.

Our team has put a lot of efforts in the selection and preparation of these interview questions for manual testers. They have thought through all the answers and tried the best to keep them simple and easy to remember. However, if you like to improve any of the answers or wish to add a new question, then do let us know.

Below are a few manual testing interview tips. These should help you in presenting yourself with confidence during interviews.

  • Read about the company and the opportunity.
  • Be good at non-vocal skills.
    • Show them your confidence, make proper eye contact and stand straight.
    • Brace for a great start.
  • Dress well.
    • Prefer to wear a formal outfit.
    • You may even look out for a dress code in the company if they’ve any.
  • Neither talk too much nor pretend to be too familiar.
  • Be polite while replying.
  • Take time to think before answering a question.
  • Ask questions.
  • Don’t look desperate.
  • Be authentic, candid and concise.
  • Thank the interviewer in person.

Apart from these manual testing interview questions, you might like to check out the below post, one of the best technical questionnaires for Senior test engineers.

The list of most important manual testing interview questions appears next. Read them all to boost your testing concepts.

100+ Manual Testing Interview Questions & Answers

100+ Manual Testing Interview Questions and Answers

Manual Testing Interview Questions

Q-1. What does Requirement Traceability Matrix include?

Requirement Traceability Matrix (RTM) is a document which records the mapping between the high-level requirements and the test cases in the form of a table.

That’s how it ensures that the Test Plan covers all the requirements and links to their latest version.

Q-2. Explain the difference between Pilot and Beta testing?

Read the following points to know the difference between Pilot and Beta testing.

1. We do the beta test when the product is about to release to the customer whereas pilot testing takes place in the earlier phase of the development cycle.
2. In the beta test, testing application is given to a few users to make sure that application meet the customer requirements and does not contain any showstopper bug. Whereas, in the pilot test, few members of the testing teamwork at the Customer site to set up the product. They give their feedback also to improve the quality of the end product.

Q-3. Describe how to perform Risk analysis during software testing?

Risk analysis is the process of identifying the hidden issues that may derail the successful delivery of the application. It also prioritizes the sequence of resolving the identified risks for testing purpose.

Following are some of the risks that are of concern to the QA.

1. New Hardware.
2. New Technology.
3. New Automation Tool.
4. The sequence of code delivery.
5. Availability of test resources for the application.

We prioritize them into three categories which are as follows.

1. High magnitude: Impact of the bug on the other functionality of the application.
2. Medium: It is somewhat bearable but not desirable.
3. Low: It is tolerable. This type of risk has no impact on the company business.

Q-4. What is Silk Test and why should you use it?

Here are some facts about the Silk tool.

1. It’s a tool developed for performing the regression and functionality testing of the application.
2. It benefits when we are testing Window based, Java, the web, and the traditional client/server applications.
3. Silk Test help in preparing the test plan and managing them to provide the direct accessing of the database and validation of the field.

Q-5. What is the difference between Master Test Plan and Test Plan?

The difference between the Master Plan and Test Plan can be described using the following points.

1. Master Test Plan contains all the test scenarios and risks prone areas of the application. Whereas, the Test Plan document contains test cases corresponding to test scenarios.
2. Master Test Plan captures every test to be run during the overall development of application whereas test plan describes the scope, approach, resources, and schedule of performing the execution.
3. MTP includes test scenarios to be executed in all the phases of testing that run during the complete lifecycle of the application development.

Whereas, a separate Test Plan exists for each stage of testing like Unit, Functional, and System which contains the test cases related to that type only.
4. A Master Test Plan suffice for big projects which require execution in all phases of testing. However, preparing a basic Test Plan is enough for small projects.

Q-6. How do you handle a non-reproducible bug?

Following bugs lie under the non-reproducible category.

1. Defects observed due to low memory issue.
2. Issues raised due to address pointing to a memory location that does not exist.
3. The race condition is an error scenario which occurs when the timing of one event impacts another executing in a sequence.

A tester can take the following actions to handle the non-reproducible bugs.

1. Execute test steps that are close to the error description.
2. Evaluate the test environment.
3. Examine and evaluate test execution results.
4. Keep the resources & time constraints under check.

Q-7. How do you perform Automated Testing in your environment?

Automation Testing is a process of executing tests automatically. It reduces the human intervention to a great extent. We use different test automation tools like QTP, Selenium, and WinRunner. These tools help in speeding up the testing tasks.

Using the above tools we can create test scripts to verify the application automatically. After completing the test execution, these tools also generate the test reports.

Q-8. What are the factors that you’ll consider to choose automated testing over manual testing?

The choice of automated testing over manual testing depends on the following factors.

1. Tests require periodic execution.
2. Tests include repetitive steps.
3. Tests execute in a standard runtime environment.
4. Automation is expected to take less time.
5. Automation is increasing reusability.
6. Automation reports are available for every execution.
7. Small releases like service packs which include a minor bug fix. In such cases, executing the regression tests is sufficient for validation.

Q-9. What is the difference between a Test Driver and Test Stub?

The test driver is a piece of code that calls a software component under test. It is useful in testing that follows the bottom-up approach.

Test stub is a dummy program that integrates with an application to complete its functionality. These are relevant for testing that uses the top-down approach.

Let’s take an example.

1. Let’s say there is a scenario to test the interface between modules A and B. We have developed only module-A. Then we can test module-A if we have real module-B or a dummy module for it. In this case, we call module-B as the Test Stub.
2. Now, module-B can’t send or receive data directly from module-A. In such a scenario, we’ve to move data from one module to another using some external features called Test Driver.

Q-10. What are the essential qualities of an experienced QA or Test Lead?

Every QA or Test Lead should have the following qualities.

1. Well-versed in Software testing processes.
2. Ability to accelerate teamwork to increase productivity.
3. Improve coordination between QA and Dev engineers.
4. Provide ideas to refine the QA processes.
5. Ability to conduct RCA meetings and draw conclusions.
6. Excellent written and interpersonal communication skills.
7. Quick learner and able to groom the team members.

Q-11. What are the different types of software testing?

Following is the list of various testing types used by manual testers.

  • Unit testing
  • Integration testing
  • Regression testing
  • Shakeout testing
  • Smoke testing
  • Functional testing
  • Performance testing
    • Load testing
    • stress testing
    • Endurance testing
  • White box and Black box testing
  • Alpha and Beta testing
  • System testing

Q-12. What are the key elements of a test plan?

A test plan contains the following main points.

  • Testing objectives
  • Test scope
  • Testing the frame
  • The environment
  • Reason for testing
  • The criteria for entrance and exit
  • Deliverables
  • Risk factors

Q-13. What is a Test case?

A test case is a sequence of actions and observations that are used to verify the desired functionality. A good test case helps to identify problems in the requirements or design of an application.

Q-14. What is Agile testing and why is it important?

Agile testing is a software testing process which evaluates software from the customer point of view. It is beneficial because this does not require Dev to complete coding for starting QA. Instead, the coding and testing both go hand in hand. However, it may require continuous customer interaction.

Q-15. How do you test a product if the requirements are yet to freeze?

If the requirement spec is not available for a product, then a test plan can be created based on the assumptions made about the product. But we should get all assumptions well documented in the test plan.

Q-16. How will you tell if enough test cases have been created to test a product?

First of all, we’ll check if every requirement has at least one test case covered. If yes, then we can say that there are enough test cases to test the product.

Q-17. What will you do when a bug turns up during testing?

When a bug shows up, we can follow the below steps.

  • Run more tests to make sure that the problem has a clear description.
  • Run a few more tests to ensure that the same problem doesn’t exist with different inputs.
  • Once we are sure of the full scope of the bug, then we can add details and report it.

Q-18. If a product is in production and one of its modules gets updated, then is it necessary to retest?

It is advisable to perform regression testing and run tests for all of the other modules as well. Finally, the QA should carry out the System testing.

Q-19. What is the difference between Functional Requirement and Non-Functional Requirement?

The functional requirement specifies how a product should run whereas a non-functional requirement represents how it should be.

Functional Requirements.

  • Authentication
  • Business rules
  • Historical Data
  • Legal and Regulatory Requirements
  • External Interfaces

Non-functional Requirements.

  • Performance
  • Reliability
  • Security
  • Recovery
  • Data Integrity
  • Usability

Q-20. How come the Severity and Priority relate to each other?

  • Severity – Represents the gravity/depth of the bug.
  • Priority – Specifies which bug should get fixed first.
  • Severity – Describes the application point of view.
  • Priority – Defines the user’s point of view.

Q-21. What are the different types of Severity?

The severity of a bug can be low, medium or high depending on the context.

  • User Interface Defect – Low
  • Boundary Related Defects – Medium
  • Error Handling Defects – Medium
  • Calculation Defects – High
  • Misinterpreted Data – High
  • Hardware Failures – High
  • Compatibility Issues – High
  • Control Flow Defects – High
  • Load Conditions (Memory leakages under load testing) – High

Q-22. What are the Entry and Exit Criteria in Software Testing?

Entry criteria – It is a process that should run when a system begins. It includes the following artifacts.

  • SRS (Software Requirement Specification)
  • FRS (Functional Requirement Specification)
  • Use case
  • Test-Case
  • Test-plan

Exit Criteria – It signals when the testing should complete and when should the product be ready to release. It includes the following artifacts.

  • Test Summary Report
  • Metrics
  • Defect Analysis report

Q-23. What is the test strategy?

Test strategy is an approach to carry out the testing activity. It covers the following.

  • Roles and responsibilities for each member.
  • Testing scope.
  • Test tools.
  • Test environment.
  • Testing schedule.
  • Associated risks.

Q-24. What is smoke testing and what is sanity?

Smoke testing confirms the basic functionality works for a product. It requires you to identify the most basic test cases for execution.

Sanity testing, on the other hand, ensures that the product runs without any logical errors. For example, if we are testing a calculator app; we may multiply a number by 3 and check whether the sum of the digits of the answer is divisible by 3.

Q-25. What is the difference between a Bug, Defect, and Error?

A bug is usually the same as the defect. Both of them represents an unexpected behavior of the software.

However, an error would also fall in the same category. But in some cases, errors are fixed values.

For example – 404/405 errors in HTML pages.

Q-26. What is the difference between High level and Low-Level test case?

  • High-level test cases cover the core functionality of a product like standard business flows.
  • Low-level test cases are those related to user interface (UI) in the application.

Q-27. What is the difference between Static testing and dynamic testing?

Static Testing.

  • It is a white box testing technique which directs the developers to verify their code with the help of a checklist to find errors in it.
  • Developers can start it done without actually finalizing the application or program.
  • Static testing is more cost-effective than Dynamic testing.
  • It covers more areas than Dynamic testing in a shorter time.

Dynamic Testing.

  • Dynamic testing involves the execution of an actual application with valid inputs and checking of the expected output.
  • Examples of Dynamic testing are Unit Testing, Integration Testing, System Testing and Acceptance Testing.
  • Dynamic testing happens after the code deployment.
  • It starts during the validation stage.

Q-28. What is a Test Harness?

Test Harness requires configuring a set of tools and input data to test an application under various conditions. It involves monitoring the actual output with the expected output for correctness.

Its benefits are as follows.

  • Upward push in productivity due to process automation.
  • Improve the overall product Quality.

Q-29. What is Defect Leakage?

Defect leakage occurs at the Customer or the End-user side after the product delivery. If the end user sees an issue in the application, then such bugs lead to Defect leakage. And this process of finding bugs is also called as Bug Leakage.

Q-30. What kind of document will you need to begin Functional testing?

  • It is none other than the Functional specification document. It defines the full functionality of a product.
  • Other documents are also useful in testing like user manual and BRS.
  • Gap analysis is another document which can help in understanding the expected and existing system.

Q-31. Beside test case & test plan, what documents a tester should produce?

Here are a few other documents to prepare.

  • Testing metrics
  • Test design specs
  • End-to-end scenarios
  • Test summary reports
  • Bug reports

Q-32. What is a Business Requirements Document (BRD)?

BRD provides a detailed business solution for a project including the documentation of customer needs and expectations.

BRD fulfills the following objectives.

  • Gain agreement with stakeholders.
  • Provide clarity on the business requirements.
  • Describe the solution that meets the customer/business needs.
  • Determine the input for the next phase of the project.

Q-33. What is Risk Analysis?

Risk analysis is a technique to identify the things that can go wrong in a software development project. They can negatively impact the scope, quality, timeliness, and cost of a project.

However, everyone involved in the project has a part in minimizing the risk. But it’s the leader who ensures that the whole team understands the individual role in managing the risk.

Q-34. What is exploratory testing?

Exploratory testing is a process which lets a tester to concentrate more on execution and less on planning.

  • It requires formulating a test charter, a short declaration of the scope, a set of objectives and possible approaches to be used.
  • The test design and test execution activities may run in parallel without formally documenting the test conditions, test cases or test scripts.
  • Testers can use boundary value analysis to concentrate the testing effort on error-prone areas by accurately pinpointing the boundaries.
  • Notes should be recorded for the Exploratory Testing sessions as it would help to create a final report of its execution.

Q-35. Can we do System testing at any stage?

No. The system testing should start only if all modules are in place and work correctly. However, it should happen before the UAT (User Acceptance testing).

Q-36. Why is it impossible to test a program thoroughly?

Here are the two principal reasons that make it impossible to test a program entirely.

  • Software specifications can be subjective and can lead to different interpretations.
  • A software program may require too many inputs, too many outputs, and too many path combinations to test.

Q-37. What is the primary difference between Debugging & Testing?

  • Testing is to find out defects while using a product whereas debugging is to reach the part of the code causing failure.
  • Debugging is isolating the problem area in the code done by a developer whereas Testing is identifying the bug in an application and done by a tester.

Q-38. What are the roles of glass-box and black-box testing tools?

Black-box testing.

It doesn’t require the knowledge of internal design or code. So the tests are based on requirements and functionality. Black box testing focuses on finding the following errors.

  • Interface errors
  • Performance errors
  • Initialization errors
  • Incorrect or missing functionality
  • Errors in accessing an external database

Glass-box testing or White-box testing.

It requires familiarity with the internal design and application code. So the tests concentrate on path coverage, branch coverage, and statement coverage. It is expected to cover the following.

  • All possible code flows of a module.
  • Execute all loops.
  • Exercise all logical decisions.
  • Verify the internal data structure to ensure their validity.

Q-39. What is GAP analysis?

Gap analysis reveals any deviation between the features available for testing and how the customer perceives them to be.

Traceability matrix is a testing tool which testers can use to track down the gaps.

Q-40. How do we know the code has met specifications?

Traceability matrix is an intuitive tool which ensures the requirements mapped to the test cases. And when the execution of all test cases finishes with success, it indicates that the code has met the requirements.

Q-41. Is it possible to achieve 100% coverage of testing? How would you ensure it?

No, it’s not possible to perform 100% testing of any product. But you can follow the below steps to come closer.

  • Set a hard limit on the following factors.
    • Percentage of test cases passed
    • The no. of bug found
  • Set a red flag if,
    • Test budget depleted
    • Deadlines breached
  • Set a green flag if,
    • The entire functionality gets covered in test cases.
    • All critical & high bugs must have a status of CLOSED.

Q-42. What are error guessing and error seeding?

Error Guessing.

It is a test case design technique in which testers have to guess the defects that might occur and write test cases to represent them.

Error Seeding.

It is the process of adding known bugs in a program for the tracking the rate of detection & removal. It also helps to estimate the number of faults remaining in the program.

Q-43. What is the difference between coupling and cohesion?

The difference between coupling and cohesion is as follows.

  • Cohesion is the degree which measures the dependency of the software component that combines related functionality into a single unit whereas coupling represents to have it in a different group.
  • Cohesion deals with the functionality that relates to different processes within a single module whereas coupling deals with how much one module is dependent on the other modules within the product.
  • It is a good practice to increase the cohesion between the software whereas coupling is discouraged.

Q-44. What is CMM?

The Capability Maturity Model for Software (CMM or SW-CMM) is a model for assessing the maturity of the software processes of an organization.

It also identifies the key practices that increase the maturity of these processes.

Q-45. What is Cause Effect Graph?

It is a graphical representation of inputs and the associated outputs effects which assist in designing test cases.

Q-46. Why does software have bugs?

  • Miscommunication.
  • Programming errors.
  • Timeline pressures.
  • Change in requirements.
  • Software complexity.

Q-47. What is Ramp Testing?

It is a testing method which proposes to raise an input signal until the system breaks down.

Q-48. What is Recovery Testing?

It ensures that the program must recover from any expected or unexpected events without loss of data or functionality.

Events could be like a shortage of disk space, unexpected loss of communication, or power out conditions.

Q-49. What do you understand of Inspection?

It’s a group-level review and quality improvement process for the product documents. It focuses on the following two aspects.

  • Product document improvement.
  • Process improvement (of both document production and inspection).

Q-50. What is globalization testing?

Globalization testing concentrates on detecting the potential problems in the product design that could spoil globalization. It certifies that the code can handle the desired international support without breaking any functionality. And also, it ensures that there would be no data loss and display problems.

Q-51. What does it mean by functional testing?

Functional testing is a software testing methodology which ensures that the application under test has all the functionality working as per the specifications provided.

Q-52. What are the different types of functional testing?

The functional testing covers the following types of validation techniques.

1- Unit Testing
2- Smoke testing
3- Sanity testing
4- Integration Testing
5- Interface Testing
6- System Testing
7- Regression Testing
8- UAT

Q-53. How do you conduct functional testing?

Functional testing sees the application under test as a black-box. We as a tester, first of all, write down the use cases for all the possible workflows of the said features.

After that, we verify the functionality by exercising all the said features, their options and ensure that they behave as expected.

Q-54. What tool do you use for functional testing?

We use the Unified Functional Testing (UFT) tool developed by HP (Hewlett Packard) for both the functional and regression testing.

This tool makes use of Visual Basic (VB) scripting to automate the functional workflows. It allows us to integrate manual, automated as well as framework-based test scripts in the same IDE.

Q-55. What are the functional test cases?

Functional test cases are those that confirm that the application executes a specified business function. Most of these tests take the form of user or business cases that resemble the standard transactions.

Q-56. What is functional and nonfunctional?

In Software engineering terms, a non-functional requirement (NFR) is one that lays down the criteria for assessing the operation of a system, rather than a general behavior. They often get called as the “quality attributes” of a system.

Whereas the functional requirements are those that cover the technical aspect of the system.

Q-57. What are nonfunctional test cases?

Non-functional testing is a type of testing for observing the non-functional aspects (such as performance, usability, reliability) of the application under test.

It validates the readiness of a system as given in the nonfunctional specification and never got addressed in functional testing.

Q-58. When should you stop testing?

Here is the list of influencing factors to decide when to stop testing:

1. Deadlines (project deadline, testing milestones, etc.)
2. Test cases executed with a certain percentage of success.
3. Test budget got exhausted.
4. Code coverage target achieved.
5. The volume of defects drops below the average.
6. Beta or alpha testing cycle ends.

Q-59. What is Reliability testing?

Reliability testing is a testing strategy to measure the consistency of a Software in executing a specific operation without throwing any error for a certain period in the given environment.


The probability that a Server class application hosted on the cloud is up and running for six long months without crashing is 99.99%. We refer to this type of testing as reliability.

Q-60. How is a test case different from a test scenario?

A test case is a testing artifact to verify a particular flow with defined input values, test preconditions, expected output, and postconditions prepared to cover specific behavior.

A test scenario can have one or many associations with a test case which means it can include multiple test cases.

Q-61. What does it mean by STLC?

The STLC is an acronym for the Software Testing Life Cycle. It is a testing model which proposes to execute test execution in a systematic and planned way. In the STLC model, many activities occur to improve the quality of the product.

The STLC model lays down the following steps:

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

Q-62. What is the Requirement Analysis phase in STLC?

The requirement analysis (RA) is the first stage of the STLC model. In this step, the testing team learns what to test & determine the testable requirements. If some specifications are not precise or have a disagreement, then the stakeholders like business analyst (BA), architects, customers provide the clarity.

Q-63. What are the tasks performed in the Requirement Analysis phase of STLC?

Test team performs the following tasks during the RA phase.

1. Provide a questionnaire for the customer-facing people.
2. List down the priorities areas for testing.
3. Gather test environment details for carrying out the testing tasks.
4. Evaluate the possibility of test automation and prepare a report.

Q-64. What is the Test Planning (TP) phase in STLC?

The second phase of STLC is the test planning. It is a crucial step as the team here defines the whole testing strategy for the project. Hence, it gets also known as the Test strategy phase.

In this stage, the test lead has to get the effort and cost estimation done for the whole project. This phase starts out soon after the RA phase gets over. The outcomes of the TP include the Test Planning & Effort estimation documents. After the planning ends, the testing team can begin writing the test case development tasks.

Q-65. What are the tasks performed in the Test Planning (TP) phase of STLC?

Test team performs the following tasks during the TP phase.

1. Provide a written objective & scope for the STLC cycle.
2. Mention the testing types to cover.
3. Estimate testing efforts and resource requirements.
4. Select the testing tools required.
5. Confirm the test infra requirements.
6. List down the testing schedule and set milestones.
7. Prepare the summary of the entire testing process.
8. Create the control policy.
9. Assign roles and responsibilities.
10. Outline the testing deliverables.
11. Conclude the entry criteria, suspension/resumption criteria, and exit conditions.
12. Mark the expected risks.

Q-66. What is the Test Case Development phase in STLC?

The testing team picks on the test case development tasks once the test planning (TP) phase is over. In this stage of STLC, the principal activity is to write detailed test cases for the requirements. While performing this task, they also need to prepare the input data required for testing. Once the test plan is ready, it needs to be reviewed by senior members or the lead.

One of the documents which team has to produce is the Requirement Traceability Matrix (RTM). It is an industry-wide standard for ensuring the test case get correctly mapped with the requirement. It helps in tracking both the backward & forward direction.

Q-67. What are the tasks performed in the Test Case Development phase of STLC?

Test team performs the following tasks during the TCD phase.

1. Write test cases.
2. Produce scripts for automation testing (Optional).
3. Gather test data required for test execution.

Q-68. What is the Test Environment Setup phase in STLC?

It is a time-consuming yet crucial activity in the STLC to prepare the test environment. Only after the test setup is available, the team can determine which conditions the application would go through testing.

It is an independent task and can go in parallel with test case writing stage. The team or any member outside the group can also help in setting up the testing environment. In some organizations, a developer or the customer can also create or provide the testing beds. Simultaneously, the test team starts writing the smoke tests to ensure the readiness of the test infra.

Q-69. What are the tasks performed in the Test Environment Setup phase of STLC?

Test team performs the following tasks during the TES phase.

1. Assess the need for new Software & hardware requirements.
2. Prepare the test infra.
3. Execute smoke tests and confirms the readiness of the test infra.

Q-70. What is the Test Execution phase in STLC?

After the testing infra is ready, the test execution phase can start off. In this stage, the team runs the test cases as per the test plan defined in the previous steps.

If a test case executes successfully, the team should mark it as Passed. If some tests have failed, then the defects should get logged, and the report should go to the developer for further analysis. As per the books, every error or failure should have a corresponding defect. It helps in tracing back the test case or the bug later. As soon as the development team fixes it, the same test case should execute and report back to them.

Q-71. What are the tasks performed in the Test Execution phase of STLC?

Test team performs the following tasks during the TE phase.

1. Execute tests as per the test planning.
2. Provide test execution status showing the passed, failed, skipped statistics.
3. Create defects for failed cases and assign to dev for resolution.
4. Perform re-execution of test cases which have got the defect fixes.
5. Make sure the defects get closed.

Q-72. What is the Test Cycle Closure phase in STLC?

The testing team calls upon the meeting to evaluate the open defects, known issues, code quality issues and accordingly decides on the closure of the test cycle.

They discuss what went well, where is the need for improvement and notes the pain points faced in the current STLC. Such information is beneficial for the future STLC cycles. Each member puts his/her views on the test case & bug reports and finalizes the defect distribution by type and severity.

Q-73. What are the tasks performed in the Test Cycle Closure phase of STLC?

Test team performs the following tasks during the TCC phase.

1. Define closure criteria by reviewing the test coverage, code quality., the status of the business objectives, and test metrics.
3. Produce a test closure report.
4. Publish best practices used in the current STLC.

Q-74. What does a Fault mean in Software testing?

A fault is a condition that makes the software to fail while executing the intended function.

Q-75. What does an Error mean in Software testing?

An error represents a problem in a program that arises unexpectedly and causes it not to function correctly. An application can encounter either software errors or network errors.

Q-76. What does a Failure mean in Software testing?

A failure represents the incompetence of a system or component in executing the intended function as per its specification.

It could also happen in a customer environment that a particular feature didn’t work after product deployment. They would term it as a product failure.

Q-77. What is the difference between error and bug?

A slip in the coding indicates an Error. The error discovered by a manual tester becomes a Defect. The defect which the dev team admits known as a Bug. If a build misses on the requirements, then it is a functional failure.

Read – Difference between Defect, Error, Bug, Failure, and Fault

Q-78. What is Defect Life Cycle in software testing?

Defect Life Cycle also has another name as Bug Life Cycle.

Defect Life Cycle is the representation of the different states of a defect which it attains at different levels during its lifetime. It may have variations from company to company or even gets customized for some projects as the software testing process drives it to not getting out of the way.

Q-79. What is the difference between priority and severity in software testing?

Severity indicates the impact of a defect on the development or the operation of a component in the application going under test. It usually is an indication of commercial loss or cost to the environment or business reputation.

On the contrary, the Priority of a defect shows the urgency of a bug yet to get a fix. For example – a bug in a server application blocked it from getting deployed on the live servers.

Q-80. What does defect density mean in software testing?

Defect density is a way to measure the no. of defects found in a product during a specific test execution cycle. It gets determined by dividing the defect count found with the size of the software or component.

KLOC (Thousands of lines of code) is the unit used to measure the defect density.

Q-81. What does the Defect Detection Percentage mean in software testing?

Defect Detection Percentage (DDP) is a type of testing metric. It indicates the effectiveness of a testing process by measuring the ratio of defects discovered before the release and reported after release by customers.

For example – let’s say the QA logged 70 defects during the testing cycle and the customer reported 20 more after the release. The DDP would come to 72.1% after the calculation as 70/(70 + 20) = 72.1%.

Q-82. What does the Defect Removal Efficiency mean in software testing?

Defect Removal Efficiency (DRP) is a type of testing metric. It is an indicator for the efficiency of the development team to fix issues before the release.

It gets measured as the ratio of defects fixed to total the number of issues discovered.

For example – let’s say that there were 75 defects discovered during the test cycle while 62 of them got fixed by the dev team at the time of measurement. The DRE would come to 82.6% after the calculation as 62/75 = 82.6%.

Q-83. What does the Test Case Efficiency mean in software testing?

Test Case Efficiency (TCE) is a type of testing metric. It is a clear indicator of the efficiency of the test cases getting executed in the test execution stage of the release. It helps in ensuring and measuring the quality of the test cases.

Test Case Efficiency (TCE) => (No. of defects discovered / No. of test cases executed)* 100

Q-84. What is Age of Defect in software testing?

Defect age is the time elapsed between the day the tester discovered it and the day the developer got this fixed.

While estimating the age of a defect, consider the following points.

1. The day of birth for a Defect is the day it got assigned and accepted by the dev.
2. The issues which got dropped are out of the scope.
3. The age can be both in hours or days.
4. The end time is the day got verified and closed, not just fixed by the dev.

Q-85. What is Defect Clustering in software testing?

Defect clustering is a situation in testing which could arise if either most of the software bugs got discovered only in a handful of modules or the software fails to operate frequently.

Q-86. What is Pesticide Paradox in software testing?

The pesticide paradox is a situation in software testing when the same tests get repeated over and over again until they are no longer able to find new bugs.

Q-87. What is the Pareto Principle in software testing?

In software testing, the Pareto Principle refers to the notion that 80% of all bugs happen to be in the 20% of the program modules.

Q-88. What are the different ways to apply the Pareto Principle in software testing?

Following is the list of ways to exercise Pareto Principle in software testing:

1. Arrange the defects based on their causes, not via consequences. Don’t club bugs that yield the same outcome. Prefer to group issues depending on what module they occur.
2. Collaborate with the dev team to discover new ways to categorize the problems. E.g., use the same static library for the components which counted for the most bugs.
3. Put more energy for locating the problem areas in the source code instead of doing a random search.
4. Re-order the test cases and pick the critical ones first to begin.
5. Pay attention to the end-user response and assess the risk areas around.

Q-89. What do you know about the Data Flow Testing?

It is one of the white-box testing techniques.

Data Flow Testing emphasizes for designing test cases that cover control flow paths around variable definitions and their uses in the modules. It expects them to have the following attributes:

1. The input to the module
2. Control flow path for testing
3. Pair of an appropriate variable definition and its use
4. The expected outcome of the test case

Q-90. What do you know about the API Testing?

API is an acronym for Application Programming Interface. It gives users access to public classes, functions, and member variables for calling them from the external applications. It lays down a model for components to being interaction with each other.

API testing comprises of three parts:

1. Data tier (database)
2. Business logic tier (PHP/J2EE)
3. Presentation tier (UI)

API testing is also a white box testing method. It makes use of the code and a programming tool to call the API. It ignores the UI layer of the application and validates the path between the client and the API. The client software forwards a call to the API to get the specified return value. API testing examines whether the system is responding with the correct status or not.

API testing got carried out by the testers to confirm the system from end to end. They don’t have permissions to get to the source code but can use the API calls. This testing covers the authorization, usability, exploratory, automated and the document validation.

Q-91. What Is Cyclomatic Complexity in software testing?

In software testing, the cyclomatic complexity represents a test metric known as the program complexity. This method got introduced by Thomas J. McCabe in the year 1976. It sees a program as a graph using the control flow representation.

The graph includes the following attributes:

1. Nodes – A node indicates the processing tasks
2. Edges – An edge shows the control flow between the nodes.

Q-92. What is the usage of Cyclomatic Complexity in software testing?

1. It gets to find the independent path for test execution.
2. It proposes that the test should cover all the branches once.
3. It gives space to concentrate on the untested paths.
4. It guarantees the better code coverage.
5. It determines the risks associated with a program.
6. It aims to minimize the probable risks.

Q-93. What are Rainbow or Color Box Testing types?

The majority of software testers knew about the grey, black and white box testing. Let’s see what all color box testings are available.

1. White box tests
2. Black box checking
3. Grey box testing
4. Glass box tests
5. Red box scripts
6. Yellow box testing
7. Green box checking

Q-94. What do you know about the Structured Testing?

Structured testing is often get called as the basis path testing. It got invented by Tom McCabe.

Q-95. What are the steps involved in Structured Testing?

1. The control flow graph should get derived from the system component.
2. The Cyclomatic Complexity of the chart should get considered.
3. A group of C basis path should get identified.
4. Defining test cases for every basis path is necessary.
5. The execution should include all the established test cases.

Q-96. What does the high availability testing mean for a software tester?

High availability shows the ability of a system or a component to operate continuously without failure even at high loads for a long time.

Hence, the High availability testing confirms that a system or its sub-systems have gone through thorough checks and, in many cases, simulates failures to validate whether components support redundancy or not.

Q-97. What does it mean by baseline testing?

A baseline is the indicator of a specific benchmark that serves as the foundation of a new creation.

In Baseline testing, the tests capture and preserve all the results produced by the source code, and compare against a reference baseline. This reference baseline refers to the last accepted test results. If there are new changes in the source code, then it requires re-execution of tests to form the current baseline. If the new results get accepted, then the current baseline becomes the reference.

Q-98. What is the purpose of a failover test?

Failover testing is a test strategy to evaluate how a software allocates resources and switch operations to backup systems for preventing operational failures.

Q-99. What does it mean by Gorilla testing?

Gorilla Testing is a testing strategy where testers collaborate with developers as a joint force for validating a target module thoroughly from all ends.

Q-100. What is the purpose of End to End testing?

End to End Testing is a testing strategy to execute tests which covers every possible flow of an application from its start to the finish. The objective of performing end-to-end tests is to discover software dependencies and to assert that the correct input is getting passed between various software modules and sub-systems.

Summary – Manual Testing Interview Questions and Answers

It was one more post that can boost your chances in a job interview. Also, we try that our posts could teach skills that can help you most in your work. That’s why we came up with this blog post on the top manual testing interview questions for experienced QA engineers.

It would be great if you let us know your feedback on this post. Also, you can ask us to write on a topic of your choice. We’ll add it to our writing plan.

If you’d enjoyed the post and wish to see more such posts, then follow us on our social media (Facebook/Twitter) accounts.

Keep Learning,