ch11lect2_UD - Using UML, Patterns, and Java...

Info iconThis preview shows pages 1–10. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 11, Testing, Part 2: Integration and System Testing Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 2 Overview Integration testing Big bang Bottom up Top down Sandwich Continuous System testing Functional Performance Acceptance testing Summary Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 3 Integration Testing The entire system is viewed as a collection of subsystems (sets of classes) determined during the system and object design Goal: Test all interfaces between subsystems and the interaction of subsystems The Integration testing strategy determines the order in which the subsystems are selected for testing and integration. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 4 Why do we do integration testing? Unit tests only test the unit in isolation Many failures result from faults in the interaction of subsystems Often many Off-the-shelf components are used that cannot be unit tested Without integration testing the system test will be very time consuming Failures that are not discovered in integration testing will be discovered after the system is deployed and can be very expensive. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 5 Stubs and drivers Driver: A component, that calls the TestedUnit Controls the test cases Stub: A component, the TestedUnit depends on Partial implementation Returns fake values. Driver Tested Unit Stub Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 6 Example: A 3-Layer-Design Layer I Layer II Layer III Spread SheetView A Calculator C BinaryFile Storage E XMLFile Storage F Currency DataBase G Currency Converter D Data Model B A C E F G D B Spread SheetView BinaryFile Storage Entity Model A E F Currency DataBase G Currency Converter D B Calculator C XMLFile Storage (Spreadsheet) Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 7 A C E F G D B Big-Bang Approach Test A Test B Test G Test F Test E Test C Test D Test A, B, C, D, E, F, G Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 8 Bottom-up Testing Strategy The subsystems in the lowest layer of the call hierarchy are tested individually Then the next subsystems are tested that call the previously tested subsystems This is repeated until all subsystems are included Drivers are needed. Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java...
View Full Document

This note was uploaded on 02/19/2011 for the course CS 319 taught by Professor Ugurdogrusoz during the Fall '10 term at Bilkent University.

Page1 / 31

ch11lect2_UD - Using UML, Patterns, and Java...

This preview shows document pages 1 - 10. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online