Automated Maintainability of TTCN-3 Test Suites Based on Guideline Checking

Authors:
George Din;Diana Vega;Ina Schieferdecker
Affiliations:
FOKUS Fraunhofer Institut, Berlin, Germany;Technical University of Berlin, Berlin, Germany;Technical University of Berlin, Berlin, Germany
Venue:
SEUS '08 Proceedings of the 6th IFIP WG 10.2 international workshop on Software Technologies for Embedded and Ubiquitous Systems
Year:
2008

Citing 4
Cited 1

The C++ programming language

The C++ programming language
Refactoring: improving the design of existing code

Refactoring: improving the design of existing code
Java Look & Feel Design Guidelines

Java Look & Feel Design Guidelines
Refactoring and metrics for TTCN-3 test suites

SAM'06 Proceedings of the 5th international conference on System Analysis and Modeling: language Profiles

Analyzing Response Inconsistencies in Test Suites

TESTCOM '09/FATES '09 Proceedings of the 21st IFIP WG 6.1 International Conference on Testing of Software and Communication Systems and 9th International FATES Workshop

Quantified Score

Hi-index	0.00

Visualization

Abstract

Similar to software development, the test development must be accompanied with a set of rules specifying how to write tests. They are grouped together into a document called guideline. Guidelines are especially necessary for large test specifications involving many developers and have the goal to reduce the effort of the overall development. So far, no universal guidelines for the TTCN-3 language [1] have been defined. Instead, each company or team defines and follows own development rules for test structuring and development. This paper deals with the problem of how to automate the validation whether a TTCN-3 test specification complies or not with an established guideline, i.e. guideline checking. The results of the validation process are a list of non-consistencies. A follow up step is the refactoring which automatically proposes and applies changes to improve the test suite compliance level, and thus its quality.