Integrate Selenium Grid and Sikuli API

Currently, I am working on the automation testing framework, which combines with both Selenium Grid and Sikuli API.

I already implemented a library which includes functionality of Selenium and Sikuli, and it works well when I set up my hub and node on the same machine. However, this is just the same as running Selenium RC on the machine.

So, in order to achieve parallel testing, my next step is to lau开发者_如何学Pythonnch the nodes from other machines and register them to the hub machine. The idea environment is Amazon EC2 instance.

Hub: Linux box

Nodes: win server 2008

It works fine if I just ran the tests using the library only contains Selenium functions. However, I got error message that

"NO X11 DISPLAY variable was set, but this program performed an operation which requires it."

Should I export DISPLAY variable to the node's ip address? And do I need to set the node machine as an X server? What if there are many instances registered to the hub machines?

Sorry for the vague question... but any idea that how to implement this framework is appreciated. I am using selenium grid since there are many action performing graph verification. It would be very efficient if I can do it parallel testings.

Thanks a lot for any help and advice.

There is a project aiming at providing Sikuli capabilities on Selenium Grid.

https://github.com/sterodium/selenium-grid-extensions

It works by adding extensions both on Selenium Grid hub and nodes.

See my blog post about the topic of integrating tools like Sikuli and AutoIt with Selenium Grid. It provides a theoretical approach to implement said automation, though to my knowledge no one has yet implemented a working solution to demonstrate.

http://autumnator.wordpress.com/2011/12/22/autoit-sikuli-and-other-tools-with-selenium-grid/

On a side note, not sure how your X.11 issue came into play, it would be best you work on the framework using local network of machines with Selenium Grid before you convert to an Amazon EC2 deployment. It helps in the design and debug process as EC2 may present its own issues so you want to have the simplest basic Grid setup working first (non-EC2).