Sedit

SeDiTeC - Testing Based on Sequence Diagrams

Falk Fraikin, Thomas Leonhardt Software Engineering Research Group Darmstadt University of Technology {fraikin|leonhardt}@informatik.tu-darmstadt.de Abstract

In this paper we present a concept for automated testing of object-oriented applications and a tool called SeDiTeC that implements these concepts for Java applications. SeDiTeC uses UML sequence diagrams, that are complemented by test case data sets consisting of parameters and return values for the method calls, as test specification and therefore can easily be integrated into the development process as soon as the design phase starts. SeDiTeC supports specification of several test case data sets for each sequence diagram as well as to combine several sequence diagrams to so-called combined sequence diagrams thus reducing the number of diagrams needed. For classes and their methods whose behavior is specified in sequence diagrams and the corresponding test case data sets SeDiTeC can automatically generate test stubs thus enabling testing right from the beginning of the implementation phase. Validation is not restricted to comparing the test case data sets with the observed data, but can also include validation of pre- and postconditions. also Test. In the Analysis & Design discipline the use cases are refined by use case realizations. The essential part of a use case realization always consists of one or more interaction diagrams, i.e. sequence and/or collaboration diagrams. Those diagrams are then used to analyze which objects are needed to implement the functionality of the use case, which methods the objects need to expose, and how the objects need to interact. A detailed description how to create and use sequence diagrams as use case realizations is given in [17]. When it comes to testing (covered by the Test discipline) the instructions given by the RUP are on a quite abstract level. Relevant in this context is the remark in [11] that typically black box...