Manual Testing Interview Questions

We have selected Manual Testing Interview Questions and Answers that are asked most frequently. We have selected those questions having higher chance that an interviewer can ask. When you are appearing in Software Testing Interview these questions may be very useful for you. You can brush-up Manual Testing Interview Questions before your interview and you can increase your chance.

We have added the most important Manual Testing Interview Questions with Answers that Might help you to get your next QA Engineering Job.

What is Software Testing?
Software Testing is a process used to identify the correctness, completeness and the quality of developed software. It includes a series of activities conducted with the intent of finding errors in software so that it could be corrected before the product is released to the market.

What are the two main categories of software testing?
Software testing is a huge domain but it can be broadly categorised into two areas such as :
1- Manual Testing
2- Automation Testing

What is Manual testing?
Manual Testing is the oldest type of software testing where the testers manually execute test cases without using any test automation tools. It means the software application is tested manually by QA testers.

What is Automation testing?
Automation Testing is the process of using the assistance of tools, scripts, and software to perform test cases by repeating pre-defined actions. Test Automation focuses on replacing the manual human activity with systems or devices that enhance efficiency.

What different types of manual testing techniques are there?
Different types of manual testing techniques are as below;
1-Black Box Testing
2-White Box Testing
3-Unit Testing
4-System Testing
5-Integration Testing
6-Acceptance Testing

What is Black-box testing?
It is a standard software testing approach that requires testers to assess the functionality of the software as per the business requirements. The software is treated as a black box and validated as per the end user’s point of view.

What is a test plan?
A test plan stores all possible testing activities to ensure a quality product. It gathers data from the product description, requirement, and use case documents.

What does a test Plan Document include?
A Test Plan Document includes the following sections:

  1. Testing objectives
  2. Test scope
  3. Testing the frame
  4. Environment
  5. Reason for testing
  6. Criteria for entrance and exit
  7. Deliverable
  8. Risk factors

What is agile testing and why is it important?
Agile testing is a software testing process that evaluates software from the end user point of view. It is favourable as it does not require the development team to complete coding for starting QA. Instead, both coding and testing go hand in hand. However, it may require continuous customer interaction.

What are the different levels of manual testing?
There are four levels of Manual Testing:

  1. Unit Testing
  2. Integration Testing
  3. System Testing
  4. User Acceptance Testing

What is acceptance testing?
Acceptance testing is done to enable a customer to determine whether the software product is acceptable or not. It also validates whether the software follows a set of agreed acceptance criteria and use cases. In this level, the system is tested for the user acceptability.

What is accessibility testing?
This is a special type of testing for the persons with disabilities. It is used to validate whether a software product is accessible to the people having disabilities (deaf, blind, mentally disabled etc.).

What is Ad-hoc testing?
The whole system is break into small ad-hoc systems and tested for functionality. Ad-hoc testing is a testing phase where the tester tries to ‘break’ the system by randomly trying the system’s functionality.

What is Bottom-up testing?
The Bottom-up testing is a testing approach which follows integration testing where the lowest level components are tested first, after that the higher level components are tested. The process is repeated until the testing of the top-level component.

What is Random Testing or Monkey Testing?
It is random in Nature Random data is generated and tested over system without any pattern. This is called Random testing or Monkey Testing. There is no use cases or test cases.
Features/Limitation of Monkey or Random Testing:
-Most of the random tests are redundant and unrealistic.
-It needs more time to analyse results.
-It is not possible to recreate the test if you do not record what data was used for testing.

What is Load Testing?
Load testing is a testing technique in which system is tested with an increasing load until it reaches the threshold value. The main purpose of load testing is to check the response time of the system with an increasing amount of load. Load testing is performed to make sure that the system can withstand a heavy load

What is Stress Testing?
Stress testing is a testing technique to check the system when hardware resources are not enough such as CPU, memory, disk space, etc. The main purpose of stress testing is to check the failure of the system and to determine how to recover from this failure is known as recoverability.

What is Spike Testing?
Spike testing is a subset of load testing. This type of testing checks the instability of the application when the load is varied.

What is traceability matrix?
The relationship between test cases and requirements is shown with the help of a document. This document is known as a traceability matrix.

What is Endurance Testing?
Endurance testing is a subset of load testing. This type of testing checks the behaviour of the system. Endurance testing is also known as Soak testing. A memory leak occurs when the program does not release its allocated memory after its use. Sometimes the application does not release its memory even after its use and this unusable memory cause memory leak. This causes an issue when the application runs for a long duration.

What is Volume Testing?
Volume testing is a testing technique in which the system is tested when the volume of data is increased.

What is Scalability Testing?
Scalability testing is a testing technique that ensures that the system works well in proportion to the growing demands of the end users.

What are the differences between Alpha Testing and Beta Testing?
Alpha Testing is a type of software testing performed to identify bugs before releasing the product to real users or to the public. Alpha Testing is a type of user acceptance testing.

Beta Testing is performed by real users of the software application in a real environment. Beta Testing is also a type of user acceptance testing.

What is the difference between static and dynamic testing?
Static Testing – During Static testing method, the code is not executed, and it is performed using the software documentation.
Dynamic Testing – To perform this testing the code is required to be in an executable form.

What’s the difference between a bug and a defect?
A bug is a just fault in the software that’s detected during testing time. A defect is a variance between expected results and actual results, detected by the developer after the product goes live.

What is a top-down and bottom-up approach in testing?
Top-Down Testing happens from top to bottom. That is, high-level modules are tested first and after that low-level modules. Lastly, the low-level modules are incorporated into a high-level state to guarantee the framework is working as it is expected to.

Bottom-Up Testing happens from base levels to high-up levels. The lowest level modules are tested first and afterwards high-level state modules. Lastly, the high-level state modules are coordinated to a low level to guarantee the framework is filling in as it has been proposed to.

Spread the love

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.