Disable Preloader

Software testing is the process of verifying a system with the purpose of identifying any errors, gaps or missing requirement versus the actual requirement. Software testing is broadly categorised into two types - functional testing and non-functional testing. Testing is the process of evaluating a system or its component(s) with the intent to find whether it satisfies the specified requirements or not. Testing is executing a system in order to identify any gaps, errors, or missing requirements in contrary to the actual requirements. This tutorial will give you a basic understanding on software testing, its types, methods, levels, and other related terminologies.

Module List

  • Fundamentals of Testing
  • Testing Throughout the Software Life Cycle
  • Static Techniques
  • Test Design Techniques
  • Test Management
  • Tool Support for Testing

Course Details

    • Why is Testing Necessary (K2)
      • Software Systems Context (K1)
      • Causes of Software Defects (K2)
      • Role of Testing in Software Development, Maintenance and Operations (K2)
      • Testing and Quality (K2)
      • How Much Testing is Enough? (K2)
    • What is Testing? (K2)
    • Seven Testing Principles (K2)
    • Fundamental Test Process (K1)
      • Test Planning and Control (K1)
      • Test Analysis and Design (K1)
      • Test Implementation and Execution (K1)
      • Evaluating Exit Criteria and Reporting (K1)
      • Test Closure Activities (K1)
    • The Psychology of Testing (K2)
    • Code of Ethics (K2)

    • Software Development Models (K2)
      • V-model (Sequential Development Model) (K2)
      • Iterative-incremental Development Models (K2)
      • Testing within a Life Cycle Model (K2)
    • Test Levels (K2)
      • Component Testing (K2)
      • Integration Testing (K2)
      • System Testing (K2)
      • Acceptance Testing (K2)
    • Test Types (K2)
      • Testing of Function (Functional Testing) (K2)
      • Testing of Non-functional Software Characteristics (Non-functional Testing) (K2)
      • Testing of Software Structure/Architecture (Structural Testing) (K2)
      • Testing Related to Changes: Re-testing and Regression Testing (K2)
    • Maintenance Testing (K2)

    • Static Techniques and the Test Process (K2)
    • Review Process (K2)
      • Activities of a Formal Review (K1)
      • Roles and Responsibilities (K1)
      • Types of Reviews (K2)
      • Success Factors for Reviews (K2)
    • Success Factors for Reviews (K2)

    • The Test Development Process (K3)
    • Categories of Test Design Techniques (K2)
    • Specification-based or Black-box Techniques (K3)
      • Equivalence Partitioning (K3)
      • Boundary Value Analysis (K3)
      • Decision Table Testing (K3)
      • State Transition Testing (K3)
      • Use Case Testing (K2)
    • Structure-based or White-box Techniques (K4)Experience-based Techniques (K2)
      • Statement Testing and Coverage (K4)
      • Decision Testing and Coverage (K4)
      • Other Structure-based Techniques (K1)
    • Experience-based Techniques (K2)
    • Choosing Test Techniques (K2)

    • Test Organization (K2)
      • Test Organization and Independence (K2)
      • Tasks of the Test Leader and Tester (K1)
    • Test Planning and Estimation (K3)
      • Test Planning (K2)
      • Test Planning Activities (K3)
      • Entry Criteria (K2)
      • Exit Criteria (K2)
      • Test Estimation (K2)
      • Test Strategy, Test Approach (K2)
    • Test Progress Monitoring and Control (K2)
      • Test Progress Monitoring (K1)
      • Test Reporting (K2)
      • Test Control (K2)
    • Configuration Management (K2)
    • Risk and Testing (K2)
      • Project Risks (K2)
      • Product Risks (K2)
    • Incident Management (K3)

    • Types of Test Tools (K2)
      • Understanding the Meaning and Purpose of Tool Support for Testing (K2)
      • Test Tool Classification (K2)
      • Tool Support for Management of Testing and Tests (K1)
      • Tool Support for Static Testing (K1)
      • Tool Support for Test Specification (K1)
      • Tool Support for Test Execution and Logging (K1)
      • Tool Support for Performance and Monitoring (K1)
      • Tool Support for Specific Testing Needs (K1)
    • Effective Use of Tools: Potential Benefits and Risks (K2)
      • Potential Benefits and Risks of Tool Support for Testing (for all tools) (K2)
      • Special Considerations for Some Types of Tool (K1)
    • Introducing a Tool into an Organization (K1)

Training Advantages
35 contact hours
Industry Case Studies
Industry case studies
Real time training


  1. Unit Testing.
  2. Integration Testing.
  3. System Testing.
  4. Sanity Testing.

Software testing is in demand. It is relatively easy to start a career in product/software testing. Testing tools are easy to learn. Software testing is an important process of the software development life cycle.

SDLC defines all the standard phases which are involved during the software development process, whereas the STLC process defines various activities to improve the quality of the product. SDLC is a Development Life Cycle whereas STLC is a Testing Life Cycle.

Manual testing is simply underappreciated today, and any self-respecting QA Engineer is forcefully being morphed into performing what many fail to realize is truly a software engineering effort of itself. At a high level, software QA as a guiding process is dying, though testing will always be needed.