A framework for component deployment testing

Component-based development is the emerging paradigm in software production, though several challenges still slow down its full taking up. In particular, the "component trust problem" refers to how adequate guarantees and documentation about a component's behaviour can be transferred from the component developer to its potential users. The capability to test a component when deployed within the target application environment can help establish the compliance of a candidate component to the customer's expectations and certainly contributes to "increase trust". To this purpose, we propose the CDT framework for Component Deployment Testing. CDT provides the customer with both a technique to early specify a deployment test suite and an environment for running and reusing the specified tests on any component implementation. The framework can also be used to deliver the component developer's test suite and to later re-execute it. The central feature of CDT is the complete decoupling between the specification of the tests and the component implementation.

[1]  Clemens A. Szyperski,et al.  Component software - beyond object-oriented programming , 2002 .

[2]  Yingxu Wang,et al.  A method for built-in tests in component-based software maintenance , 1999, Proceedings of the Third European Conference on Software Maintenance and Reengineering (Cat. No. PR00090).

[3]  Eda Marchetti,et al.  Integration of "Components" to Test Software Components , 2003, TACoS.

[4]  John Daniels,et al.  UML Components: A Simple Process for Specifying Component-Based Software , 2000 .

[5]  Alessandro Orso,et al.  Component Metadata for Software Engineering Tasks , 2000, EDO.

[6]  Jeffrey M. Voas.  Developing a Usage-Based Software Certification Process , 2000, Computer.

[7]  Elaine J. Weyuker,et al.  Testing Component-Based Software: A Cautionary Tale , 1998, IEEE Softw..

[8]  Bertrand Meyer,et al.  Applying 'design by contract' , 1992, Computer.

[9]  G. Bundell,et al.  Software Component Certification , 2001, Computer.

[10]  Robert V. Binder,et al.  Testing Object-Oriented Systems: Models, Patterns, and Tools , 1999 .

[11]  Andrea Polini,et al.  Re-thinking the Development Process of Component-based Software , 2002 .

[12]  Jerry Zeyu Gao,et al.  On Building Testable Software Components , 2002, ICCBSS.

[13]  VoasJeffrey.  Developing a Usage-Based Software Certification Process , 2000 .

[14]  Monica S. Lam,et al.  Automatic extraction of object-oriented component interfaces , 2002, ISSTA '02.

[15]  Eda Marchetti,et al.  The Cow_Suite Approach to Planning and Deriving Test Suites in UML Projects , 2002, UML.

[16]  David S. Rosenblum.  Adequate Testing of Component-Based Software , 1997 .

[17]  Thorsten von Eicken,et al.  技術解説 IEEE Computer , 1999 .

[18]  Andrea Polini,et al.  WCT: A Wrapper for Component Testing , 2002, FIDJI.

[19]  Hong Sun,et al.  Investigating the use of analysis contracts to support fault isolation in object oriented code , 2002, ISSTA '02.

[20]  Jeffrey M. Voas,et al.  Certifying Off-the-Shelf Software Components , 1998, Computer.

[21]  Clemens Szyperski,et al.  Component software , 1997 .

[22]  G. G. Stokes.  "J." , 1890, The New Yale Book of Quotations.

[23]  Ralph Johnson,et al.  design patterns elements of reusable object oriented software , 2019 .

[24]  David S. Rosenblum,et al.  WREN---an environment for component-based development , 2001, ESEC/FSE-9.

[25]  Daniel G. Bobrow,et al.  Book review: The Art of the MetaObject Protocol By Gregor Kiczales, Jim des Rivieres, Daniel G. and Bobrow(MIT Press, 1991) , 1991, SGAR.

[26]  Alexander L. Wolf,et al.  Annotating Components to Support Component-Based Static Analyses of Software Systems , 1999 .