• Human-Driven Process: Manual testing relies on testers to manually perform test cases, requiring observation, analysis, and judgment throughout the process. 
   

• Flexible and Adaptive: Since manual testers can explore and test different parts of the application without predefined scripts, they can adapt their testing based on real-time findings. This makes manual testing ideal for complex or less documented projects. 
   

• Exploratory Testing: Testers have the freedom to explore the software beyond predefined test cases, uncovering bugs and unexpected issues that might not be discovered with automation. 
   

• User-Centric: Manual testing allows testers to think like real users, simulating how they would interact with the software. This is useful in detecting issues related to user experience (UX) and usability. 

Types of Manual Testing 

1. Black Box Testing 

In black box testing, testers evaluate the software without knowing the internal structure or code. This approach focuses on validating whether the application behaves as expected based on user inputs and outputs.

Testers treat the software like a "black box," only assessing what goes in and what comes out, which makes this method ideal for functional and usability testing. 

Key Features: 

• Focuses on user experience and software behavior. 
• Does not require knowledge of internal code. 
• Ideal for functional testing, system testing, and acceptance testing. 

2. White Box Testing 

In contrast to black box testing, white box testing involves testers who have knowledge of the code and internal workings of the software. 

 Testers perform tests on specific parts of the code, analyzing its logic and control flow to identify issues such as code inefficiencies, security vulnerabilities, and data handling errors. 

Key Features: 

• Requires understanding of the software’s internal structure. 
• Commonly used for unit testing and integration testing. 
• Helps identify logical errors and code inefficiencies. 

3. Gray Box Testing 

Gray box testing is a blend of both black box and white box testing methodologies. In this approach, testers have partial knowledge of the internal workings of the application. 

This helps in designing test cases more effectively while maintaining a user-centric perspective. It's especially useful for identifying issues related to structural problems or improper use of the application.

Key Features: 

• Hybrid Approach: Combines both black box (external functionality) and white box (internal structure) testing techniques. 
• Limited Internal Knowledge: Testers have partial access to the application's internal code and architecture, providing better insights into test design. 
• Effective for Web Applications: Gray box testing is particularly beneficial for web applications, where testers need both system-level understanding and user-level functionality. 
• Balanced View: Provides a good balance between testing from a user’s perspective and validating internal structures. 

4. Sanity Testing 

Sanity testing, a subset of regression testing, is performed to quickly verify whether a specific section of the application is functioning correctly after a minor change or bug fix.  

It focuses on confirming that recent updates haven't introduced new defects in the existing functionality. This non-exhaustive testing is usually done after receiving a new build. 

Key Features: 

• Subset of Regression Testing: Targets specific functionalities rather than the entire system. 
• Quick and Focused: Ensures that minor changes or bug fixes haven’t disrupted essential functionality without the need for in-depth testing.
• Conducted on New Builds: Performed after receiving new builds to ensure that the bug fixes or updates are successful. 
• Prepares for Further Testing: Sanity testing acts as a preliminary check before the software moves into more extensive testing phases. 

5. Exploratory Testing 

Exploratory testing is an unscripted, flexible testing technique where testers interact with the software in real time. Testers explore the application, documenting issues as they arise, and adapting test cases based on findings.  

This approach is effective for discovering bugs or edge cases that might not be covered by formal test cases. 

Key Features: 

• No predefined test cases; testers explore the software on the fly. 
• Encourages creativity and problem-solving.
• Useful in early development stages or for applications without strict documentation.

6. Regression Testing 

Regression testing ensures that new updates, fixes, or enhancements do not negatively affect existing functionality. It’s one of the most important manual software testing types when continuous changes are made to the code base. 

 Even small changes can introduce unexpected bugs, and regression testing ensures that the entire system remains stable. 

Key Features: