html5-img
1 / 6

Overview

ECE 453 – CS 447 – SE 465 Software Testing & Quality Assurance Case Studies Instructor Paulo Alencar. Overview. Selecting an integration testing strategy Some OO integration testing strategies are compared.

tammy
Download Presentation

Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ECE 453 – CS 447 – SE 465 Software Testing & Quality AssuranceCase StudiesInstructorPaulo Alencar

  2. Overview • Selecting an integration testing strategy • Some OO integration testing strategies are compared. • Six real-world case studies of various complexities are considered (e.g., small telecommunications software, Swing Java Library) • Optimization problem – minimization of the number of stubs to the written (cost) and the number of steps needed to achieve the integration (duration) • Hahn, V., Akif, K., Traon, Y., Jezequel, J., Selecting an Efficient OO Integration Strategy: An Experimental Comparison of Actual Strategies, ECOOP’01, Lecture Notes in Computer Science, vol. 2072, pp. 381-401, 2001.

  3. Main Results • Four integration strategies and six real-world case studies • Integration strategies – Kung, Tai-Daniels, Genetic, Triskell • Case studies: • Telecommunication switching system (SMDS) • GNU Eiffel compiler (partial) • Interviews graphic library • Pylon Eiffel library (e.g., data structures) • Base classes of Java 2 Platform, v. 1.3 • Package Swing – Java 2 Platform, v. 1.3

  4. Main Results Test Dependence Graph (TDG) is obtained from UML class diagrams:

  5. Main Results Stub number for each case study:

  6. Main Results Step number for each case study:

More Related