CS487_04_05_10

CS487_04_05_10 - CS487 Software Engineering I OMAR ALDAWUD...

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

View Full Document Right Arrow Icon
Software Engineering I CS487 OMAR ALDAWUD 04/05/2010 2010 Illinois Institute of Technology © 2 Software Testing Testing is the process of exercising a program with the specific intent of finding errors prior to delivery to the end user.
Background image of page 1

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

View Full DocumentRight Arrow Icon
3 What Testing Shows errors errors requirements conformance requirements conformance performance performance an indication an indication of quality of quality 4 Who Tests the Software? developer independent tester Understands the system but, will test "gently" and, is driven by "delivery" Must learn about the system, but, will attempt to break it and, is driven by quality
Background image of page 2
5 Testing Strategy unit test integration test validation test system test 6 Testing Strategy ¡ We begin by ‘ testing-in-the-small’ and move toward testing-in-the-large’ ¡ For conventional software ¡ The module (component) is our initial focus ¡ Integration of modules follows ¡ For OO software ¡ our focus when “testing in the small” changes from an individual module (the conventional view) to an OO class that encompasses attributes and operations and implies communication and collaboration
Background image of page 3

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

View Full DocumentRight Arrow Icon
7 1. Unit Testing module to be tested test cases test cases results results software software engineer engineer 8 Unit Testing •interface •local data structures •boundary conditions •independent paths •error handling paths module to be tested test cases Focus on the internal processing logic and data structures within the boundaries of the component
Background image of page 4
9 Unit Test Environment Module Module stub stub stub stub driver driver interface interface local data structures local data structures boundary conditions boundary conditions independent paths independent paths error handling paths error handling paths RESULTS RESULTS test cases test cases Like main program Accept test case data Print relevant results Replace modules that are called by the module to be Tested Cohesive modules are easy to test!! 10 2. Integration Testing Strategies Options: 1. The “big bang” approach 2. An incremental construction strategy Top-down, Bottom-up,Sandwich,Smoke Build a program structure that represent the Design (architecture)
Background image of page 5

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

View Full DocumentRight Arrow Icon
11 Top Down Integration top module is tested with stubs stubs are replaced one at a time, "depth first“ Or “Breadth First’ as new modules are integrated, some subset of tests is re-run A B C D E F G 12 Bottom-Up Integration drivers are replaced one at a time, "depth first" worker modules are grouped into builds and integrated A B C D E F G cluster Begin testing with the atomic modules. stubs are not required Builds that perform a specific sub function
Background image of page 6
13 Sandwich Testing Top modules are tested with stubs Worker modules are grouped into builds and integrated A B C D E F G cluster 14 Smoke Testing ¡ A common approach for creating “daily builds ” for product software ¡ Smoke testing steps: 1. Software components that have been translated into code are integrated into a “build.” ¡ A build includes all data files, libraries, reusable modules, and
Background image of page 7

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

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

This document was uploaded on 04/23/2010.

Page1 / 28

CS487_04_05_10 - CS487 Software Engineering I OMAR ALDAWUD...

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

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