froglogic / All / Squish tip of the week: How to setup a Jenkins slave to run Squish tests

Squish tip of the week: How to setup a Jenkins slave to run Squish tests

Did you know that you can use Jenkins to run Squish tests?

Jenkins, previously known as Hudson, is an open source tool for continuous integration* written in Java. Many companies use Jenkins to deploy and automate projects for their software life circle.

As Jenkins supports the master/slave mode where the workload of building projects can be assigned to multiple slave nodes, only a single Jenkins installation is needed to host a large number of projects and to provide different environments needed for builds and tests. Together with Squish automated and functional GUI (regression) testing gets easier and less time consuming.

Jenkins & Squish GUI Tester

In our Knowledge Base you will find a detailed instruction on how to setup a Jenkins slave to run Squish tests.

*Continuous Integration (CI) is a part of modern software development. CI reflects the process of building and testing applications. For example nightly builds where a program code will be compiled and the Software will be tested. If problems occur, a developer will be informed.

Related topics


Could you follow up on some missing detail, specifically how to pass the –debugLog and the –interactive options to squishrunner using the jenkins plugin. Without those, (running SquishQT) nativeType() style navigation to deal with native OSX file dialogs etc. won’t work.

Hi Michael,

Thank you for you feedback on this article. We are sorry to let you know that the squishrunner options -debugLog and -interactive are currently not supported through the Jenkins plugin. We will treat your comment as a feature request to add support these options in a future version of the plugin.

Anyway, executing a Squish for Qt test that makes use of nativeType() to automate a native file dialog on OS X should even work with the current version of the plugin. If your test execution fails to automate the file dialog through nativeType(), this might have other reasons like a synchronization problem. For a better insight, I suggest to get in contact with and send the script that you are executing together with the log files from the Jenkins execution. We can then discuss how to resolve your issue.

Kind regards

How to mail the results via Jenkins

Leave a Reply

Your email address will not be published. Required fields are marked *

Copy link
Powered by Social Snap