Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 253 views

    Integration

    Uploaded by

    Yogendra Rajavat
    Integration testing verifies the interaction between software components by testing them as a group. There are several types of integration testing, including top-down, bottom-up, bi-directional, and system/big bang testing. Top-down testing tests high-level modules and stubs replace lower-level modules. Bottom-up testing tests lower-level modules individually and then integrates them, testing subsystems separately before the full system. Bi-directional testing combines top-down and bottom-up approaches. System/big bang testing integrates all modules at once, which is high-risk. Integration testing has phases like scenario testing using test cases replicating user usage and defect bash testing where people from different roles test together simultaneously.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd

    Integration

    Uploaded by

    Yogendra Rajavat
    253 views12 pages
    Integration testing verifies the interaction between software components by testing them as a group. There are several types of integration testing, including top-down, bottom-up, bi-directional, and system/big bang testing. Top-down testing tests high-level modules and stubs replace lower-level modules. Bottom-up testing tests lower-level modules individually and then integrates them, testing subsystems separately before the full system. Bi-directional testing combines top-down and bottom-up approaches. System/big bang testing integrates all modules at once, which is high-risk. Integration testing has phases like scenario testing using test cases replicating user usage and defect bash testing where people from different roles test together simultaneously.

    Original Description:

    Method of testing

    Original Title

    Integration Ppt

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Integration testing verifies the interaction between software components by testing them as a group. There are several types of integration testing, including top-down, bottom-up, bi-directional, and system/big bang testing. Top-down testing tests high-level modules and stubs replace lower-level modules. Bottom-up testing tests lower-level modules individually and then integrates them, testing subsystems separately before the full system. Bi-directional testing combines top-down and bottom-up approaches. System/big bang testing integrates all modules at once, which is high-risk. Integration testing has phases like scenario testing using test cases replicating user usage and defect bash testing where people from different roles test together simultaneously.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    253 views12 pages

    Integration

    Uploaded by

    Yogendra Rajavat
    Integration testing verifies the interaction between software components by testing them as a group. There are several types of integration testing, including top-down, bottom-up, bi-directional, and system/big bang testing. Top-down testing tests high-level modules and stubs replace lower-level modules. Bottom-up testing tests lower-level modules individually and then integrates them, testing subsystems separately before the full system. Bi-directional testing combines top-down and bottom-up approaches. System/big bang testing integrates all modules at once, which is high-risk. Integration testing has phases like scenario testing using test cases replicating user usage and defect bash testing where people from different roles test together simultaneously.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    of 12

    TOPIC

    INTEGRATION TESTING
    Definition - What does Integration
    Testing mean?

    Integration testing is a software testing methodology used to
    test individual software components or units of code to verify
    interaction between various software components and detect
    interface defects.

    Components are tested as a single group or organized in an
    iterative manner.

    Types Of Integration Testing

    Top-Down

    Bottom-Up

    Bi-directional (sandwich)

    System intregation testing (big bang)
    Top-Down Integration Testing
    Top-down integration testing is an integration testing
    technique used in order to simulate the behaviour of the
    lower-level modules that are not yet integrated.

    Stubs are the modules that act as temporary replacement for
    a called module and give the same output as that of the
    actual product.

    The replacement for the 'called' modules is known as 'Stubs'
    and is also used when the software needs to interact with an
    external system.
    Top Down Integration - Flow Diagram

    Bottom Up Testing

    Each component at lower hierarchy is tested individually and
    then the components that rely upon these components are
    tested.

    In bottom-up testing, each subsystem is tested separately and
    then the full system is tested.

    All the bottom or low-level modules, procedures or functions
    are integrated and then tested.
    Bottom Up Integration - Flow Diagram



    Bi-directional Integration (Sandwich)

    Bi-directional Integration, is a kind of integration testing
    process that combines top-down and bottom-up testing.


    Bi-directional Integration testing is a vertical incremental
    testing strategy that tests the bottom layers and top layers
    and tests the integrated system in the computer software
    development process.


    System Integration Testing(Big Bang)


    Involves integrating the modules to build a complete
    software system. This is considered a high-risk
    approach because it requires proper documentation
    to prevent failure.

    This is very similar to system testing as this basically
    has a whole system before starting the testing.

    Phases Of Integration Testing

    Two types of phases:-

    Scenario testing

    Defect bash
    Scenario Testing

    Scenario testing helps testers to explore how the software will
    work in the hands of an end user.
    Scenario testing is done by creating test scenarios which
    replicate the end users usage.
    A test scenario can be a independent test case or a series of
    test cases that follow each other.
    Test scenario is just a story which explains the usage of the
    software by any end user.

    Defect Bash Testing


    It is an ad hoc testing where people performing different role
    in an organization test the product together at the same time.

    This is very popular among application development
    companies, where the product can be used by who perform
    different roles.

    You might also like