The plugin will work for Hudson as well as for Jenkins. As the installation, configuration and use of the plugin is nearly the same for Hudson and Jenkins, this section uses Hudson for the sake of simplicity and will point to Jenkins where appropriate.
Hudson and Jenkins monitor the executions of repeated jobs, such as building a software project or jobs run by cron. (For more about Hudson see java.net/projects/hudson/, for more about Jenkins see jenkins-ci.org.)
Using the plugin described in this section, it is possible to run Squish tests as Hudson and Jenkins jobs.
The plugin can be downloaded using the following URL: download.froglogic.com/resources/squish-hudson-jenkins-plugin_latest.zip.
To install the plugin, simply unzip the file and move or copy the .hpi
file into HUDSON_HOME/plugins where
HUDSON_HOME is Hudson's home directory. For Jenkins the home
directory is named JENKINS_HOME. Once the
.hpi file is in the right place it can be enabled
simply by restarting Hudson. After the restart, there should be an entry
for the Squish plugin in the Hudson plugin manager.
After checking that the Squish plugin is correctly loaded, the next step is to add Squish's installation path to Hudson's global system configuration and to decide if the building should fail if a Squish verification fails. Usually the Squish installation path will be set to “Default installation path” but if you're using more than one Squish installation or want to configure a different Squish installation path for a slave node, the “Advanced configuration” will be appropriate. Each entry must consist of a key pointing to an absolute Squish path e.g. qt462/squishPath=C:\SquishQt462. The key (qt462) can be referenced inside the job configuration which is explained next.
To run Squish tests in the Hudson build process we must adapt the job configuration to include Squish. Here we will use the address book example that is shipped with Squish.
The only thing we must do is to add a new build step which we'll call “Squish”, to the job configuration, and to set up the test suite and the test cases which we want carried out. The configuration key points to the Squish installation path. If set to Default or left blank the “Default installation path” inside the Hudson system configuration will be used; otherwise the key inside “Advanced path configuration” will be used. Additionally a host and port could be specified to use an already running squishserver. In the screenshot we have added two build steps, both using the same test suite, but with different test cases.
After applying the new build step we can run the job. When the run has finished there is a link on the summary page to the Squish test results.
The Squish test results appear inside Hudson:
