Chapter 11, Testing, Part 2: Integration and System Testing

Slides:



Advertisements
Similar presentations
2017/3/25 Test Case Upgrade from “Test Case-Training Material v1.4.ppt” of Testing basics Authors: NganVK Version: 1.4 Last Update: Dec-2005.
Advertisements

Testing Relational Database
By Rick Clements Software Testing 101 By Rick Clements
Making the System Operational
Software Engineering COMP 201
Week 2 The Object-Oriented Approach to Requirements
Configuration management
Software Testing Strategies
Software testing.
Defect testing Objectives
Testing Workflow Purpose
Test process essentials Riitta Viitamäki,
Chapter 6 Data Design.
การทดสอบโปรแกรม กระบวนการในการทดสอบ
Component-Based Software Engineering Main issues: assemble systems out of (reusable) components compatibility of components.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software processes 2.
Lecture 8: Testing, Verification and Validation
Chapter 10 Software Testing
Executional Architecture
Chapter 10: The Traditional Approach to Design
Systems Analysis and Design in a Changing World, Fifth Edition
Chapter 15 System Implementation
Software Engineering I: Integration and System Testing
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.
CMSC 345, Version 11/07 SD Vick from S. Mitchell Software Testing.
Integration testing Satish Mishra
Illinois Institute of Technology
Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 1 Software Engineering October 31, 2001 Testing.
Chapter 11, Testing.
Outline Types of errors Component Testing Testing Strategy
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 11: Integration- and System Testing.
Software System Integration
System/Software Testing
Testing Chapter 11. Dealing with Errors Verification: –Makes assumptions –Doesn’t always deal with real environment Testing (this lecture) –Testing is.
Testing. Outline Terminology Types of errors Dealing with errors Quality assurance vs Testing Component Testing Unit testing Integration testing Testing.
ECE 355: Software Engineering
Conquering Complex and Changing Systems Object-Oriented Software Engineering Chapter 9, Testing.
Overview Integration Testing Decomposition Based Integration
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.
Conquering Complex and Changing Systems Object-Oriented Software Engineering Chapter 11, Testing.
Testing Basics of Testing Presented by: Vijay.C.G – Glister Tech.
TESTING LEVELS Unit Testing Integration Testing System Testing Acceptance Testing.
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.
Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 1 Terminology  Reliability: The measure of.
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 11, Testing, Part 2: Integration and System Testing.
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)
Conquering Complex and Changing Systems Object-Oriented Software Engineering Chapter 9, Testing.
Software testing techniques Software testing techniques Sandwich strategy Presentation on the seminar Kaunas University of Technology.
1 Phase Testing. Janice Regan, For each group of units Overview of Implementation phase Create Class Skeletons Define Implementation Plan (+ determine.
Conquering Complex and Changing Systems Object-Oriented Software Engineering Chapter 9, Testing.
What is this?. Erroneous State (“Error”) Algorithmic Fault.
Lecturer: Eng. Mohamed Adam Isak PH.D Researcher in CS M.Sc. and B.Sc. of Information Technology Engineering, Lecturer in University of Somalia and Mogadishu.
Chapter 11, Testing, Part 2: Integration and System Testing
Software Testing Strategies for building test group
Chapter-5 (Testing Strategy)
Integration Testing.
Chapter 11, Testing, Part 2: Integration and System Testing
Chapter 11, Testing, Part 2: Integration and System Testing
Chapter 11, Testing, Part 2: Integration and System Testing
Chapter 11, Testing.
Software System Integration
Higher-Level Testing and Integration Testing
Chapter 9, Testing.
test the system against user & system requirements
Chapter 11: Integration- and System Testing
Chapter 11: Integration and System Testing
CS410 – Software Engineering Lecture #11: Testing II
Presentation transcript:

Chapter 11, Testing, Part 2: Integration and System Testing

Overview Integration testing System testing Acceptance testing Summary Big bang Bottom up Top down Sandwich Continuous System testing Functional Performance Acceptance testing Summary

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. For the selection of the subsystems we use the system decomposition from System Design Kürzen? Tonspur: Übergang Unit Test zu Integration

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.

Stubs and drivers Driver: Stub: 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

Example: A 3-Layer-Design (Spreadsheet) Spread SheetView BinaryFile Storage Entity Model A E F Currency DataBase G Currency Converter D B Calculator C XMLFile Storage A Spread SheetView A Layer I B C D B Data Model Calculator C D Currency Converter Layer II For the following integration testing strategies, we use this call hierarchy of an example design consisting of 3 layers and 7 subsystems. E F G E BinaryFile Storage F XMLFile Storage Currency DataBase G Layer III

Big-Bang Approach Test A Test B Test C Test A, B, C, D, Test D E, F, G This unit tests each of the subsystems, and then does one gigantic integration test, in which all the subsystems are immediately tested together. Don‘t try this!! Why: The interfaces of each of the subsystems have not been tested yet. Test D Test E Test F Test G

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.

Bottom-up Integration C E F G D B A B C D Test E E F G Test B, E, F This unit tests each of the subsystems, and then does one gigantic integration test, in which all the subsystems are immediately tested together. Don‘t try this!! Why: The interfaces of each of the subsystems have not been tested yet. Test F Test A, B, C, D, E, F, G Test C Test G Test D,G

Pros and Cons of Bottom-Up Integration Testing Tests the most important subsystem (user interface) last Drivers needed Pro No stubs needed Useful for integration testing of the following systems Object-oriented systems Real-time systems Systems with strict performance requirements.

Top-down Testing Strategy Test the top layer or the controlling subsystem first Then combine all the subsystems that are called by the tested subsystems and test the resulting collection of subsystems Do this until all subsystems are incorporated into the test Stubs are needed to do the testing.

Top-down Integration Test A, B, C, D, E, F, G Test A Test A, B, C, D This unit tests each of the subsystems, and then does one gigantic integration test, in which all the subsystems are immediately tested together. Don‘t try this!! Why: The interfaces of each of the subsystems have not been tested yet. Test A, B, C, D, E, F, G Test A Test A, B, C, D Layer I Layer I + II All Layers

Pros and Cons of Top-down Integration Testing Test cases can be defined in terms of the functionality of the system (functional requirements) No drivers needed Cons Writing stubs is difficult: Stubs must allow all possible conditions to be tested. Large number of stubs may be required, especially if the lowest level of the system contains many methods. Some interfaces are not tested separately.

Sandwich Testing Strategy Combines top-down strategy with bottom-up strategy The system is viewed as having three layers A target layer in the middle A layer above the target A layer below the target Testing converges at the target layer. How do you select the target layer if there are more than 3 layers? Heuristic: Try to minimize the number of stubs and drivers

Sandwich Testing Strategy B C D Test A E F G Test A,B,C, D Test E Anpassen Test A, B, C, D, E, F, G Test B, E, F Test F Test D,G Test G

Pros and Cons of Sandwich Testing Top and Bottom Layer Tests can be done in parallel Problem: Does not test the individual subsystems and their interfaces thoroughly before integration Solution: Modified sandwich testing strategy

Modified Sandwich Testing Strategy Test in parallel: Middle layer with drivers and stubs Top layer with stubs Bottom layer with drivers Top layer accessing middle layer (top layer replaces drivers) Bottom accessed by middle layer (bottom layer replaces stubs).

Modified Sandwich Testing B C D Test A Test A,C Test C E F G Test B Test A, B, C, D, E, F, G Test E Test B, E, F Test F Test D Test D,G Test G

Continuous Testing Continuous build: Requires integrated tool support: Build from day one Test from day one Integrate from day one System is always runnable Requires integrated tool support: Continuous build server Automated tests with high coverage Tool supported refactoring Software configuration management Issue tracking.

Continuous Testing Strategy Spread SheetView Layer I B C D Data Model Calculator Currency Converter Layer II SCRUM Scheibe vom Brot XXXX E F G BinaryFile Storage XMLFile Storage Currency DataBase Layer III + Cells + Addition Sheet View + File Storage

Steps in Integration Testing 1. Based on the integration strategy, select a component to be tested. Unit test all the classes in the component. 2. Put selected component together; do any preliminary fix-up necessary to make the integration test operational (drivers, stubs) 3. Test functional requirements: Define test cases that exercise all uses cases with the selected component 4. Test subsystem decomposition: Define test cases that exercise all dependencies 5. Test non-functional requirements: Execute performance tests 6. Keep records of the test cases and testing activities. 7. Repeat steps 1 to 7 until the full system is tested. The primary goal of integration testing is to identify failures with the (current) component configuration. .

System Testing Functional Testing Performance Testing Validates functional requirements Performance Testing Validates non-functional requirements Acceptance Testing Validates clients expectations When we are system testing, we are testing all subsystems together. The requirements have a large impact on the quality of system testing: The more explicit the requirements, the easier they are to test. We distinguish the following types of system testing Let’s walk through each of these system testing types

Functional Testing Goal: Test functionality of system Test cases are designed from the requirements analysis document (better: user manual) and centered around requirements and key functions (use cases) The system is treated as black box Unit test cases can be reused, but new test cases have to be developed as well. Essentially the same as black box testing Unit test cases can be reused, but in end user oriented systems new test cases have to be developed as well. .

Performance Testing Goal: Try to violate non-functional requirements Test how the system behaves when overloaded. Can bottlenecks be identified? (First candidates for redesign in the next iteration) Try unusual orders of execution Call a receive() before send() Check the system’s response to large volumes of data If the system is supposed to handle 1000 items, try it with 1001 items. What is the amount of time spent in different use cases? Are typical cases executed in a timely fashion? Push the (integrated) system to its limits.

Types of Performance Testing Stress Testing Stress limits of system Volume testing Test what happens if large amounts of data are handled Configuration testing Test the various software and hardware configurations Compatibility test Test backward compatibility with existing systems Timing testing Evaluate response times and time to perform a function Security testing Try to violate security requirements Environmental test Test tolerances for heat, humidity, motion Quality testing Test reliability, maintain- ability & availability Recovery testing Test system’s response to presence of errors or loss of data Human factors testing Test with end users. Stress Testing Stress limits of system (maximum # of users, peak demands, extended operation) Volume testing Test what happens if large amounts of data are handled Configuration testing Test the various software and hardware configurations Compatibility test Test backward compatibility with existing systems Security testing Try to violate security requirements

Acceptance Testing Goal: Demonstrate system is ready for operational use Choice of tests is made by client Many tests can be taken from integration testing Acceptance test is performed by the client, not by the developer. Alpha test: Client uses the software at the developer’s environment. Software used in a controlled setting, with the developer always ready to fix bugs. Beta test: Conducted at client’s environment (developer is not present) Software gets a realistic workout in target environ- ment Majority of all bugs in software is typically found by the client after the system is in use, not by the developers or testers. Therefore two kinds of additional tests: Alpha test Beta test: … One disadvantage: Potential customers might get discouraged

Testing has many activities Establish the test objectives Design the test cases Write the test cases Test the test cases Execute the tests Evaluate the test results Change the system Do regression testing

Test Team Test Team Professional Tester Analyst System Designer User too familiar Programmer with code Analyst System Designer Test User Team Configuration Management Specialist

The 4 Testing Steps 1. Select what has to be tested Analysis: Completeness of requirements Design: Cohesion Implementation: Source code 2. Decide how the testing is done Review or code inspection Proofs (Design by Contract) Black-box, white box, Select integration testing strategy (big bang, bottom up, top down, sandwich) 3. Develop test cases A test case is a set of test data or situations that will be used to exercise the unit (class, subsystem, system) being tested or about the attribute being measured 4. Create the test oracle An oracle contains the predicted results for a set of test cases The test oracle has to be written down before the actual testing takes place.

Guidance for Test Case Selection Use analysis knowledge about functional requirements (black-box testing): Use cases Expected input data Invalid input data Use design knowledge about system structure, algorithms, data structures (white-box testing): Control structures Test branches, loops, ... Data structures Test records fields, arrays, ... Use implementation knowledge about algorithms and datastructures: Force a division by zero If the upper bound of an array is 10, then use 11 as index. Rauslassen?

Summary Testing is still a black art, but many rules and heuristics are available Testing consists of Unit testing Integration testing System testing Acceptance testing Design patterns can be used for integration testing Testing has its own lifecycle