Manual Testing
sign in to trackManual testing is the process of testing software by performing test steps manually, without using automated test scripts to execute the tests.
A manual tester interacts with the application, checks different scenarios, compares the actual result with the expected result, and reports any defects found.
Manual testing can involve following predefined test cases as well as exploring the application to identify unexpected behavior. It requires logical thinking, attention to detail, understanding of requirements, and the ability to think from a user's perspective.
Example
Suppose an application has a Login feature.
A manual tester may:
Open the login page.
Enter a valid username and password.
Click Login.
Check whether the user is successfully logged in.
Try an incorrect password.
Check whether the appropriate error message is displayed.
Try leaving the fields empty.
Check how the application responds.
The tester compares the actual behavior with the expected behavior and reports any difference as a defect.
When Is Manual Testing Useful?
Manual testing can be particularly useful when:
A feature is being tested for the first time.
Requirements or the user interface are changing frequently.
Exploratory testing is needed.
User experience and usability need to be evaluated.
Human observation or judgment is important.
A test is not suitable for automation.
◈Key Points
- Best for exploratory testing, UX evaluation, ad-hoc testing, and one-off scenarios.
- Manual testing excels at catching usability issues and visual defects automation overlooks.
- It is slower and not repeatable at scale — every regression cycle costs tester time.
- Skilled manual testers use heuristics (mnemonics like SFDPOT, FEW HICCUPPS) to guide exploration.
- Manual testing should focus on what automation cannot do, not duplicate what it already covers.
Keep a 'test charter' during exploratory sessions: document your mission, time-box it, and capture notes. This makes exploratory work auditable and reproducible.