2010
DOI: 10.5381/jot.2010.9.5.a1
|View full text |Cite
|
Sign up to set email alerts
|

Test Case Generation Based on State and Activity Models.

Abstract: We propose a novel testing technique for object-oriented programs. Based on the state and activity models of a system, we construct an intermediate representation, which we have named state-activity diagram (SAD). We generate test cases to achieve state-activity coverage of SADs. We have empirically evaluated the effectiveness of our approach. The results show that the proposed technique could detect seeded integration testing faults which could not be detected by the related approaches.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
15
0
1

Year Published

2012
2012
2022
2022

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 44 publications
(16 citation statements)
references
References 26 publications
0
15
0
1
Order By: Relevance
“…Previous work [24] identified state charts and sequence charts to be appropriate approaches for automatically deriving test cases based on models. Several publications presented some combinations of structural testing to improve test case generation [25] and more formal models for modeling systems behavior [26] [27]. Considering the temporal behavior remains open but will be considered as future work, e.g., based on [28].…”
Section: Discussionmentioning
confidence: 99%
“…Previous work [24] identified state charts and sequence charts to be appropriate approaches for automatically deriving test cases based on models. Several publications presented some combinations of structural testing to improve test case generation [25] and more formal models for modeling systems behavior [26] [27]. Considering the temporal behavior remains open but will be considered as future work, e.g., based on [28].…”
Section: Discussionmentioning
confidence: 99%
“…Approaches for doing so exist. Some authors use state machines to derive test cases (e.g., (Kim et al 1999;Samuel et al 2008;Kansomkeat and Rivepiboon 2003)), others use activity diagrams (Linzhang et al 2004;Mingsong et al 2009;Kim et al 2007;Tripathy and Mitra 2013), and still others both (Swaina et al 2010). However, many authors highlight that the UML models without additional annotation do not contain sufficient information for automated test generation.…”
Section: Discussionmentioning
confidence: 99%
“…A static slicing is formed by eliminating those parts of the program that are not relevant to the values stored in the selected set of variables at the selected point of interest. A dynamic slice is regarding with finding all statements that can affect its value for the current input, instead of all the statements that could influence the value of the variable for any inputs [9]. In this paper we have applied the dynamic slicing because the state of the object in these types of diagram is continuously changing [8], [5].…”
Section: Dynamic Slicing Of Stdgmentioning
confidence: 99%
“…A slicing technique is basically used to facilitate the process of testing and debugging [8], [5], [9]. There are two types of Slicing like Static slicing and dynamic slicing.…”
Section: Dynamic Slicing Of Stdgmentioning
confidence: 99%
See 1 more Smart Citation