What Does Manual Testing Mean?

 In software testing, manual testing is the process of manually reviewing and testing a software/application for errors, defects and/or vulnerabilities. This type of testing is performed by software developers and testers, without any automated tools, to identify any defects within the software from the perspective/experience of an end user.

Manual testing is usually part of a comprehensive software testing process and is performed prior to software release. Software testers use and review the developed software the way an end user would use it. 

The testing process can be a systematic process that uses formal test plans and action cases or can informally be performed by a user domain expert. Software can be tested for multiple user roles such as for software admin and software user—both using software but in a different way

Manual testing is a testing process that is carried out manually in order to find defects without the usage of tools or automation scripting. A test plan document is prepared that acts as a guide to the testing process in order to have the complete test coverage.

Following are the testing techniques that are performed manually during the test life cycle: 

  • Acceptance Testing 
  • White Box Testing 
  • Black Box Testing 
  • Unit Testing 
  • System Testing Integration Testing


Testing Overview

  • What is testing?
  • Why Test?
  • Cost Of Quality
  • When to Start Testing/Stop Testing?
  • Who can Test?
  • What are needed for Testing?


  • What is SDLC?
  • ETVX
  • Waterfall
  • Spiral
  • V-Model.
  • Agile Model.

Testing Methodologies

  • White Box
  • Black Box
  • Grey Box
    • White Box Testing
      • Static Testing
        • Desk Checking
        • Code Walkthrough
        • Inspection
      • Structural Testing
        • Code coverage
        • Statement Coverage
        • Path Coverage
        • Function Coverage
        • Condition coverage
        • Code Complexity:
        • Cyclomatic

Black Box Testing

  •   Requirements Based Testing
  •   Positive and Negative Testing
  •   Boundary Value Analysis
  •   Equivalence Class Partitioning
  •   State Based Testing
  •   Decision Tables.
  •   Documentation Testing.
  •   Compatibility Testing.
  •   Domain Testing.

Use Case/Test Case

  •   What is Use Case?
  •   What is a Test Case?
  •   Relationship between Use-Case and a Test Case.
  •   What makes a good Test Case?
  •   Test Case writing techniques

Integration Testing Types of Integration:

  •   Top-down Integration
  •   Bottom-Up Integration
  •   Bi-Directional Integration
  •   Total System Integration(Big Bang)

System and Acceptance Testing

  •   Design/Architecture Testing.
  •   Business Vertical Testing.
  •   Deployment Testing.
  •   Beta Testing.
  •   Certification, Standards and Testing for Compliance

Regression Testing

  •   What is Regression Testing?
  •   When to do Regression Testing?
  •   How to do Regression Testing?
  •   Advantages of Regression Testing.

    Key Highlights

    • Real Time-Trainers
    • Mock Interviews on every Saturday
    • Per batch 8 members only
    • 24/7 LAB Access
    • Resume Preparation
    • Certificate
    • 100% Job oriented training program
    • Real Time Projects after course completion
    • Tasks on daily basis
    • Timings of Learners Conveniences

    Join with us to start your career