Sikuli & Continuous Integration with Hudson

No known issues only known challenges ;-)

The challenges you will face and the possible solutions depend on the rest of the things you want to do with Hudson.

I guess you want to use Sikuli to test your app's GUI.

These are the main questions:
- Which "language" you want to use for your tests? Jython (Python), JRuby (Ruby), Groovy, Scala, or plain Java are easy, any other choice will result in much more effort or might be impossible.
- Do you want to integrate Sikuli tests directly into your behavior tests?
- How and where will the tests be run (local or remote)?

At the bottom line, a Sikuli test is just a script, that can be run from command line, triggered by whatever is possible in your testing environment.

Hi RaiMan,

First of all, thank you for your quick reply :)

Now, my answers:
 - Which "language" you want to use for your tests? Jython (Python), JRuby (Ruby)
Ramona: Python (because it is so great :) )

- Do you want to integrate Sikuli tests directly into your behavior tests?
Ramona: Sorry for not knowing this already, but I assume by behavior tests you mean the tests which can be read by non-programmers. If so, I haven't given too much thought, but at this point, I guess the answer is Yes, I think so.

 - How and where will the tests be run (local or remote)?
Ramona: Not sure yet, but my best guess is remote, so that the machine holding Hudson can be maintained by someone else.

--- have a look at https://answers.launchpad.net/sikuli/+question/153455

--- - How and where will the tests be run (local or remote)?
that is not the real problem.
the question was meant: Will the Sikuli tests run on the same machine as the app to be tested?
Since if not, there will be some extra effort (VNC, RemoteDesktop, X11, ...)
There are some discussions about that in these Q&A's.

--- Python is nice, but Ruby is nicer ;-)
I just decided to switch totally to JRuby as far as Sikuli is concerned.
The main reason (beside all the other nice things for easy scripting and I am longer with Ruby than with Python): You can reopen classes even on the Java level. So it is very easy, to tweek Sikuli as you need it: you miss something - just add it on the fly. If you want to do this with Python (e.g. want a new method for Screen, Region, Match, ...), you have to modify the existing sikuli-script.jar or even rebuild it, if you step down to the Java level. No need for that with JRuby.