Let’s go deeper into the core concepts of Manual Testing so you can build a strong foundation.


πŸ“Œ Manual Testing Concepts

1. Software Testing Basics

  • Definition: The process of evaluating software to ensure it meets requirements and works correctly.
  • Goal: Find defects and improve quality.
  • Testing vs Debugging:
    • Testing = Finding defects.
    • Debugging = Fixing defects.

2. Verification vs Validation

  • Verification β†’ “Are we building the product right?” (checking documents, design, code).
  • Validation β†’ “Are we building the right product?” (checking actual software).

3. SDLC & STLC

  • SDLC (Software Development Life Cycle) β†’ Phases of software development (Requirement β†’ Design β†’ Coding β†’ Testing β†’ Deployment β†’ Maintenance).
  • STLC (Software Testing Life Cycle) β†’ Phases of testing within SDLC:
    1. Requirement Analysis
    2. Test Planning
    3. Test Case Design
    4. Test Environment Setup
    5. Test Execution
    6. Defect Reporting
    7. Test Closure

4. Types of Testing

A. Based on Knowledge

  • Black Box Testing β†’ Focus on inputs/outputs (no knowledge of code).
  • White Box Testing β†’ Test internal logic and code paths.
  • Gray Box Testing β†’ Partial knowledge of code.

B. Based on Purpose

  • Functional Testing β†’ Does the software do what it should?
  • Non-Functional Testing β†’ Performance, load, security, usability.

5. Levels of Testing

  1. Unit Testing β†’ Smallest part (function/module).
  2. Integration Testing β†’ Interaction between modules.
  3. System Testing β†’ Full application as a whole.
  4. User Acceptance Testing (UAT) β†’ Tested by client/end users.

6. Test Case & Test Scenario

  • Test Case = Step-by-step instructions with input, action, and expected result.
  • Test Scenario = High-level idea of what to test (broader than test case).

πŸ‘‰ Example:

  • Scenario: Verify login functionality.
  • Test Case: Enter valid username/password β†’ Click login β†’ User should land on dashboard.

7. Defect / Bug

  • Defect/Bug β†’ A mismatch between expected and actual result.
  • Bug Life Cycle (Status Flow):
    New β†’ Assigned β†’ Open β†’ Fixed β†’ Retested β†’ Closed/Rejected/Deferred

8. Testing Techniques

  • Equivalence Partitioning (EP) β†’ Divide inputs into valid/invalid groups.
  • Boundary Value Analysis (BVA) β†’ Test at boundaries (e.g., age input: 17, 18, 100, 101).
  • Error Guessing β†’ Tester uses experience to find defects.

9. Regression vs Retesting

  • Retesting β†’ Testing the same defect after it is fixed.
  • Regression Testing β†’ Checking that fixing one bug didn’t break other areas.

10. Entry & Exit Criteria

  • Entry Criteria β†’ Conditions before testing starts (requirements ready, environment setup).
  • Exit Criteria β†’ Conditions to stop testing (all planned tests executed, major bugs fixed).

11. Manual Testing Tools (Supporting, not automation)

  • Bug Tracking Tools β†’ JIRA, Bugzilla, Mantis.
  • Test Management Tools β†’ TestRail, Quality Center, Zephyr.

βœ… In Summary:
Manual Testing concepts cover STLC, levels of testing, test case design, bug life cycle, verification vs validation, regression vs retesting, and test techniques.

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *