Software testing is very crucial to validate the quality of software products. Companies across the globe are relying on manual testing because of the non-viability of automated testing in every scenario. Manual testing has its usability in cases when automation cannot be done readily.

This article lists manual testing interview questions that will help you to prepare for your upcoming manual testing interview.

Q1. What is Software Testing?

Ans. Software Testing is a process of validating a software product by identifying its correctness, completeness and quality. The process involves a number of activities that focus on finding errors in the software and related products and ensuring its quality before its market release.

Q2. Why is testing required?

Ans. Software testing is crucial for the following reasons-

  • To find out any errors in the product made during the development phases
  • To ensure less resource utilization by identifying any error in early phases of software development life cycle
  • To ensure effective performance of the software and provide an assurance to the stakeholders
  • To have accurate, consistent and reliable results
  • To ensure convenience to the user regarding the quality of the product
  • To ensure customer satisfaction and build the customers’ confidence in the organization
  • To avoid monetary penalties with respect to the quality of the product

Q3. When should you start the testing process?

Ans. Ideally, testing must begin from the start of the project. After the requirements are calculated, testers should come up with the system testing plan and start test case preparation. This also helps to find gaps in the process, if any.

Q4. What are the differences between Quality Assurance and Quality Control?


Quality Assurance Quality Control
A process of assuring that consumers receive the desired quality products  A process of fulfilling the quality of desired products 
Prevents any defects Identifies and fixes defects
Does not involve program execution Involves program execution
A procedure of creating deliverables  A procedure of verifying the created deliverables
Involves the complete software development life cycle  Involves complete software testing life cycle


Q5. What are the differences between Verification and Validation?


Verification Validation
Process of verifying documents, design, code, and program Process of evaluating the final software product to check if it meets customer requirements and expectations
Static in nature  Dynamic
Does not involve code execution Involves code execution
Human involvement required Computer-based execution
Low-level exercise High-level exercise

Q6. What are different steps involved in manual testing?

Ans. Different steps involved in manual testing include –

  • Planning and control
  • Analysis and design
  • Implementation and execution
  • Evaluating exit criteria
  • Reporting
  • Test closure activities

Q7. What are the different stages of manual testing?

Ans. There are four stages of manual testing –

Unit testing – The process of testing the smallest code logically isolated in a system and ensuring its functional correctness.

Integration Testing – The process of combining and testing individual units to verify if they can work smoothly when integrated.

System Testing – The process of testing all the components of software to ensure its overall quality. It comprises of different testing methodologies including

  • Usability testing
  • Regression testing
  • Functional testing

User Acceptance Testing – The process of deciding if a particular software is suitable for market release.

Q8. What is API?

Ans. API or Application Programming Interface is a communication protocol. This protocol is between clients and servers and a contract is created to ensure smooth functioning, and building of client-side software. The client describes its requirements and the server is responsible for delivering the product as agreed.

Q9. What is API testing?

Ans. API testing or Application Programming Interface (API) testing determines if the product meets the expectations of the consumers in terms of performance, functionality, reliability, and security.

Q10. What is Acceptance Testing?

Ans. Acceptance Testing is a process in software testing where a system is tested for its acceptability. This test helps the testers to evaluate the system’s compliance in accordance with the clients’ requirements and check if it is acceptable for delivery.

Q11.What is Accessibility Testing?

Ans. Accessibility testing is mandatory in software testing. It verifies if people with disabilities (deaf, blind, mentally unstable, among others) can use the software product.

Q12. What is Adhoc Testing?

Ans. Ad-hoc testing is an informal testing phase aiming to break a system by randomly trying the system’s functionality. It is an unplanned activity and doesn’t follow any test design technique.

Q13. What is Agile Testing?

Ans. Agile Testing is a testing practice following Agile methodologies. It aligns with iterative development methodology where requirements develop gradually from customers and testing teams.

Q14. What is Static Testing?

Ans. Static Testing is also called Dry Run Testing. In this form of software testing, the actual program or application is not used and the programmers read their own code to find any errors.

Q15. What is Dynamic Testing?

Ans. Dynamic testing checks the dynamic behavior of the code. Under dynamic testing, the software is analyzed against parameters like memory & CPU usage, response time and overall software performance.

Q16. What is White Box Testing?

Ans. White box testing is a methodology based on internal code structure of the software and involves examining the program structure. It derives test data from the program logic. White Box Testing is also known as Glass Box Testing, Clear Box Testing, and Structural Testing.

Q17. What is Black Box Testing?

Ans. Black Box Testing is a methodology where the tester tests the product without knowing its internal code structure, design or implementation.It is alsoknown as Behavioral Testing.

Q18. What is Grey Box Testing?

Ans. As the name suggests, Grey Box Testing combines the aspects of both Black Box Testing and White Box Testing. Here the tester performs the test with limited information about the internal structure and functionality of the software.

Q19. What are different types of defects?

Ans. There are three types of defects-

Wrong – These defects happen when requirements are incorrectly implemented.

Missing – These defects refer to missing things, for example – if the specification has not been implemented correctly because of any missing information or link.

Extra – Extra denotes extra feature incorporated in the final product. Since it was not received as a user requirement, it is referred as a defect.

Q20. What are the limitations of manual testing?

Ans. Manual testing has a few limitations, which include –

  • Higher susceptibility to errors because of human intervention
  • Time consuming
  • Not feasible to carry load testing and performance testing
  • Limited scope compared to automation testing
  • Not suitable in very large organizations and projects with time limitations
  • Costly