• Like

Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Integration test

  • 739 views
Uploaded on

Integration test & concept explained easily

Integration test & concept explained easily

More in: Education
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
739
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
24
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Software Integration Testing Speaker: Jerry Gao Ph.D. San Jose State University email: jerrygao@email.sjsu.edu URL: http://www.engr.sjsu.edu/gaojerry
  • 2. Topic: Software Integration Testing - What is Software Integration Testing? - Non-Incremental Software Integration - Incremental Software Integration - Traditional software Integration Strategies - Software Integration Test Harness -Test Stubs and Test Drivers - Object-Oriented Software Integration Strategies Jerry Gao Ph.D. 7/20002 Presentation Outline All Rights Reserved
  • 3. Topic: Software Integration Testing What is Software Integration Testing? Testing activities that integrate software components together to form a complete system. To perform a cost-effective software integration, integration test strategy, integration test set are needed. Major testing focuses: - Interfaces between modules (or components) - Integrated functional features - Interacting protocols and messages - System architectures Who perform software integration: Developers and test engineers What do you need?: - Integration strategy - Integration test environment and test suite - Module (or component) specifications - Interface and design documents Jerry Gao Ph.D. 7/2002 What is White-Based Software Testing?
  • 4. Topic: Software Integration Testing What is a software integration strategy? Software test strategy provides the basic strategy and guidelines to test engineers to perform software testing activities in a rational way. Software integration strategy usually refers to --> an integration sequence (or order) to integrate different parts (or components) together. A test model is needed to support the definition of software integration test strategies. Typical test models: control flow graph object-oriented class diagram scenario-based model component-based integration model architecture-based integration model Jerry Gao Ph.D. 7/2002 Software Integration Strategy
  • 5. Jerry Gao Ph.D. 7/2002 Topic: Software Integration Testing Traditional Software Integration Strategy There are two groups of software integration strategies: - Non Incremental software integration - Incremental software integration Non Incremental software integration: --> Big band integration approach Incremental software integration: --> Top- down software integration --> Bottom-up software integration --> Sandwich integration
  • 6. Topic: Software Integration Testing Jerry Gao Ph.D. 7/2002 Test Stubs and Test Drivers What are software test stubs? - Software test stubs are programs which simulate the behaviors of software components (or modules) that are the dependent modules of a under test module. Typical stubs relates to a under test module in the following ways: UT Module Dependent Module Stub Functional call without parameters and return values UT Module Dependent Module Stub Functional call with parameters and return values UT Module Dependent Module Stub Functional call with input parameters only
  • 7. Topic: Software Integration Testing Jerry Gao Ph.D. 7/2002 Test Stubs and Test Drivers What are software test drivers? - Software test drivers are programs which simulate the behaviors of software components (or modules) that are the control modules of a under test module. Typical drivers relates to a under test module in the following ways: UT Module Control Module Driver Functional call without parameters and return values UT Module Control Module Driver Functional call with parameters and return values UT Module Control Module Driver Functional call with input parameters only
  • 8. Non-incremental integration: - Big Band - combine (or integrate) all parts at once. Advantages: simple Disadvantages: - hard to debugging, not easy to isolate errors - not easy to validate test results - impossible to form an integrated system Jerry Gao Ph.D. 7/2002 Topic: Software Integration Testing Traditional Software Integration Strategy
  • 9. Top-down Integration Idea:-Modules are integrated by moving downward through the control structure. Modules subordinate to the main control module are incorporated into the system in either a depth-first or breadth-first manner. Integration process (five steps): 1. the main control module is used as a test driver, and the stubs are substituted for all modules directly subordinate to the main control module. 2. subordinate stubs are replaced one at a time with actual modules. 3. tests are conducted as each module is integrated. 4. On completion of each set of tests, another stub is replaced with the real module. 5. regression testing may conducted. Pros and cons top-down integration: - stub construction cost - major control function can be tested early. Jerry Gao Ph.D. 7/2002 Topic: Software Integration Testing
  • 10. Topic: Software Integration Testing Jerry Gao Ph.D. 7/2002 Top-Down Integration Main M1 M3 M2 M7 M6 M5 M4 M8 Select the integration sequence: Depth-First Breadth-First - Left --> Right - Right --> Left 1 2 3 4 5 6 7 8
  • 11. Topic: Software Integration Testing Jerry Gao Ph.D. 7/2002 Top-Down Integration Integration Order: Breadth-First (Left Order) IS: Integrated System Mi ’: software stub for Module Mi. Step #1: IS = Main + M1 (need: M2’, M3’, M4’ and M5’) Step #2: IS = IS + M2 (need: M4’, M5’, M6’, and M3’) Step #3: IS = IS + M3 (need: M4’, M5’, M6’, and M7’) Step #4: IS = IS + M4 (need: M5’, M6’,and M7’) Step #5: IS = IS + M5 (need: M8’, M6’, and M7’) Step #6: IS = IS + M6 (need: M7’, and M8’) Step #7: IS = IS + M7 (need: M8’) Step #8: IS = IS + M8
  • 12. Topic: Software Integration Testing Jerry Gao Ph.D. 7/2002 Bottom-Up Software Integration Idea:- Modules at the lowest levels are integrated at first, then by moving upward through the control structure. Integration process (five steps): 1. Low-level modules are combined into clusters that perform a specific software sub-function. 2. A driver is written to coordinate test case input and output. 3. Test cluster is tested. 4. Drivers are removed and clusters are combined moving upward in the program structure. Pros and cons of bottom-up integration: - no stubs cost - need test drivers - no controllable system until the last step
  • 13. Topic: Software Integration Testing Jerry Gao Ph.D. 7/2002 Bottom-Up Integration Main M1 M3 M2 M7 M6 M5 M4 M8 1 5 3 4 9 7 6 2 8
  • 14. Topic: Software Integration Testing Jerry Gao Ph.D. 7/2002 Bottom-Up Integration Integration Order: Breadth-First (Left Order) IS: Integrated System Mi”: software driver for Module Mi. Step #1: IS1 = M8 + M4 (need: M5” and M1”) Step #2: IS1 = IS1 + M5 (need: M1”) Step #3+4: IS1 = IS1 + M1 (need: Main”) Step #5: IS2 = M2 + M6 (need: Main”) Step #6: IS3 = M3 + M7 (need: Main”) Step #7: IS = IS1 + Main Step #7: IS = IS + IS2 Step #8: IS = IS + IS3
  • 15. Topic: Software Integration Testing Jerry Gao Ph.D. 7/2002 Object-Oriented Software Integration There are a number of proposed integration test strategies for object-oriented software. One of them is known as Class Test Order. What is class test order? - It is a class test sequence order for a class library or an OO program.
  • 16. Topic: Software Integration Testing Jerry Gao Ph.D. 7/2002 A Class Test Order for Object-Oriented Programs ButtonList Button Sensor TextButton Subject InstructorItr ButtonState Event Scene World Control ControlState CanvasRep Canvas MonoScene AG AS AS AS AS AS AS AG AS AS AS AS AS AG I I I I I I AS AS AS AG AS
  • 17. Topic: Software Integration Testing Jerry Gao Ph.D. 7/2002 A Class Test Order for Object-Oriented Programs ButtonList Button Sensor TextButton Subject InstructorItr ButtonState Event Scene World Control ControlState CanvasRep Canvas MonoScene AG AS AS AS AS AS AS AG AS AS AS AS AS AG I I I I I I AS AS AS AG AS
  • 18. Topic: Software Integration Testing Jerry Gao Ph.D. 7/2002 A Class Test Order for Object-Oriented Programs ButtonList Button Sensor TextButton Subject InstructorItr ButtonState Event Scene World Control ControlState CanvasRep Canvas MonoScene AG AS AS AS AS AS AS AG AS AS AS AS AS AG I I I I I I AS AS AS AG AS 1 4 I 3 2 4 1 2 3 5 4.1 4.2 3.1 3.2 3.3 3.4 1.1 1.2 5.1 5.2