Visualizing Testsuites to Aid in Software Understanding

Cornelissen, B.; Deursen, Arie van; Moonen, Leon; Zaidman, Andy

doi:10.1109/csmr.2007.54

Cited by 54 publications

(56 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Tools for assisting in the understanding of test suites have been proposed by Cornelissen et al, who present a visualization of test suites as sequence diagrams [2]. Greiler et al propose higher level visualizations, aimed at assisting developers in seeing plug-in interactions addressed by their test suites [8].…”

Section: Related Workmentioning

confidence: 99%

“…We analyze how measuring similarity based test relations can help to (1) find relevant tests by showing test relationships, (2) understand the functionality of a test by describing high-level test cases with related unit test cases and (3) reveal blank spots in the investigated unit test suites. This paper is structured as follows: in Section 2, we discuss our test execution tracing approach.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Measuring Test Case Similarity to Support Test Suite Understanding

Greiler

Deursen

Zaidman

2012

Objects, Models, Components, Patterns

Self Cite

View full text Add to dashboard Cite

Abstract. In order to support test suite understanding, we investigate whether we can automatically derive relations between test cases. In particular, we search for trace-based similarities between (high-level) endto-end tests on the one hand and fine grained unit tests on the other. Our approach uses the shared word count metric to determine similarity. We evaluate our approach in two case studies and show which relations between end-to-end and unit tests are found by our approach, and how this information can be used to support test suite understanding.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Measuring Test Case Similarity to Support Test Suite Understanding

Greiler

Deursen

Zaidman

2012

Objects, Models, Components, Patterns

Self Cite

View full text Add to dashboard Cite

show abstract

“…Examples are getters and setters that are called from within a class (when called between classes, getter and setter accesses can indicate important relationships! ), and constructors and destructors of unimportant or unused objects (Cornelissen et al 2007a;Hamou-Lhadj and Lethbridge 2003). We can also filter elements of the program or its libraries, i.e., calls to specific components, classes, methods, etc.…”

Section: Trace Analysismentioning

confidence: 99%

“…-Metric-based filtering methods can be used to determine which parts to keep and which parts to discard from a trace. Examples are: using stack depth as a metric, i.e., filtering all calls above a specific depth (Pauw et al 1998) or below a specific depth (Cornelissen et al 2007a). Hamou-Lhadj and Lethbridge put forward a utilityhood metric that indicates the probability that a specific method is a utility method, which is based on fan-in and fan-out analysis, and use a threshold value to filter parts of the trace (Hamou-Lhadj and Lethbridge 2006).…”

Section: Trace Analysismentioning

confidence: 99%

Understanding Ajax applications by connecting client and server-side execution traces

et al. 2012

Self Cite

View full text Add to dashboard Cite

Ajax-enabled Web applications are a new breed of highly interactive, highly dynamic Web applications. Although Ajax allows developers to create rich Web applications, Ajax applications can be difficult to comprehend and thus to maintain. For this reason, we have created FireDetective, a tool that uses dynamic analysis at both the client (browser) and server-side to facilitate the understanding of Ajax applications. We evaluate FireDetective using (1) a pretest-posttest user study and (2) a field user study. Preliminary evidence shows that the FireDetective tool is an effective aid for Web developers striving to understand Ajax applications.

show abstract

“…We have conducted an experiment [5] in which we have reverse engineered and abstracted a form of UML sequence diagrams, which we call scenario diagrams. At the basis of this process lies a program's testsuite, of which the testcases are used as execution scenarios.…”

Section: Sdrmentioning

confidence: 99%

Dynamic Analysis Techniques for the Reconstruction of Architectural Views

Cornelissen

2007

14th Working Conference on Reverse Engineering (WCRE 2007)

Self Cite

View full text Add to dashboard Cite

Gaining an understanding of software systems is an important discipline in many software engineering contexts. It is essential that software engineers are assisted as much as possible during this task, e.g., by using tools and techniques that provide architectural views on the software at hand. This Ph.D. research addresses this issue by employing dynamic analysis for the reconstruction of such views from running systems. The aim is to devise new abstraction techniques and novel visualizations, to combine them, and to assess the benefits through substantial case studies and controlled experiments. This paper describes our approach, reports on the results thus far, and outlines our future steps.

show abstract

Visualizing Testsuites to Aid in Software Understanding

Cited by 54 publications

References 21 publications

Measuring Test Case Similarity to Support Test Suite Understanding

Measuring Test Case Similarity to Support Test Suite Understanding

Understanding Ajax applications by connecting client and server-side execution traces

Dynamic Analysis Techniques for the Reconstruction of Architectural Views

Contact Info

Product

Resources

About