Our current setup requires that we have ever increasing code coverage numbers in our testing. We're starting to run out of pure non-UI code to test, so it would be very helpful to find a proper solution for doing UI testing on our build agents behind Jenkins. The tests ideally would run in an automated way like typical JUnit test suites.
In the past we'd dabbled very little with WindowTester to achieve this, but didn't do much test writing with it.
We currently build and test against Eclipse 4.3 and 4.4 on linux (ubuntu) build agents.
Here's the listing of options from Eclipse's wiki: http://wiki.eclipse.org/Eclipse/Testing#UI_tests
It would be helpful to try writing some unit tests with some of these frameworks to see what feels most natural, is easiest to get started and maintain, etc. To me, the open source options would be strongly preferred, and in that case the frontrunners would be: SWTBot, WindowTester, Automated GUI Recorder, and Jubula. I'd say we shoudl try and write a few tests against untested UI code. You can look at http://studio-jenkins.appcelerator.org/job/studio3-core-development/lastCompletedBuild/jacoco/ and delve into the latest build's code coverage report to get an idea of where we have holes in our testing (pretty much every part of the UI).