Wednesday, March 24, 2010

Reverse-engineering of JUnit tests


Tuesday I presented MoDisco during two EclipseCon sessions at Santa-Clara:

We decided this year to illustrate MoDisco with a example based on JUnit :
  • reverse-engineering of source code containing JUnit tests (we took draw2d as a sample)
  • creation of a fine-grained EMF model describing the source code
  • definition of an extension (Facet) to find the JUnit Test suites, Test cases and Tests contained within the code



  • colorization (UICustom) of the packages, classes and methods to be tested, depending on how many tests are defined for them



  • transformation of the EMF model and regeneration of the source code to migrate from JUnit3 to JUnit4
The slides are available here.

I will blog soon to give more details about this JUnit use-case.


2 comments:

  1. Hi I've been trying to find about MoDisco for months I'm a Computer Science post-graduate student in UK at University of Leicester and we’ve chosen MoDisco as a theme for an essay. My name is Renata Brogan and I would like to ask you a few questions If I can... Or if you can indicate a source of information where I can research about MoDisco!!!
    1 - In Mo Disco software metrics are based in SMM, so I can't find any source of information about how the metrics are generated, if there is a specific compiler to generate the metrics from a specific legacy system.
    2 - How the SMM in MoDisco is related to KDM and the discovery managers.

    ReplyDelete