Thanks to Aurelien for
pointing this out to me via twitter.
information about Jubula:
tests are designed to be at the system / acceptance level.
So they are for testing use cases / workflows via the GUI
approach doesn’t use capture-replay, so there is a focus on
writing good, maintainable tests
main target group is testers who are not also programmers,
however there is, since January, a client API that makes
Jubula more accessible to developers as well: more
information on this is here 
don’t currently have a maven target for use during a maven
build, but you could start the Jubula testexec via ant – or
get in touch if you want to go down this road, and we can
talk about what needs to be done
you’re at Eclipse Con, then I’m happy to chat to you more
about Jubula / give you a demo. Just let me know. I’ll also
be at the project quality day all day. There will also be
some talks / demos about Jubula there
can find downloads, examples and docs for Jubula here .
Hope this information
interest in implementing full cycle testing for eclipse
full cycle I mean, testing starting from installation,
launching, execution basic operations(crud for
projects/files), perhaps compilation/execution of some
classes(jdt), shutdown, etc.
other words common scenarios would be:
-> installation -> restart-> create
-> installation -> restart -> uninstallation
scenarios should be executed with maven.
there any instruments available to implement such testing