TTCN-3 Bibliography

WIKINDX Resources

H. Neukirchen and M. Bisanz, "Utilising Code Smells to Detect Quality Problems in TTCN-3 Test Suites," in Proc. Testing of Communication Systems (Testcom/Fates/Forte) 2007, ser. Lecture Notes in Computer Science, vol. 4581/2007, Tallinn (Estonia), June 26-29, 2007, pp. 228–243. 
Added by: Deleted user (02 Apr 2009 14:02:53 Europe/Berlin)   
Resource type: Proceedings Article
DOI: 10.1007/978-3-540-73066-8
BibTeX citation key: Neukirchen2007
View all bibliographic details
Categories: General
Creators: Bisanz, Neukirchen
Publisher: organized by Tallinn University of Technology (Tallinn (Estonia))
Collection: Testing of Communication Systems (Testcom/Fates/Forte) 2007
Views: 8/1144
Views index: %
Popularity index: 1.25%
   URLs   http://www.springerlink.com/content/b207674171t55l13
Abstract
Today, test suites of several ten thousand lines of code are specified using the Testing and Test Control Notation (TTCN-3). Experience shows that the resulting test suites suffer from quality problems with respect to internal quality aspects like usability, maintainability, or reusability. Therefore, a quality assessment of TTCN-3 test suites is desirable. A powerful approach to detect quality problems in source code is the identification of code smells. Code smells are patterns of inappropriate language usage that is error-prone or may lead to quality problems. This paper presents a quality assessment approach for TTCN-3 test suites which is based on TTCN-3 code smells: To this aim, various TTCN-3 code smells have been identified and collected in a catalogue; the detection of instances of TTCN-3 code smells in test suites has been automated by a tool. The applicability of this approach is demonstrated by providing results from the quality assessment of several standardised TTCN-3 test suites.
Added by: Deleted user  
wikindx 5.2.1 ©2017 | Total resources: 340 | Username: -- | Bibliography: WIKINDX Master Bibliography | Style: Institute of Electrical and Electronics Engineers (IEEE) | Database queries: 48 | DB execution: 0.02061 secs | Script execution: 0.02981 secs