Manual Testing Essentials

Manual testing is the process of manually executing test cases without using automation tools to ensure a software application behaves as expected.

Key Concepts:

• Test Plan, Test Case & Suite, Bug Life Cycle

• Smoke, Sanity, Regression, and UAT Testing

✅ Test Plan

A Test Plan is a strategic document that outlines the QA process for validating a software application. It includes what to test, how to test, who will test, and the scope of testing.

🔍 Key Elements:

• Objectives and scope of manual testing

• Test items and features to be tested

• Resources, responsibilities, and timelines

• Risk assessment and mitigation

💡 Actionable Tip:
Before writing your first Test Case, always review the Test Plan to understand the test objectives and constraints. It ensures your testing aligns with business goals.

---

🧪 Test Case & Test Suite

A Test Case is a step-by-step guide to validate a specific function of the software. It includes inputs, execution conditions, and expected results. A Test Suite is a collection of related Test Cases, grouped logically for execution.

🔍 Example:

• Test Case: Validate login with valid credentials

• Test Suite: User Authentication Tests

💡 Actionable Tip:
Use a standard format: Test Case ID, Description, Steps, Expected Result, Actual Result, Status. This consistency improves traceability and communication in the manual QA process.

---

🐞 Bug Life Cycle

The Bug Life Cycle describes the journey of a defect from identification to resolution. It's essential to manage quality and maintain transparency in the QA process.

🔄 Common Stages:

1. New

2. Assigned

3. Open

4. Fixed

5. Retest

6. Verified

7. Closed / Reopened

💡 Actionable Tip:
Always attach screenshots or logs when reporting a bug. It helps developers reproduce and fix the issue faster, improving overall manual testing efficiency.

Testing Techniques:

• Black-box

• Exploratory

• Ad-hoc

• Boundary Value Analysis

🎯 Black Box Testing

Black Box Testing focuses on validating the functionality of the application without knowing its internal code structure. Testers provide inputs and verify outputs against expected results.

🔍 Used For:

• Functional testing

• Acceptance testing

💡 Actionable Tip:
When using Black Box techniques, think like an end-user. Focus on user workflows, not code. This mindset helps uncover real-world issues that developers may overlook.

---

🔍 Exploratory Testing

Exploratory Testing is an informal but powerful approach where testers learn the system as they test. There’s no fixed script—testers explore the app based on intuition and experience.

🔍 Best When:

• Time is limited

• Requirements are incomplete

• You want to discover edge cases

💡 Actionable Tip:
Take quick notes while exploring. Log anything unusual. This can later be turned into formal Test Cases if needed.

---

🧪 Ad-hoc Testing

Ad-hoc Testing is unstructured testing done without planning or documentation. The aim is to break the system and find unexpected bugs.

🔍 When to Use:

• After formal testing

• When you suspect something might be wrong

💡 Actionable Tip:
Pair with a teammate during Ad-hoc testing. A fresh perspective often catches what you miss.

---

🔢 Boundary Value Analysis (BVA)

Boundary Value Analysis is a technique where you test at the edge of input ranges—minimum, maximum, just below, just above, and at boundary values.

🔍 Why it Matters:
Most bugs occur at the edge of input boundaries, making BVA highly effective in detecting errors.

💡 Actionable Tip:
Always test one value below, at, and above the limit. For example, if a field accepts 1–100, test with 0, 1, 100, and 101.

Documentation:

• Writing test cases

• Maintaining test execution reports

• Defect tracking (e.g., JIRA, Bugzilla)
  
  

Soft Skills:

• Effective communication with developers
• Prioritizing test cases

• Handling deadlines and pressure