Manual testing is software testing where users test the software step by step and compare the expected outcome with actual outcome according to the requirements of the client. It is one of the processes for finding bugs, defects, and issues in software programs. It helps to know if the application is working according to the user's requirements or not. In general, the process of software development involves the user writing every test case and executing it without the help of any automated testing tools.
Manual testing have its own advantages and disadvantages;
Advantages of Manual Testing
Testing is done more from user's point of view.
User can test software in a creative way which helps to locate unexpected defects or bugs.
Manual testing allows testers to emulate user experiences, while automated tests may struggle with real-world variables.
Manual testing detects non-coding bugs, while automated tools detect code-related issues.
Manual testing helps testers monitor product quality, familiarize with features, and maintain knowledge for future issues arising from code changes.
Disadvantages of Manual Testing
Manual testing takes more time than automated testing.
Manual testing is susceptible to human error, resulting in inconsistent results.
Manual testing can be more expensive for large projects.
Manual testers need a strong product understanding to identify errors.
Manual testing can become repetitive and boring.
How is manual testing done?
manual testing process
The process of manual testing is as below;
Understanding the requirements
Create test plan and scenarios
Write test cases
Execute the test
Record results and defects
Re-execute after bug fix
Understanding the requirements: Understand software requirements and specifications to understand intended functionality, user interactions, and expected behavior.
Create Test Plan and Test Scenarios: Create a test plan outlining objectives, scope, approach, resources, schedule, and criteria for testing the application under specific scenarios.
Write Test Cases: Design detailed test cases with step-by-step instruction, inputs data, expected results, and necessary preconditions for each identified scenario.
Execute the test: Testing is an important phase after designing test cases. This is a fundamental procedure where real work is done. After each test is completed, it should be marked as skipped, failed, or passed. Keeping crucial notes on failures is essential for accessing metrics for planning.
Record results and defects: Record the actual results and any differences from the expected outcomes. Include details about the defect, steps to reproduce, environment information, and any relevant attachments or screenshots.
Re-execute after bug fix: Re-test affected areas after addressing defects and making necessary code changes to ensure issues are resolved and the application behaves as expected.
Three major techniques of manual testing:
Mainly there are three types of Manual testing which are listed below;
White-box testing
Black-box testing
Grey-box testing
White-box testing: White box testing is a software testing method that analyzes an application's internal code, logic, and structure. It involves verifying individual components, code paths, and decision outcomes to identify complex defects, logical errors, and inadequate coverage. It complements black box testing and improves software quality.
Black-box testing: Black box testing is a software testing method where testers evaluate an application's functionality without knowing its internal code. It focuses on validating inputs and outputs based on requirements, simulating user interactions and scenarios. Although it doesn't require programming skills, it may miss complex defects and internal logic. Black box testing is essential for real-world validation and is part of a comprehensive testing strategy alongside white box testing.
Gray-box testing: Gray box testing is a hybrid approach that combines white box (internal code knowledge) and black box (external behavior) testing. It is useful for integration, system, security, and performance testing, offering a balanced perspective on defects. However, it requires careful consideration to maintain objectivity and prioritize testing efforts.
