Skip to topic | Skip to bottom


MichaelaGreiler.ETSEr1.1 - 06 Sep 2011 - 13:03 - MichaelaGreiler

Start of topic | Skip to actions

Eclipse Test Suite Exploration Tool (ETSE)

The Eclipse Test Suite Exploration Tool implements five architectural views that can be used to understand test suites for plug-in-based systems from an extensibility perspective. To create these views static meta data and dynamic trace data is used. For more information on the views and the tool please download the Technical Report.

Overview of ETSE's Architecture


The ETSE tool was presented at the Eclipse Testing Day 2011 TestingDayBanner2011.png

Download and install ETSE via ETSE's Update site: Download via Update Site

ETSE is in development. Please check regularly for updates...

Getting Started with ETSE

How to install ETSE

It's recommended to use the update site to download and install ETSE.

To analyse your own projects, you will need:

- The ETSE core framework: This framework allows to analyse static meta data and trace data. Optional:

- The ETSE GUI: This plug-in allows to interact with the ETSE core via the Eclipse IDE.

To produce execution traces of your test run, you can make use of the ETSE Tracer:

- The ETSE tracer: This plug-in can be used to trace the test run by means of AspectJ?. You can also use a tracing tool of your choice, and prepare trace data to be used with ETSE.


ETSE needs a configuration file, which tells the tool which plug-ins, test-components and trace files to analyse.

To make the start as easy as possible, we provide a small example - consisting of all data ETSE needs. If you would like to use that please write me an email, and I will provide you with the data.

Surely, you can feed ETSE your own data. Then ETSE will need:

Plug-ins Under Test directory: A directory where the plug-ins under test are located.

Test Components directory: A directory where the test components can be found.

Full execution trace: A trace of "method-call"-events during test execution

Extension initialization execution trace: Traces "extension-initialization" events

Extension and Test method trace: Traces events of method-calls and extension initialization

Additional jars: To analyse the byte-code of the plug-ins under test, ETSE needs required jars on the classpath

For more detailed information on the format of the execution traces either have a look at the technical reports about ETSE or contact me.

For further informations please feel free to contact Michaela Greiler.

You are here: MichaelaGreiler > ETSE

to top

Copyright © 2003-2018, Software Engineering Research Group, Delft University of Technology, The Netherlands