Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I will try to keep this question simple. I've done much research on the topic, and haven't found any solution.

GUI Tests fail when doing maven builds on Hudson (Jenkins). Hudson is running as a service, logged on as Local System. I have enabled the service to interact with the desktop, but the tests are still failing.

The machine is a WinXP 64bit, but I have the option to migrate to Win7 64bit if that will fix this.

How do I get GUI tests passing during a hudson (maven) build?


share|improve this question
How do the tests fail? What does/does not happen? Can you run the tests manually if you cd to the Jenkins work dir and do a manual mvn verify? – Bittrance Jun 28 '11 at 21:42
up vote 3 down vote accepted

According to this thread, the only way to do so is to not run it as a service, but instead run it as a logged-on user, with a desktop.

Personally, I had luck with the following settings: 1) write a batch file to launch the slave via JNLP/javaws 2) put said script into autostart 3) set the user to auto-login. This was all in a VM, so when I launched the VM it automagically registered itself as available to the hudson server.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.