software tools: EclEmma

Posted in Eclipse, programmer productivity at 8:09 pm by ducky

In a previous post, I said that I thought it would be handy to have your source editor color code based on which lines were executed in the prior execution of the code. I mused about merging Eclipse with a profiler in that post, but later realized that I could also use a code completion tool… and then discovered someone had already done it. EclEmma is a fine code coverage tool that is nicely integrated with Eclipse and does exactly what I want.

EclEmma isn’t positioned as a debugging tool, but it sure can be used as one.


  1. Best Webfoot Forward » comparative programming linguistics said,

    January 5, 2008 at 4:44 pm

    […] a hobby project in PHP while reading up on tools like odb, JML, Daikon, Esc/Java2, javaspider, and EmmaECL. The contrast is […]

  2. Best Webfoot Forward » VanDev talk summary said,

    February 6, 2008 at 9:31 pm

    […] Many code coverage tool will also color lines based on whether they were executed or not. This is a cheap way to see which execution paths were taken! Examples include Visual Studio, the Intel C++ Code Coverage Tool, and the Eclipse plug-in EclEmma. […]

  3. Best Webfoot Forward » Wish list: wonder-code-coverage tool said,

    May 6, 2008 at 4:07 pm

    […] previous posts, I talked about wanting a code-coverage tool to use while debugging, and how EclEmma did most of what I wanted. After my user study, where I dissected in detail how seven professional programmers did four […]

  4. Best Webfoot Forward » My MS thesis is done! said,

    July 24, 2008 at 5:47 pm

    […] source code background based on whether the messed-up code was fully, partially, or not executed. (EclEmma already does this, but does it for the entire run, not for selected sections of the program […]