Integration Testing Presented By Nesreen Ahmad. *Main Points:-  Definition Of Integration Testing.  Procedure Of Integration Testing.  Integration.

Slides:



Advertisements
Similar presentations
Chapter 11, Testing, Part 2: Integration and System Testing
Advertisements

Chapter 13 Review Questions
1 Integration Testing CS 4311 I. Burnstein. Practical Software Testing, Springer-Verlag, 2003.
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 11: Integration- and System Testing.
Software Integration Testing Speaker: Jerry Gao Ph.D. San Jose State University URL:
Integration testing Satish Mishra
Integration and System Testing CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 29, 2007.
Strategic Approach to Testing
PVK-HT061 Contents Introduction Requirements Engineering Project Management Software Design Detailed Design and Coding Quality Assurance Maintenance.
Illinois Institute of Technology
INTEGRATION TESTING ● After or during Unit Testing ● Putting modules together in a controlled way to incrementally build up the final system. ● Start with.
Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 1 Software Engineering October 31, 2001 Testing.
Outline Types of errors Component Testing Testing Strategy
Software Testing Name: Madam Currie Course: Swen5431 Semester: Summer 2K.
Program unit A Program unit B Program unit T Function 1 Function 2 Function Component 1 Whole System (e.g. regression testing) Component 3....
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 11: Integration- and System Testing.
Software Testing & Strategies
Bottom-Up Integration Testing After unit testing of individual components the components are combined together into a system. Bottom-Up Integration: each.
Software System Integration
Testing Chapter 11. Dealing with Errors Verification: –Makes assumptions –Doesn’t always deal with real environment Testing (this lecture) –Testing is.
ECE 355: Software Engineering
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 20 Slide 1 Integration testing l Tests complete systems or subsystems composed of integrated.
Overview Integration Testing Decomposition Based Integration
Using UML, Patterns, and Java Object-Oriented Software Engineering Art for Chapter 11, Testing.
Different Levels of Testing
Object-Oriented Software Engineering, Ch. 9
INT-Evry (Masters IT– Soft Eng)IntegrationTesting.1 (OO) Integration Testing What: Integration testing is a phase of software testing in which.
Architectural Design To explain the advantages and disadvantages of different distributed systems architectures To discuss client-server and distributed.
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.
Architectural Design lecture 10. Topics covered Architectural design decisions System organisation Control styles Reference architectures.
Software Testing Reference: Software Engineering, Ian Sommerville, 6 th edition, Chapter 20.
 Repository Model  Client-Server Model  Layered Model  Modular decomposition styles  Object Models  Function Oriented Pipelining  Control Styles.
1 Systems V & V, Quality and Standards Dr Sita Ramakrishnan School CSSE Monash University.
Intro to S/W Engg Software Testing. Terminology  Reliability: The measure of success with which the observed behavior of a system confirms to some specification.
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 11, Testing, Part 2: Integration and System Testing.
1 Integration Testing CS 4311 I. Burnstein. Practical Software Testing, Springer-Verlag, 2003.
Chapter 7 Implementation. Implementation Approaches F Big bang –Code entire system and test in an unstructured manner F Top-down –Start by implementing.
Big Bang Approach No testing of Individual Units Advantages Cost can be saved No stubs/Drivers Very fast Disadvantages Hard to debug Location of defect.
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.
CS451 Software Implementation and Integration Yugi Lee STB #555 (816) Note: This lecture was designed.
What is a level of test?  Defined by a given Environment  Environment is a collection of people, hard ware, software, interfaces, data etc.
1 Object-Oriented Analysis and Design with the Unified Process Figure 13-1 Implementation discipline activities.
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 testing techniques Software testing techniques Sandwich strategy Presentation on the seminar Kaunas University of Technology.
Integration testing After different modules of a system have been coded and unit tested: –modules are integrated in steps according to an integration plan.
Software Testing Reference: Software Engineering, Ian Sommerville, 6 th edition, Chapter 20.
Chapter 8 Testing the Programs. Integration Testing  Combine individual comp., into a working s/m.  Test strategy gives why & how comp., are combined.
Software Engineering Zhang Shuang
Handouts Software Testing and Quality Assurance Theory and Practice Chapter 7 System Integration Testing
Chapter 8 Testing the Programs 8.1 Software Faults and Failures 1. Introduction  faults: A: definition: the problem caused by error B: cause: X: the software.
Chapter 11, Testing, Part 2: Integration and System Testing
Integration Testing.
Rekayasa Perangkat Lunak Part-13
Marius Skudžinskas IFM-02
Chapter 11, Testing, Part 2: Integration and System Testing
Software System Integration
Higher-Level Testing and Integration Testing
Princess Nourah bint Abdulrahman University
Different Levels of Testing
Integration Testing CS 4311
Integration Testing.
Chapter 11: Integration- and System Testing
TYPES OF TESTING.
Chapter 11: Integration and System Testing
CS410 – Software Engineering Lecture #11: Testing II
Information system analysis and design
Presentation transcript:

Integration Testing Presented By Nesreen Ahmad

*Main Points:-  Definition Of Integration Testing.  Procedure Of Integration Testing.  Integration Testing Strategies.

Definition Of Integrated Testing  Detects faults that have not been detected during unit testing by focusing on small groups of components.

Procedure Of Integration Testing  Two or more components are integrated and tested, and when no new faults are revealed (discovered), additional components are added to the group.  This procedure allows the testing of increasingly more complex parts of the system while keeping the location of potential faults relatively small.

Integration Testing Strategies  Big Bang Testing.  Bottom-Up Testing.  Top-Down Testing.  Sandwich Testing.

Layer I Database (E) Layer III User Interface (A) Layer I I Billing (B)Event Service (C)Learning (D) Network (F)Neural Network (G)

First: Big Bang Testing  This strategy assumes that all components are first tested individually and then tested together as single system.  Advantage: That no additionally test stubs or drivers are needed.  Disadvantage: 1- It is expensive. 2- It is difficult to pinpoint the specific components (or combination of components).

Second: Bottom-Up Testing  Strategy first tests each component of the bottom layer individually, and then integrates them with components of the next layer up.

User Interface (A) Learning (D) Event Service (C) Billing (B) Network (F) Neural Network (G) Database (E) - Bottom-Up test strategy -

 Advantage: Interface faults can be more easily found.  Disadvantage: Faults found in the top layer may often lead to change in the subsystem decomposition or in the subsystem interfaces of lower layers.

Third: Top-Down Testing  Tests the components of the top layer first, and then integrates the components of the next layer down. When all components of the new layer have been tested together, the next layer is selected.

User Interface (A) Learning (D) Event Service (C) Billing (B) Network (F) Neural Network (G) Database (E) - Top-Down test strategy -

 Advantage: It starts with user interface components.  Disadvantage: 1-The development of test stub is time-consuming and prone error. 2- A large number of stubs is usually required for testing nontrivial systems.

Fourth: Sandwich Testing  Combines the top-down and bottom-up strategies, attempting to make use of the best of both.  There are Three Layers:- 1-Target Layer (“the meat”). 2-The Layer above the target layer. 3-The Layer below the target layer.

Test A Test A,B,C,D Test A, D Test A, C Test A, B Test G Test A,B,C,D,E,F,G Test B,E,F Test D,G Test F Test E - Sandwich Testing Strategy - Top Layer Bottom Layer

Test A Test A,B,C,D Test A, D Test A, C Test A, B Test G Test A,B,C,D,E,F,G Test B,E,F Test D,G Test F Test E - Modified Sandwich Testing Strategy - Test B Test C Test D Top Layer Bottom Layer Target Layer

 The advantage of modified sandwich testing: Many testing activities can be performed in parallel.  The disadvantage of modified sandwich testing: Is needed for additional test stubs and drivers.