Manual Testing

• 
  

  Manual Testing is the process of manually executing test cases without using automation tools to identify defects in software.

  
  

Key Benefits:

• 
  

  Detects UI/UX issues better than automation.

  
  


• 
  

  Useful for exploratory, usability, and ad-hoc testing.

  
  


• 
  

  Cost-effective for small-scale projects.

  
  


• 
  

  Allows human intuition and observation, which automation cannot replicate.

  
  

Types of Manual Testing:

• 
  

  Functional Testing – Validates the application's functionality.

  
  


• 
  

  Regression Testing – Ensures new changes don’t affect existing features.

  
  


• 
  

  Usability Testing – Checks the user-friendliness of the application.

  
  


• 
  

  Exploratory Testing – Performed without predefined test cases to identify unexpected defects.

  
  

Manual Testing Process (Software Testing Life Cycle - STLC):

• 
  

  Requirement Analysis – Understand the system requirements.

  
  


• 
  

  Test Planning – Define scope, strategy, and resources.

  
  


• 
  

  Test Case Design – Write detailed test cases.

  
  


• 
  

  Test Execution – Run test cases manually.

  
  


• 
  

  Defect Reporting – Log bugs and issues.

  
  


• 
  

  Test Closure – Document results and lessons learned.

  
  

Common Tools for Manual Testing:

• 
  

  TestRail, JIRA, Bugzilla – Test case & defect management.

  
  


• 
  

  Postman – For API testing.

  
  


• 
  

  Excel/Google Sheets – Simple test case documentation.