Manual Testing

MANUAL TESTING TRAINING COURSE SYLLABUS

What Is Manual Testing...?

Manual testing is a software testing process in which test cases are executed manually without using any automated tool. All test cases executed by the tester manually according to the end user's perspective. It ensures whether the application is working, as mentioned in the requirement document or not. Test cases are planned and implemented to complete almost 100 percent of the software application. Test case reports are also generated manually. Manual Testing is one of the most fundamental testing processes as it can find both visible and hidden defects of the software. The difference between expected output and output, given by the software, is defined as a defect. The developer fixed the defects and handed it to the tester for retesting. Manual testing is mandatory for every newly developed software before automated testing. This testing requires great efforts and time, but it gives the surety of bug-free software. Manual Testing requires knowledge of manual testing techniques but not of any automated testing tool. Manual testing is essential because one of the software testing fundamentals is "100% automation is not possible."

Trainer

BalaMurugan T

Available Seats

30

Schedule

5.00 pm - 7.00 pm

Software Testing Overview

  • Introduction to Software Testing
  • Objectives of Testing
  • Software Development Process
  • Project vs. Product
  • Error / Fault / Failure
  • Why Software has defects?
  • Most common defects
  • Cost of fixing defects
  • What is Verification & Validation
  • Difference between QA & QC
  • Role of a Tester

    • Principles of Testing

  • Early Testing
  • Exhaustive Testing Impossible
  • Defect Clustering
  • Pesticide Paradox
  • Testing is Context Dependent
  • Testing Should Show Presence of Defects
  • Absence of Error is a Fallacy

    • Software Development Life Cycle (SDLC)

  • SDLC Phases
  • SDLC Models RAD
    1. Waterfall Model
    2. V Model
    3. Prototype Model
    4. Spiral Model
    5. Model Agile Model

    Software Testing Methodologies

  • Static Testing
  • White Box Testing
  • Black Box Testing
  • Gray Box Testing

    • Static Testing Techniques

  • Reviews
  • Walkthroughs

    • White Box Testing

  • Unit Testing
  • Integration Testing

    • Black Box Testing

  • System Testing
  • User Acceptance Testing (UAT)
    1. Alpha Testing
    2. Beta Testing

    System Testing and Types of System Testing

  • Smoke / Sanity Testing
  • Formal Testing
  • Priority Based/Risk Based Testing
  • Ad-hoc Testing
  • Re-Testing and Regression Testing
  • End-to-End Testing
  • Exploratory Testing
  • Benchmark Testing
  • Monkey Testing
  • UI Testing
  • Usability Testing
  • Security Testing
  • Performance Testing
  • Load Testing
  • Stress Testing
  • Compatibility Testing
  • Installation Testing
  • Globalization Testing
  • Localization Testing
  • Recovery Testing

    • Software Testing Life Cycle (STLC)

  • Test Planning
    1. Test Strategy
    2. Test Plan
  • Test Analysis
    1. Analyzing Functional Requirements
    2. Preparing Requirement Clarification
  • Test Preparation
    1. Identifying & documenting Test Scenarios
    2. Test Case Design Techniques
  • ECP
  • BVA
  • Decision Table Testing
  • State Transition Testing
  • Use case Testing
    1. Preparing Test Cases
    2. Preparing Test Data
    3. Preparing RTM
  • Test Execution
    1. Build Release Process
    2. Executing Testcases
  • Defect / Bug Life Cycle
  • Defect Management
    1. What is defect?
    2. Defect Classification
    3. Defect Severity & Defect Priority
    4. Defect Report Template
    5. Defect Reporting & Defect Tracking
  • Test Closure
    1. Criteria for Test Closure
    2. Status Reports (Daily and Weekly)
    3. Test Summary Reports
  • Agile Testing
  • Database Testing

    • Test & Defect Management Tools

  • ALM (Quality Center)
  • Jira