What is Manual Testing? Basics, Types, and Examples

🔍 Introduction

Manual Testing is the most fundamental approach in the Software Testing Life Cycle (STLC). It is the process of manually testing software applications without the use of automation tools. The tester acts as the end-user and validates whether the software behaves as expected. Despite the growth of automation testing, manual testing remains essential because it helps in identifying usability issues, visual inconsistencies, and unexpected behavior that automation tools may miss.

In this article, we’ll cover the basics of manual testing, different types of manual testing, and examples to understand how it works in real-life projects.

📘 Basics of Manual Testing

Manual Testing focuses on ensuring that the application is functioning correctly based on the given requirements. Here are the core fundamentals:

1. No Automation Tools Used

• Testers execute test cases manually, step by step.

• Tools like JIRA, Bugzilla, and Trello are used for tracking defects, but execution is done without code/scripts.

2. End-User Perspective

• The tester plays the role of the actual user.

• Validates both functionality and user experience.

3. Test Documentation

• Includes Test Plan, Test Cases, Test Scenarios, and Bug Reports.

• Example of a simple test case format:

Test Case ID: TC001
Test Scenario: Login with valid credentials
Pre-condition: User must have a valid account
Test Steps:
1. Open the application.
2. Navigate to Login Page.
3. Enter valid Username and Password.
4. Click on Login.
Expected Result: User should be redirected to the Dashboard.
Actual Result: (To be filled after execution)
Status: Pass/Fail

4. Verification and Validation

• Verification: Checking whether the product is built correctly (following requirements).

• Validation: Ensuring the right product is built for the end-user.

🛠️ Types of Manual Testing

Manual Testing covers multiple testing methods depending on the project needs. Below are the most common types:

1. Unit Testing

• Performed on individual components or modules.

• Usually done by developers, but manual testers may validate with test data.

2. Integration Testing

• Ensures that two or more modules work together.

• Example: Testing the integration between the login page and the user dashboard.

3. System Testing

• Validates the entire application as a whole.

• Example: End-to-end testing of an e-commerce app from login to checkout.

4. Smoke Testing

• Also called Build Verification Testing.

• Quick check to ensure basic functionalities work.

• Example: Checking if the app installs correctly and opens without crash.

5. Sanity Testing

• Narrow and focused testing after small changes.

• Example: After fixing a login bug, tester only re-checks login.

6. Regression Testing

• Ensures that new changes do not break existing features.

• Example: After adding a “Forgot Password” feature, tester re-checks login and dashboard.

7. Usability Testing

• Focuses on user-friendliness and experience.

• Example: Checking whether the “Sign Up” button is visible and accessible.

8. Acceptance Testing

• Done to verify if the application meets business requirements.

• Usually performed during User Acceptance Testing (UAT) phase.

9. Exploratory Testing

• No predefined test cases, tester explores the app.

• Helps in finding unexpected defects.

10. Ad-hoc Testing

• Informal testing without documentation.

• Example: Randomly trying invalid inputs to check system stability.

🧑‍💻 Examples of Manual Testing in Real Projects

Example 1: Testing a Login Page

• Scenario: A banking application login page.

• Test Cases:

  • Enter correct username & password → Should login successfully.

  • Enter wrong password → Should show error message.

  • Leave fields empty → Should not allow login.

  • Check “Forgot Password” link → Should redirect properly.

Example 2: E-Commerce Checkout Flow

• Scenario: Online shopping cart.

• Test Cases:

  • Add items to cart → Items should reflect in cart.

  • Apply discount coupon → Correct discount applied.

  • Enter invalid credit card → Show payment error.

  • Successful payment → Generate order confirmation email.

Example 3: Mobile App Testing

• Scenario: Social media mobile app.

• Test Cases:

  • App installation on Android & iOS.

  • Navigation in portrait & landscape mode.

  • Uploading image/video functionality.

  • Notifications and push alerts.

🎯 Summary

Manual Testing is the foundation of software quality assurance. It ensures that the software application works as expected and delivers the right experience to users. Although automation testing is growing, manual testing remains crucial for usability, accessibility, exploratory, and ad-hoc testing. Understanding its basics, types, and real-world examples gives you a strong foundation as a QA professional.

👉 Whether you are a beginner or preparing for a QA interview, mastering manual testing concepts will give you a solid start in the world of software testing.