Manual Testing

Software testing is an investigation conducted to provide stakeholders with information about the quality of the product.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.


Software testing is an activity to check whether the actual results match the expected results and to ensure that the software system is defect free. It involves execution of a software component or system component to evaluate one or more properties of interest.

Why is Software Testing Important?

Testing is important because software bugs could be expensive or even dangerous. Software bugs can potentially cause monetary and human loss, history is full of such examples.

  • In April 2015, Bloomberg terminal in London crashed due to software glitch affected more than 300,000 traders on financial markets. It forced the government to postpone a 3bn pound debt sale.
  • Nissan cars have to recall over 1 million cars from the market due to software failure in the airbag sensory detectors. There has been reported two accident due to this software failure.
  • Starbucks was forced to close about 60 percent of stores in the U.S and Canada due to software failure in its POS system. At one point store served coffee for free as they unable to process the transaction.
  • Some of the Amazon’s third party retailers saw their product price is reduced to 1p due to a software glitch. They were left with heavy losses.
  • Vulnerability in Window 10. This bug enables users to escape from security sandboxes through a flaw in the win32k system.
  • In 2015 fighter plane F-35 fell victim to a software bug, making it unable to detect targets correctly.
  • China Airlines Airbus A300 crashed due to a software bug on April 26, 1994, killing 264 innocent live
  • In 1985, Canada's Therac-25 radiation therapy machine malfunctioned due to software bug and delivered lethal radiation doses to patients, leaving 3 people dead and critically injuring 3 others.
  • In April of 1999, a software bug caused the failure of a $1.2 billion military satellite launch, the costliest accident in history
  • In may of 1996, a software bug caused the bank accounts of 823 customers of a major U.S. bank to be credited with 920 million US dollars.


SDLC: SDLC is Software Development Life Cycle. It is the sequence of activities carried out by Developers to design and develop high-quality software.

Though SDLC uses the term ‘Development’, it does not involve just coding tasks done by developers but also incorporates the tasks contributed by testers and stakeholders.

In SDLC, test cases are created.

STLC: STLC is Software Testing Life Cycle. It consists of series of activities carried out by Testers methodologically to test your software product.

Though STLC uses the term “testing” it does not involve just testers, at some instances, they have to involve developers as well.

Course Features

Industry professionals as Trainers

  • Well researched advanced course content created by Industry professionals
  • Assignments
  • Live web design project
  • Technical HR Interview preparations
  • Exam and Industry recognised Certificate

Course Syllabus

  1. Fundamental of Testing
    1. What is software testing?
    2. Why is testing necessary?
    3. Testing Participants
    4. Testing Principles
    5. Best Practices in Testing
    6. Skills For Testing
  2. Software Development Life Cycle
    1. Introduction of Software Process
    2. The PDCA cycle
    3. Phases in SDLC
    4. Waterfall Model
      1. Phases of Waterfall Model
      2. Advantages & Disadvantages
    5. Spiral Model
      1. Phases of Spiral Model
      2. Spiral Model Strengths & Weaknesses
      3. When should you use Spiral Model
    6. Incremental Model
      1. Phases
      2. Advantages & Disadvantages
    7. Agile Model
      1. Scrum methodology
      2. Sprints in Scrum
      3. Scrum Roles
      4. Scrum Artifacts & Ceremonies
    8. V shaped Model
      1. Steps in the V-shaped Model
      2. V-shaped Strengths & Weaknesses
    9. CMMI Model
      1. CMMI Levels & KPAs
  3. Software Testing Life Cycle
    1. Requirements Analysis
    2. Test Planning
    3. Test Analysis
    4. Test Design
    5. Construction and verification
    6. Testing Cycles
    7. Final Testing and Implementation
    8. Post Implementation
  4. Verification
    1. The V-V Model
    2. Inspections
    3. Walk through
    4. Peer reviews
    5. Technical Reviews
    6. Audits
    7. Verification Benefits
  5. Validation
    1. Introduction of Validation
    2. Unit Testing
    3. Functional Testing
    4. System Testing
    5. User Acceptance Testing
      1. Alpha Testing
      2. Beta Testing
    6. Accessibility Testing
    7. Manual Support Testing
    8. User Interface Testing
    9. Bottom-Up Approach
    10. Top-Down Approach
    11. Big Bang Approach & its Issues
    12. Hybrid Approach
    13. Stub v/s Driver
  6. Non-Functional testing
    1. Security Testing
    2. Recovery Testing
    3. Configuration testing
    4. Compatibility Testing
    5. Inter-system Testing
    6. Installation Testing
    7. Performance Testing
    8. Availability Testing
    9. Parallel Testing
    10. Volume Testing
    11. Internationalization Testing
    12. Localization Testing
  7. Performance Testing
    1. Performance Testing Concepts
    2. Pre-requisites of Performance Testing
    3. Performance Test Types
      1. Load Testing
      2. Stress Testing
      3. Soak Testing
      4. Spike Testing
      5. Volume Testing
      6. Scalability Testing
    4. Common Performance Problems
    5. Performance Testing Process
  8. Other Types of testing
    1. Mutation Testing
    2. Progression Testing
    3. Re-Testing
    4. Regression Testing
    5. Sanity v/s Smoke Testing
    6. Ad-hoc Testing
      1. Monkey Testing
      2. Buddy Testing
      3. Exploratory Testing
    7. Ad-hoc Testing Methods
      1. Pair Testing
      2. Defect Seeding
    8. Mutation Testing v/s Defect Seeding
  9. Quality
    1. What is Quality?
    2. Quality Views
    3. Quality – Productivity
    4. Software Quality
    5. Quality Control (QC)
    6. Quality Assurance (QA)
  10. Risk Analysis
    1. What is Risk?
    2. Risk Analysis
    3. Risk Analysis Graph
    4. Risk Management
    5. Risk Mitigation
    6. Risk Mitigation Graph
  11. Black Box
    1. What is Black Box testing
    2. Test Case Design Methods
    3. Equivalence Partitioning
    4. Decision Tables
    5. Boundary value Analysis
    6. State Transition Testing
    7. Error guessing
    8. Use-case Based Testing
    9. Advantages & Disadvantages of Black Box Testing
  12. White Box
    1. Statement Coverage
    2. Decision Coverage
    3. Condition Coverage
    4. Cyclomatic Complexity
    5. Advantages & Disadvantages of WBT
    6. Gray Box Testing
  13. Test management
    1. Test Organization
    2. Test Strategy
    3. Test Plan
    4. Estimates
    5. Advantages & Disadvantages of WBT
    6. Test progress monitoring and control
  14. Test cases
    1. Test Scenario
    2. Characteristic of a good Test Case
    3. Structure of test case
    4. Test Case Template
    5. Writing your Test Cases
    6. Test Case Review
      1. Peer-to-peer Reviews
      2. Team Lead Reviews
      3. Team Manager Review
    7. Test Case Execution Process
  15. Defect Management
    1. Understanding Defects
    2. Priority v/s Severity
    3. Defect Report Template
    4. IEEE 829 Defect Report format
    5. Defect Tracking Sheet
    6. Defect Submission
    7. Defect lifecycle
    8. Status of Lifecyle stages
    9. Understanding Defect Age
    10. Format of defect report
    11. Defect Density
    12. Defect Types
  16. RTM (Requirements Traceability Matrix)
    1. Generating a Traceability Matrix
    2. Types Of Traceability Test Matrix
  17. Mobile Testing
    1. Overview of Mobile Devices
    2. Types of Mobile Devices
    3. Mobile Application Testing
    4. Different Mobile Platforms
    5. Types of Mobile Applications
      1. Native App
      2. Web App
      3. Hybrid App
  18. Mobile Applications Test Types
    1. Mobile Testing Types
    2. Testing for the devices
    3. Testing for the connectivity
    4. Functional Testing
    5. Memory Leakage Testing
    6. Interrupt Testing
    7. Usability Testing
    8. Installation Testing
    9. Operational Testing
    10. Security Testing
    11. Connectivity Options
    12. Mobility Testing Process
    13. Field Testing
  19. Web Application Testing
    1. Threats & Risks
    2. Testing Range
    3. Testing Strategies
    4. Test Planning
    5. Test Cases, Scripts, Suites & Scenarios
    6. Selecting Test Loads
    7. Load and Stress testing
    8. Security Testing
    9. Test For Navigation
  20. Quality Center (QC) Overview
    1. QC Introduction
    2. Components
    3. Requirements Module
    4. Test Plan Module
    5. Test Linkage
    6. Test Lab Module
    7. Defects Module
    8. Defects Linkage
    9. Traceability
  21. Manual Testing Project
    1. Case Study
    2. Understanding Business Requirement
    3. Creating Test Case
    4. Executing Test Cases
    5. Logging defects

Upcoming Batches

Job Profile

Who Is Hiring?


What Is Next?

Send Enquiry

Enter only Alphabets!Name is required.
E-mail ID is required.Invalid Email address.

Enter a valid contact no.

Congratulations!!! Your enquiry has been sent successfully. Our executive will call you shortly. Call : 8999417889.

Contact Us

Web Touch India Solution

Mobile :

Email Address :