Jump to: navigation, search

Difference between revisions of "SWTBot/CI Server"

m (Added a page on CI servers and setup)
 
m (Add the swtbot furniture on the page)
 
Line 1: Line 1:
 +
{{SWTBot}}
 +
 
This page describes steps needed to run SWTBot on a [http://martinfowler.com/articles/continuousIntegration.html Continuous Integration] server. You can use SWTBot with [https://hudson.dev.java.net/ Hudson] [http://cruisecontrol.sourceforge.net CruiseControl] [http://ccnet.thoughtworks.com CruiseControl.NET] [http://cruisecontrolrb.thoughtworks.com/ CruiseControl.rb] or any other CI server of your choice.
 
This page describes steps needed to run SWTBot on a [http://martinfowler.com/articles/continuousIntegration.html Continuous Integration] server. You can use SWTBot with [https://hudson.dev.java.net/ Hudson] [http://cruisecontrol.sourceforge.net CruiseControl] [http://ccnet.thoughtworks.com CruiseControl.NET] [http://cruisecontrolrb.thoughtworks.com/ CruiseControl.rb] or any other CI server of your choice.
  

Latest revision as of 17:16, 22 February 2011


SWTBot
Website
Update Sites
Community
Mailing List
Forums/Newsgroups
IRC
Contribute
Open Bugzilla tickets
Open Gerrit reviews
Browse Source
Continuous Integration


This page describes steps needed to run SWTBot on a Continuous Integration server. You can use SWTBot with Hudson CruiseControl CruiseControl.NET CruiseControl.rb or any other CI server of your choice.

A lot of people use a setup where there are multiple environments running on VMWare/Zen or other virtualization products. Others prefer to use a single machine to run a build.

Prerequisites

  • Ensure that your session has screensaver disabled.
  • Ensure that your session does not 'lock up' after a specified period.

Windows

Windows requires that the process running SWTBot tests has a proper "session". A session in this case means a user logged in into the machine (if you have physical access to the keyboard/mouse or vmware console access). If the only access you have is over RDP, you need to ensure that the user running the tests is *always* logged in.

See this discussion for more details.

Linux

Linux is also a bit similar. Most CI tools support running the build job using a "display". Hudson has a XVnc plugin for this purpose. If you're running tests using XVnc (or other flavor of VNC) you must ensure that there is a window manager (gnome/xfce/kde) is present. I've noticed that there are certain setups where there is no window manager present and managing/changing window focus does not work right.