Tutorials Hut

  • Testing Foundation

      Basics of Software Testing
       What is Software Testing?
       Objective of Testing
       Why is testing necessary?
       Common Terms used in Testing
       Verification Vs Validations
       QA Vs QC
       Debugging Vs Testing
       Seven Testing Principles
       SDLC Vs STLC
       Fundamentals of Test Process
       Software quality Factors
       Software Development Models
       Waterfall Model
       V models
       Iterative Model
       Test Levels
       Component Testing
       Integration Testing
       System Testing
       Acceptance Testing
       Strategies for Integration Testing
       Big Bang
       Stubs and Driver
       Top Down Testing
       Bottom Up Testing
       Test Types
       Functional Testing
       Non- Functional Testing
       Structural Testing
       Re-testing & Regression Testing
       Static AND Dynamic Techniques
       Static Technique
       Dynamic Technique
       Static Analysis by Tools
       White Box Techniques
       Statement Coverage Testing
       Branch Coverage Testing
       Decision Coverage Testing
       Path Coverage
       Black Box Techniques
       Equivalence Partitioning
       Boundary Value Analysis
       Decision Table testing
       State Transition testing
       Experience Based TestingTechniques
       Random Testing
       Exploratory Testing
       Error Guessing
       Functional Testing
       Integration Testing
       Unit Testing
       System Testing
       Smoke testing
       Sanity testing
       Regression Testing
       Usability Testing
       Security Testing
       User Acceptance Testing
       White Box & Black Box Testing
       Globalization & Localization Testing
       Non Functional Testing
       Compatibility testing
       Endurance testing
       Load testing
       Performance testing
       Recovery testing
       Scalability testing
       Stress testing
       Volume testing
       Test Planning and Estimation
       Test Planning
       Test Strategies Vs Test Plan
       Test Approaches
       Risk and Testing
       Product Risks
       Project Risks
       Defect Management
       Defect LifeCycle
       Severity Vs Priority
  • Integration Testing

    Integration means combining. Different tests interfaces between components, interactions with different parts of a system, such as the operating system, file system and hardware, and interfaces are combined and tested

    The strategy employed can significantly affect the time and effort required to yield a working, higher-level element.

    Note: ‘‘integration testing’’ is sometimes defined as the level of testing between unit and system..

    Some features of integration testing

      • Testing done to verify communication of data and actions across different systems, hardware, software or environmental components. 
      • It also tests nonfunctional aspects. 
      • Performed after integration of modules, software and external components. 
      • Integration techniques are used.Preferably this should be in incremental mode rather than a BIG BANG approach as it’s harder to isolate failures 
      • Aims to remove defects and performance issues due to integration of various systems.

    Test Level

    Test Basis


    Responsible Person

    Integration Testing

    Software and system design



    Use cases

    Sub-systems database implementation




    There may be more than one level of integration testing 

      1. Component Integration Testing: tests the interactions between software components and is done after component testing  
      2. System Integration Testing: tests the interactions between different systems or between hardware and software and may be done after system testing. 
    Recommended Articles:  

    Leave a Reply

    Your email address will not be published. Required fields are marked *