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

Supercharging QA: How Playwright MCP Agents Are Transforming Test Automation

 In automated browser testing, QA teams spend a massive chunk of their engineering cycles doing two things: writing repetitive locator boilerplates and fixing flaky tests broken by minor UI changes. The arrival of the Model Context Protocol (MCP) and Microsoft’s official Playwright MCP Server changes that dynamic. By turning browser automation into a structured interface for AI agents, test generation and maintenance are shifting from manual step-by-step coding to intent-driven execution. What is Playwright MCP? The Model Context Protocol (MCP) is an open standard designed to let AI systems interact seamlessly with external databases, APIs, and tools. The Playwright MCP Server exposes Playwright’s browser context directly to an AI agent (such as Cursor, Claude Code, or custom LLM test runners). Rather than forcing the AI to guess coordinates from screenshots or parse raw, noisy DOM trees, Playwright MCP feeds the model structured accessibility snapshots. [ AI Agent / LLM ] <---...
Post a Comment
Read more

Mastering Waits in Playwright: The Art of Synchronizing Your Automation

Web applications are rarely static. Data loads asynchronously, elements animate in and out, and pages navigate. This dynamic nature means your automation script needs to be smart enough to wait for the application to be ready before interacting with it. Without proper waiting strategies, your tests will consistently break with "element not found," "element not clickable," or "timeout" errors. Playwright offers a sophisticated suite of waiting capabilities, ranging from intelligent auto-waiting for actions to explicit waits for specific network events, page loads, or custom conditions. Understanding and utilizing these waits effectively is fundamental to writing reliable and robust Playwright tests. Playwright's Core Philosophy: Intelligent Auto-Waiting The most significant departure Playwright makes from older automation tools is its built-in auto-waiting mechanism. For nearly all actions (like click() , fill() , check() , selectOption() , etc.), Play...
Post a Comment
Read more