Skip to main content

Manual Testing Basics

 

📘 Manual Testing Basics – A Beginner’s Guide



By QA Cosmos | Updated: June 2025

🔍 What is Manual Testing?

Manual Testing is the process of testing software manually — without using automation tools — to find defects or ensure the system behaves as expected.

A manual tester acts as an end-user, checking each feature, clicking buttons, entering inputs, and validating outputs to ensure the application works correctly.

🧠 Why is Manual Testing Important?

  • 🧪 It catches usability issues that automation might miss.

  • 🕵️ It allows human judgment and exploratory testing.

  • 🧰 It's the foundation before introducing automation.

  • 💬 Critical for UI/UX feedback, especially in early stages.

🧾 Key Concepts in Manual Testing

1️⃣ SDLC vs. STLC

  • SDLC (Software Development Life Cycle): Focuses on how software is developed.

  • STLC (Software Testing Life Cycle): Focuses on how testing is planned, executed, and closed.

2️⃣ Test Case

A test case is a step-by-step instruction to verify a feature. It includes:

  • Test Case ID

  • Description

  • Steps to Execute

  • Expected Result

  • Actual Result

  • Pass/Fail Status

3️⃣ Bug/Defect

When the actual result doesn't match the expected result, it’s logged as a bug or defect.

🔁 Manual Testing Process (Step-by-Step)

  1. 📄 Understand Requirements

  2. 🧪 Write Test Scenarios and Test Cases

  3. ⚙️ Set up Test Environment

  4. ▶️ Execute Tests Manually

  5. 🐞 Log Bugs in a Bug Tracking Tool (e.g., Jira, Bugzilla)

  6. 🔁 Re-test and Close Bugs

🧰 Common Tools for Manual Testing

ToolPurpose
JIRABug & task tracking
TestLinkTest case management
Excel/SheetsLightweight test planning
Browser DevToolsInspecting HTML, logs

👩‍💻 Skills Every Manual Tester Should Have

  • 🔍 Attention to Detail

  • 🧠 Analytical Thinking

  • ✍️ Test Documentation Skills

  • 📢 Communication (for reporting bugs clearly)

  • 🎯 Basic Understanding of Web & Mobile Applications

💡 Real-Life Example

Scenario: You’re testing a login form.
Test Case:

  • Enter correct username and password → Expected: User logs in

  • Leave both fields empty → Expected: Show validation errors

  • Enter wrong credentials → Expected: Show "Invalid credentials"

You do all these manually — click by click, screen by screen.

🎯 Final Thoughts

Manual testing may seem simple, but it's the core of quality assurance. It helps uncover subtle UI/UX flaws, validate business logic, and ensure the product works for real users.

If you're just starting your QA journey — mastering manual testing is the first step toward becoming a great software tester.

📚 Coming Up Next on QA Cosmos:

  • ✨ Writing Effective Test Cases

  • ⚙️ Difference Between Manual & Automation Testing

  • 🐞 How to Report a Bug Like a Pro

  • 💼 Top Manual Testing Interview Questions

💬 Have questions or want us to cover a specific topic? Let us know in the comments below!

Would you like me to create blog posts for the next topics too (like Automation Testing, Bug Life Cycle, or Test Case design)

Labels:

Comments

Post a Comment

Popular posts from this blog

How to Inspect Disappearing Elements Using "Emulate a Focused Page" in Chrome DevTools

As web developers, we often encounter frustrating scenarios where elements like dropdowns, tooltips, or custom select menus vanish the moment we try to inspect them in Chrome DevTools. This happens because these elements are often designed to disappear when they lose focus or the mouse moves away. Fortunately, Chrome DevTools provides a powerful feature called "Emulate a focused page" that lets you freeze the page's focus state, making it much easier to debug these elusive elements. The Challenge of Disappearing Elements 👻 Imagine you're styling a complex navigation menu with sub-menus that appear on hover. When you try to right-click and "Inspect" one of these sub-menus, it vanishes! This is a classic example of an element losing its active state because DevTools gains focus, causing the element's blur or focusout event to trigger its disappearance. Traditional methods like trying to quickly click and inspect often fail, leading to wasted time and f...
Post a Comment
Read more

ISTQB CTFL Mock Test

ISTQB CTFL Interactive Mock Test Ready to ace your ISTQB Certified Tester Foundation Level (CTFL) exam? Practice is paramount! While studying the official syllabus and glossary is essential, testing your knowledge with mock exams is the best way to prepare for the actual exam format, question types, and time pressure. This blog post brings you a 40-question mock test designed to mirror the structure and difficulty of the real ISTQB CTFL exam. Take your time, answer each question to the best of your ability, and then use the provided answer key to check your performance. Aim to complete these 40 questions within 60 minutes, just like the actual exam. Important Note on Interactivity: While it would be fantastic to offer a fully interactive quiz here with real-time scoring and highlighting, this blog post format primarily delivers text. To experience an interactive version with automated scoring and feedback (like showing marks and highlighting wrong answers in r...
Post a Comment
Read more

Selenium vs. Playwright: A Deep Dive into Waiting Concepts

  In the world of web automation, "waiting" is not just a pause; it's a strategic synchronization mechanism. Web applications are dynamic: elements appear, disappear, change state, or load asynchronously. Without proper waiting strategies, your automation scripts will frequently fail with "element not found" or "element not interactable" errors, leading to flaky and unreliable tests. Let's explore how Selenium and Playwright approach this fundamental challenge. The Challenge: Why Do We Need Waits? Imagine a user interacting with a webpage. They don't click a button the exact instant it appears in the HTML. They wait for it to be visible, stable, and ready to receive clicks. Automation tools must mimic this human behavior. If a script tries to interact with an element before it's fully loaded or clickable, it will fail. Waits bridge the gap between your script's execution speed and the web application's loading time. Selenium'...
Post a Comment
Read more