Supaporn Kansomkeat

A Comparative Evaluation of Tests Generated from Different UML Diagrams

This paper presents a single project experiment on the fault revealing capabilities of model-based test sets. The tests are generated from UML statecharts and UML sequence diagrams. This experiment found that the statechart test sets did better at revealing unit level faults than the sequence diagram test sets, and the sequence diagram test sets did better at revealing integration level faults than the statechart test sets. The statecharts also resulted in more test cases than the sequence diagrams. The results show that model-based testing can be used to systematically generate test data and indicates that different UML models can play different roles in testing.

Generating test cases from UML activity diagrams using the Condition-Classification Tree Method

A key technical challenge in software testing is the design of useful test cases. Test design can be based on a variety of software artifacts, including requirements, designs, or even the implementation. The Unified Modeling Language (UML) is now widely used to describe object-oriented designs. This paper focuses on one UML diagram, the activity diagram, which is used to model software behavior. This paper proposes the Condition-Classification Tree Method for generating test cases from activity diagrams. Activity diagrams are used to generate condition-classification trees, which are then used to create test case tables and test cases. The paper presents experimental data that show the proposed method can help generate a relatively small number of test cases at reasonable cost, early in development.

An analysis technique to increase testability of object-oriented components

Object‐oriented component engineering is increasingly used for system development, partly because it emphasizes portability and reusability. Each time a component is used, it must be retested in the new environment. Unfortunately, the data abstraction that components usually use results in low testability. First, internal variables cannot be directly set. Second, even though a test input may trigger a fault, the failure does not propagate to the output. This paper presents a technique to increase object‐oriented component testability, thereby making it easier to detect faults. Components are often sealed so that source code is not available. The program analysis is performed at the Java component bytecode level. A components bytecode is analysed to create a control and data flow graph, which is then used to increase component testability by increasing both controllability and observability. We have implemented this technique and applied it to several components. Experimental results reveal that fault detection can be increased by using our increasing testability process. Copyright

Syntax-based test case generation for web application

Currently, web applications are popular and widely in many fields such as business, education, medicine and science. Because of the growing complexity of web applications, so reliability is important in development web application. A good testing technique helps to increase the web application reliability. This paper presents an approach to generate test cases with syntax-based approach. Our method includes three steps as follows. First, a web application is analyzed to create a graph that represents the flow of pages. Second, the graph of previous step is used to generate a syntax model. Finally, test cases are generated from the syntax model. We take the psu-tep system as a case study to illustrate our proposed method.