Automatic test case generation for UML activity diagrams

  • Chen Mingsong*
  • , Qiu Xiaokang
  • , Li Xuandong
  • *Corresponding author for this work

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

87 Scopus citations

Abstract

The test case generation from design specifications is an important work in testing phase. In this paper, we use UML activity diagrams as design specifications, and present an automatic test case generation approach. The approach first randomly generates abundant test cases for a JAVA program under testing. Then, by running the program with the generated test cases, we can get the corresponding program execution traces. Last, by comparing these traces with the given activity diagram according to the specific coverage criteria, we can get a reduced test case set which meets the test adequacy criteria. The approachcan also be used to check the consistency between the program execution traces and the behavior of UML activity diagrams.

Original languageEnglish
Title of host publicationProceedings of the 2006 International Workshop on Automation of Software Test, AST '06, Co-located with the 28th International Conference on Software Engineering, ICSE 2006
Pages2-8
Number of pages7
DOIs
StatePublished - 2006
Externally publishedYes
Event1st International Workshop on Automation of Software Test, AST'06, Co-located with the 28th International Conference on Software Engineering, ICSE 2009 - Shanghai, China
Duration: 20 May 200628 May 2006

Publication series

NameProceedings - International Conference on Software Engineering
ISSN (Print)0270-5257

Conference

Conference1st International Workshop on Automation of Software Test, AST'06, Co-located with the 28th International Conference on Software Engineering, ICSE 2009
Country/TerritoryChina
CityShanghai
Period20/05/0628/05/06

Keywords

  • UML activity diagram
  • instrumentation
  • random test case
  • test adequacy

Fingerprint

Dive into the research topics of 'Automatic test case generation for UML activity diagrams'. Together they form a unique fingerprint.

Cite this