loading...
Testing Patterns
Columbia, MD, USA March 06-March 08
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/SEW.2007.10831st IEEE Software Engineering Worksh ...
 This Article 
 
PDF
HTML
 
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
continue to find new areas of application. In previous work, we presented a contract formalism for specifying patterns precisely, and showed how the use of the for- malism can amplify the benefits of patterns. In this pa- per, our goal is to enable practitioners to test whether their systems, as implemented, meet the requirements, as specified in the pattern contracts, corresponding to the correct usage of the patterns underlying the systems' de- signs. In our testing approach, corresponding to each de- sign pattern, there is a set of what we call pattern test case templates (PTCTs). A PTCT codifies a reusable test case structure designed to identify defects associated with ap- plications of the particular pattern. The test assertions in the PTCT are based on the requirements specified in the appropriate pattern contract. Next we present a pro- cess using which, given any system designed using the pattern, the system tester can generate a test suite from the PTCTs for that pattern that can be used to test the system for bugs in the implementation of the particular pattern. The process allows the system tester to tailor the test suite the needs of the individual system by specifying a set of specialization rules that are designed to reflect the structure and the scenarios in which the defects codi- fied in the PTCTs are likely to manifest themselves in the particular system.
Citation:
Neelam Soundarajan, Jason O. Hallstrom, Adem Delibas, Guoqiang Shu, "Testing Patterns," sew, pp.109-120, 31st IEEE Software Engineering Workshop (SEW 2007), 2007
Usage of this product signifies your acceptance of the Terms of Use.