A UML approach to the generation of test sequences for Java-based concurrent systems

Automatic test case generation from UML communication diagrams

“…In our approach, we have not considered specific issues like polymorphic interactions or test generation for concurrent systems as discussed by Kim et al [20].…”

“…Many of the related works reported in the literature attempt to use UML state chart diagrams for testing [26,19,21,15,31,8,20]. State chart diagrams are appropriate in the context of class level testing as these do not represent message sequences and communications.…”

“…The interactions between components are then specified by annotating the state diagrams, and the resulting global FSM that corresponds to the integrated system behavior is used to generate the tests. Kim et al [20] describe a way to generate test sequences starting with a UML state machine specification that captures the underlying functionality of some given Java-based concurrent systems. This approach applied the model checker SAL to generate these test sequences, which involves manually translating the UML model to the SAL model.…”

“…Further, we use exactly the same UML diagrams developed for analysis and design, without requiring any additional formalism or effort specifically made for testing purposes. Many reported methods require augmenting the UML specifications with specific annotations to facilitate the test derivation, or an additional formalism that the methods can process [15,31,8,10,16,20].…”

“…This predicate is a part of the compound predicate condition (r > 10) and (a 6 200). Let I 0 be the initial data: [30,20] (x = 30, r = 20). The condition (r > 10) is true for I 0 (20 > 10).…”