This is an extension of YANGIDE-11:

I just noticed that the yangide source tree actually includes two projects with cool end-to-end UI integration tests (using the great Xored UI testing tool), but as of today none of them are currently run during yangide build and for proposed Gerrit changes. Having tests but not running them seems a shame! (Perhaps something like YANGIDE-10 would even have been detected by this?)

This bug is to discuss what it would take to get in particular the existing tests in org.opendaylight.yangide.editor.test and org.opendaylight.yangide.ext.refactoring.test to run for each build and proposed Gerrit change.

There is a Maven profile named "test" in the root pom.xml, so it would appear that a -Ptest would run these tests (I haven't tried yet) ?

I'm assuming that this is (was moved into) a separate profile because it cannot read headless? There are actually easy solutions to this (I've done this before..) - Jenkins can run a virtual X and then most such UI tests (unless they are VERY finicky) should run fine.

Who can we talk to about getting the Jenkins that runs the tests for yangide set up correctly, so that we can move to deleting that profile and instead simply include those two projects as normal <module> for any yangide build?