Manual Testing

#testing

Manual testing is process of evaluation of software with involvement of a person to find bugs and issue. This approach helps ensure the software works as intended and meets user needs.
Characteristics of Manual Testing:
• Human-Centric – Testers execute test cases like end users, providing input and checking results.
• Exploratory – Involves investigative testing without predefined cases to uncover unexpected issues.
• Flexible – Testers adapt test cases or explore new scenarios as requirements change.
• Early Start – Can be performed in the initial stages of development to catch issues early.
• Handles Complexity – Suitable for testing complex workflows and component interactions.
• UI Evaluation – Effective for assessing user interface design, usability, and responsiveness.

Advantages of Manual Testing:
Wherever human intervention is required, manual testing is the only way to handle it.
Complex testing can be handled
Negative Test cases work only in Manual testing

Disadvantage of Manual Testing:
Time consuming for repetitive test execution like regression testing.
Error may occur due to carelessness

Types of Manual Testing

White box testing:
In White Box Testing technique/glass box Testing, the person will check the internal structure of the system like designs, coding, etc., manually.
White Box Testing Example
Consider the following piece of code:

Here, the development team will review the entire coding part line by line to ensure the correctness of the code. It includes following methods or coverage

Statement Coverage
Branch Coverage
Path Coverage
Cyclomatic Coverage

Statement Coverage:
Statement Coverage includes each are every line of code is works as expected or not.

The goal of WhiteBox testing in software engineering is to verify all the decision branches, loops, and statements in the code.
To exercise the statements in the above white box testing example, WhiteBox test cases would be
• A = 1, B = 1
• A = -1, B = -3

Branch Coverage:
Branch Coverage includes each are every branch is performs as expected or not.
Path Testing:
White box testing will be checks all possible execution paths in the program to sure about the each one of the functions behaves as expected.

Cyclomatic Testing:
Cyclomatic complexity is a metric that measures the complexity of a program by counting its decision points. Decision points refer to various condition in which the code’s behavior is exhibited.

Black Box testing:
Black Box Testing (close box testing) is a software testing method in which the functionalities of software applications are tested without having knowledge of internal code structure, implementation details and internal paths. Black Box Testing mainly focuses on input and output of software applications, and it is entirely based on software requirements and specifications. It is also known as Behavioral Testing.

Key Features of Black Box Testing
• Functionality Focus: It validates whether the software meets its functional requirements by testing its behavior against expected outcomes.
• No Internal Knowledge Required: Testers do not need programming or implementation knowledge, making it accessible to non-technical testers.
• User-Centric Approach: Testing is performed from the perspective of an end-user, ensuring the application is intuitive and meets user expectations.
• Independent Testing: Testers are independent of the development team, ensuring unbiased
Gray box testing:
Gray Box Testing is a software testing technique that combines elements of the Black Box Testing technique and the White Box Testing technique.

Objectives of Gray Box Testing:
• To provide the combined advantages of both black box testing and white box testing.
• To combine the input of developers as well as testers.
• To improve overall product quality.
• To reduce the overhead of the long process of functional and non-functional testing.
• To provide enough free time to developers to fix defects.
• To test from the user's point of view rather than a designer's point of view.
Example of Gray Box testing: