Integration Testing.

Slides:



Advertisements
Similar presentations
1 Integration Testing CS 4311 I. Burnstein. Practical Software Testing, Springer-Verlag, 2003.
Advertisements

Control Flow Analysis. Construct representations for the structure of flow-of-control of programs Control flow graphs represent the structure of flow-of-control.
The SATM system Winter SATM SATM: Simple Automatic Teller Machine. Will work with this example during the Integration and system testing part. Build.
Software Integration Testing Speaker: Jerry Gao Ph.D. San Jose State University URL:
CMSC 345, Version 11/07 SD Vick from S. Mitchell Software Testing.
Integration testing Satish Mishra
Integration and System Testing CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 29, 2007.
Integration Testing Presented By Nesreen Ahmad. *Main Points:-  Definition Of Integration Testing.  Procedure Of Integration Testing.  Integration.
Illinois Institute of Technology
CS 425/625 Software Engineering Software Testing
INTEGRATION TESTING ● After or during Unit Testing ● Putting modules together in a controlled way to incrementally build up the final system. ● Start with.
Program unit A Program unit B Program unit T Function 1 Function 2 Function Component 1 Whole System (e.g. regression testing) Component 3....
Software Testing & Strategies
Issues on Software Testing for Safety-Critical Real-Time Automation Systems Shahdat Hossain Troy Mockenhaupt.
Software System Integration
ECE 355: Software Engineering
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.1.
Chapter 7 Unit Testing & Integration Testing Software Testing By Wararat Songpan(Rungworawut),PH.D. Department of Computer Science, Faculty of.
Overview Integration Testing Decomposition Based Integration
Different Levels of Testing
1 ECE 453 – CS 447 – SE 465 Software Testing & Quality Assurance Instructor Kostas Kontogiannis.
Prof. Mohamed Batouche Software Testing.
Final Review  Different tests  Boundary Value Testing  Equivalence Class Testing  Decision Table Based Testing  Path Testing  Data Flow & P-Slice.
INT-Evry (Masters IT– Soft Eng)IntegrationTesting.1 (OO) Integration Testing What: Integration testing is a phase of software testing in which.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 13a: Software Testing Strategies Software Engineering: A Practitioner’s Approach, 6/e Chapter.
Testing Basics of Testing Presented by: Vijay.C.G – Glister Tech.
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.1.
Chapter 14 System Testing.
Software Testing. 2 CMSC 345, Version 4/12 Topics The testing process  unit testing  integration and system testing  acceptance testing Test case planning.
Chapter 13 Integration Testing. The Mars Climate Orbiter Mission mission failed in September 1999 completed successful flight: 416,000,000 miles (
Principles of Engineering System Design Dr T Asokan
System Testing Beyond unit testing. 2 System Testing Of the three levels of testing, system level testing is closest to everyday experience We evaluate.
1 Integration Testing CS 4311 I. Burnstein. Practical Software Testing, Springer-Verlag, 2003.
CSC 480 Software Engineering Test Planning. Test Cases and Test Plans A test case is an explicit set of instructions designed to detect a particular class.
Integration testing Integrate two or more module.i.e. communicate between the modules. Follow a white box testing (Testing the code)
Integration Testing Beyond unit testing. 2 Testing in the V-Model Requirements Detailed Design Module implementation Unit test Integration test System.
Dillon: CSE470: SYSTEM INTEGRATION 1 Build Plan l Development or integration strategies l Decide the order in which components of the system will be developed.
1 Software Testing & Quality Assurance Lecture 15 Created by: Paulo Alencar Modified by: Frank Xu.
Software Engineering By Germaine Cheung Hong Kong Computer Institute Lecture 7.
Software testing techniques Software testing techniques Sandwich strategy Presentation on the seminar Kaunas University of Technology.
Lec 10 Integration Testing- 1 CSCE 747 Fall 2013 CSCE 747 Software Testing and Quality Assurance Lecture 10 – Integration Testing 9/30/
Software Testing Strategies for building test group
Group mambers: Maira Naseer (BCS ).
Trees Chapter 15.
Integration Testing.
Rekayasa Perangkat Lunak Part-13
Integration Testing This is the step after the individual pieces of code or modules (programs) are tested. A set of programs do not exist in vacuum. They.
Marius Skudžinskas IFM-02
Software Engineering: A Practitioner’s Approach, 6/e Chapter 13 Software Testing Strategies copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Chapter 18 Software Testing Strategies
Levels Of Testing and Special Tests
Definition of Integration Testing
Higher-Level Testing and Integration Testing
Chapter 13 Integration Testing
Problem Solving: Structure Charts
Different Levels of Testing
Chapter 10 – Software Testing
Integration Testing CS 4311
Test Case Test case Describes an input Description and an expected output Description. Test case ID Section 1: Before execution Section 2: After execution.
Chapter 13 Integration Testing.
Software Testing “If you can’t test it, you can’t design it”
Software System Integration
Chapter 11: Integration- and System Testing
Chapter 11: Integration and System Testing
CS410 – Software Engineering Lecture #11: Testing II
Integration Testing.
Recursive Relationship
Software Testing Strategies
Cs212: Data Structures Lecture 7: Tree_Part1
Presentation transcript:

Integration Testing

After individual components have passed unit testing, they are merged together to form subsystems and ultimately one complete system. Integration testing is the process of exercising this “hierarchically accumulating” system. Integration test looks at the: “structural” composition (or decomposition) and test the related code (modules / programs). The “call” relationship neighborhood and test the “neighborhood” The path created by the relationship and test the “path”

The order in which the subsystems are selected for testing and integration determines the testing strategy. There are 4 major types of integration test for Structural Decomposition Based test: Big bang integration (Nonincremental) Bottom up integration Top down integration Sandwich testing

Bottom-up integration In bottom-up integration, we start with the leaves of the decomposition tree stubs are replaced by driver modules that emulate units at the next level up in the tree ControlDoor and DispenseCash

Top-down integration Top-down integration begins with the main program (the root of the tree). Any lower level unit that is called by the main program appears as a “stub”, where stubs are pieces of throw-away code that emulate a called unit. If we performed top-down integration testing for the SATM system, the first step - to develop stubs for all the units called by the main program: WatchCardSlot, Control Card Roller, Screen Driver, Validate Card, Validate PIN, Manage Transaction, and New Transaction Request. Generally, testers have to develop the stubs, and some imagination is required.

Sandwich integration Sandwich integration is a combination of top-down and bottom-up integration. There will be less stub and driver development effort

Pair-wise Integration The idea behind pair-wise integration is to eliminate the stub/driver development effort. Rather than develop stubs and/or drivers, why not use the actual code? We restrict a session to just a pair of units in the call graph. The end result is that we have one integration test session for each edge in the call graph

Neighborhood Integration Neighborhood of a node in a graph to be the set of nodes that are one edge away from the given node. In a directed graph, this means all the immediate predecessor nodes and all the immediate successor nodes (notice that these correspond to the set of stubs and drivers of the node). The eleven neighborhoods for the SATM example