
Letβs cover the basics of Manual Testing in a clear way:
π Basics of Manual Testing
1. Definition
Manual Testing is the process of manually executing test cases without the help of automation tools. The tester behaves like an end-user and verifies that the application works as expected.
2. Key Objectives
- To find defects/bugs in the software.
- To ensure the product meets business requirements.
- To validate functionality, usability, and user experience.
- To improve quality and reliability of the software.
3. Characteristics of Manual Testing
- Performed by humans (testers).
- Relies on test cases, checklists, or exploratory methods.
- No programming or automation scripts required.
- Requires patience, creativity, and attention to detail.
- Slower than automation but more flexible.
4. Types of Manual Testing
- Black Box Testing β Focus on functionality (without looking at code).
- White Box Testing β Focus on internal logic & code structure.
- Gray Box Testing β Combination of black & white box.
5. Levels of Manual Testing
- Unit Testing β Testing smallest modules/functions (done by developers).
- Integration Testing β Checking how modules work together.
- System Testing β Entire application tested as a whole.
- User Acceptance Testing (UAT) β Final testing by client/end-users.
6. Phases of Manual Testing
- Requirement Analysis β Understand what needs to be tested.
- Test Planning β Define scope, strategy, tools, responsibilities.
- Test Case Design β Write test cases with steps, inputs, and expected results.
- Test Execution β Manually run test cases on the application.
- Defect Reporting β Log bugs into a tool (JIRA, Bugzilla, etc.).
- Test Closure β After bug fixes, retesting, regression testing, and reporting.
7. Advantages
β
Best for small projects or applications with frequent UI changes.
β
No need for automation skills or tools.
β
Finds user experience & usability issues.
β
Cost-effective for short-term projects.
8. Disadvantages
β Time-consuming for large projects.
β Repetitive tasks are boring and error-prone.
β Not suitable for performance/load testing.
β Less reliable (human errors possible).
9. Examples of Manual Testing
- Filling out a login form to check if login works with valid/invalid inputs.
- Navigating through an e-commerce site to check if cart and checkout work.
- Verifying error messages when incorrect data is entered.
β
In short:
Manual Testing = Human-driven process to check if software works as expected. Itβs the foundation of testing and helps in ensuring software quality before automation.