# Manual Testing Methods

In this post, we are going to see manual testing methods. Manual testing methods are classified as follows:

* 1\. BLACK BOX TESTING
* 1.1. Black Box Testing Techniques
* 1.2. Types of Black Box Testing
* 2\. WHITE BOX TESTING
* 2.1. White Box Testing Techniques
* 3\. GREY BOX TESTING

Let’s see all the three types of Manual Testing Methods below:

**BLACK BOX TESTING:**

Black Box Testing is a software testing method in which testers evaluate the functionality of the software under test without looking at the internal code structure. This can be applied to every level of software testing such as Unit, Integration, System and Acceptance Testing.

Testers create [test scenarios/cases](https://www.softwaretestingmaterial.com/test-case-template-with-explanation/) based on software requirements and specifications. So it is AKA Specification Based Testing, Behavioral Testing and Input-Output Testing.

Tester performs testing only on the functional part of an application to make sure the behavior of the software is as expected. So it is AKA Behavioral Based Testing.

The tester passes input data to make sure whether the actual output matches the expected output. So it is AKA Input-Output Testing.

There is no obligation on testers to have knowledge on source code in this process.

**Black Box Testing Techniques:**

* Equivalence Partitioning
* Boundary Value Analysis
* Decision Table
* State Transition Testing

**Types of Black Box Testing:**

**Functionality Testing:** In simple words, what the system actually does is functional testing. To verify that each function of the software application behaves as specified in the requirement document. Testing all the functionalities by providing appropriate input to verify whether the actual output is matching the expected output or not. It falls within the scope of black box testing and the testers need not concern about the source code of the application.

**Non-functionality Testing:** In simple words, how well the system performs is non-functionality testing. Non-functional testing refers to various aspects of the software such as performance, load, stress, scalability, security, compatibility etc., Main focus is to improve the user experience on how fast the system responds to a request

#### **WHITE BOX TESTING:** <a href="#white-box-testing" id="white-box-testing"></a>

White Box Testing is based on applications internal code structure. In white-box testing, an internal perspective of the system, as well as programming skills, are used to design test cases. This testing usually was done at the unit level. It is AKA Glass Box, Clear Box, Structural Testing, Open Box, Transparent Box.

**White Box Testing Techniques:**

* Statement Coverage
* Branch Coverage
* Path Coverage

#### **GREY BOX TESTING:** <a href="#grey-box-testing" id="grey-box-testing"></a>

Grey box is the combination of both White Box and Black Box Testing. The tester who works on this type of testing needs to have access to design documents. This helps to create better test cases in this process.

[\
](https://i1.wp.com/www.softwaretestingmaterial.com/wp-content/uploads/2015/12/Manual-Testing-Methods.png?ssl=1)
