Comments on: Call Graph Visualisation with AspectJ and Dot

By: igorbrejc.net » Fresh Catch For April 5th

igorbrejc.net » Fresh Catch For April 5th — Sun, 05 Apr 2009 14:01:21 +0000

[...] erik dörnenburg » Blog Archive » Call Graph Visualisation with AspectJ and Dot it would be interesting to implement this for .NET [...]

By: Ashish

Ashish — Tue, 18 Nov 2008 11:55:23 +0000

Thanks Erik, for this wonderful post. This is a very nice example of using multiple tools to achieve a goal in a few simple steps. Hopefully, shall be able to integrate the same in CI of the projects.

By: Nilanjan

Nilanjan — Fri, 03 Oct 2008 00:46:50 +0000

Really cool. Visually this is more useful than some number value shows up for cyclomatic complexity.

By: Adrian Kuhn

Adrian Kuhn — Thu, 02 Oct 2008 03:34:56 +0000

Cool to see this done for Java!
We had been studying such call graphs for Smalltalk tests here at the SCG labs some years ago, and came to the conclusion that presenting tests in the partial order of their coverage sets helps to pinpoint bugs if many tests fail. That is, if two tests fail and one covers a subset of the other, the one that covers the subset is more likely to point the developer to the bug.

Based on that insight, we later implemented an extension to JUnit, called JExample, where these dependencies are made explicit through producer-consumer relationships (simply an @Depends annotation). In an empirical study, we have shown that JExample in fact improves the pinpointing of errors. JExample extends JUnit and even runs fine with the normal JUnit plugin of Eclipse. Currently we are working on a fully automated program analysis, to automatically migrate test from JUnit to JExample.

@see http://smallwiki.unibe.ch/jexample/