Manual Testing

Manual testing is the process of testing a software manually, without the use of automation, to find defects in the software application. There are no third party automation tools used in this method of testing.

The testing process is carried out based on the guidelines specified in the test plan document to ensure complete test coverage. We will discuss Test Plan in detail in the forthcoming articles.

Role of a Tester in Manual Testing

When it comes to manual testing, the tester plays a very important role. The tester has to verify all the features of the software application from an end user point of view.Manual Testing

The tester must make sure all the functionalities mentioned in the Software Requirement Specification (SRS) document are met and there are no bugs in the application.

It is the preliminary method of testing the application and takes time to complete.

Goals of Manual Testing

  • Ensure that the system is ready for use.
  • Locate defects produced by the developer while building the software.
  • Ensure that the application being tested is free from bugs.
  • Ensure all the functionalities are tested and matching with the software requirement specification and business requirement.
  • To make sure the software is bug free.
  • To create confidence about the quality of software developed.
  • Ensure 100% coverage.

Steps to be Performed for Manual Testing

  1. Review the Software Requirement Specification to understand the application.
  2. Preparation of test scenarios
  3. Preparation of the environment for testing
  4. Preparation of test cases
  5. Execution of test cases
  6. Check if the actual result is as per the expected result
  7. Log the Defects in the Defect tracking tool
  8. Create a test summary report

Different Types of Manual Testing

Manual testing can by divided into the following types.

  • White Box Testing: White box testing is a type of testing that is carried out by the developers where they will verify the internal structure of the code rather than looking at the functionality or output. It is also known as glass box testing.
  • Unit Testing: Unit testing is another type of testing where the source code is divided into smallest testable units and tested by the developers or the development lead after the coding is done. Unit tests are prepared and the purpose of unit testing is to ensure each unit of software is ready to use and meets the coding standards and other development standards set by the organization.
  • Integration Testing: In integration testing, the different independent modules of the software are combined and tested together to detect defects during the integration and check the reliability between the modules. Test stubs and test drivers are used to help in integration testing.
  • System Testing: System testing is actually the functional and non functional testing that is performed by the testing team. Here, the completely integrated software system is tested by the testing team who ensures all the requirements are met and the software is free from defects.
  • Black Box Testing: Black box testing is a testing type where the testing is carried out to make sure the functionalities are working as expected. Here, the various inputs are given and outputs are verified without going into details about the code structure or the implementation details.
  • Acceptance Testing: Acceptance testing is a type of testing that is done after the system testing is completed by the testing team. In Acceptance testing, the customers test the application using actual data to ensure it meets all the business requirements provided. Acceptance testing is also known as UAT (User Acceptance Testing).


In this article we discussed about the different aspects of manual testing like its role, goal and the steps to perform manual testing. We also discussed the different kinds of manual testing. We will discuss each of the testing types discussed above in detail with examples in future articles.