SikuliX

Using Sikuli as part of the build process

Asked by Tony Ryan

Hi guys, is there a way to utilise Sikuli tests as part of a continuous integration process by integrating the tests with Maven or Hudson? i.e. So that the build fails when when Sikuli tests are not completed in a satisfactory manner?

Thanks in advance for your help, great product.

Question information

Language:
English Edit question
Status:
Answered
For:
SikuliX Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Tony Ryan (ryant-dnb) said : 		#1

Shameless self-bump!

I take it that no-one has used Sikuli as part of a continuous integration process before? Even if I could fail a Maven build on the fail of a Sikuli test it would be beneficial...?

Revision history for this message
Jason Cox (jasonwilburcox) said : 		#2

I plan to use Sikuli for continuous integration. It's still a work in progress, but the current plan is to use Hudson to run Cucumber tests.

I am importing the Sikuli jar and using Sikuli directly in my tests. If you have your builds fail based on running the tests, then this should work for you. I'm sure you could do this with Maven as well.

Revision history for this message
lukewpatterson (lukewpatterson) said : 		#3

I've used Sikuli in CI.

I created a quick-and-dirty Maven plugin which allows you to specify a project folder (python script and images) to run. The plugin spawned a new process, and then used the CLI feature of Sikuli IDE to run the project. The exit code was evaluated by the plugin.

Sikuli isn't deployed to a Maven repo, so I had to custom deploy it.

e.g. my Maven project included a src/main/sikuli folder which contained the python and images

I also used video capture and included that in the Maven report so it was easier to troubleshoot when things went wrong.

Can you help with this problem?

Provide an answer of your own, or ask Tony Ryan for more information if necessary.

To post a message you must log in.