On Linux, you need to have a X session started with a Window Manager. GTK must be installed.

On Linux, you need to have a X session started with a Window Manager. GTK must be installed.

−

== Locally on Linux: use another DISPLAY to save time ==

+

== Locally ==

−

SWTBot requires tested application to have focus in order to work well. If it happens on the DISPLAY you're working on, then you have to wait for tests to end before you can go on working. It's a waste of time. On Linux, you can run your test on another DISPLAY, so you can keep on working while tests are running. You can use '''Xephyr''' for that, since it allows you to see what is happening in another window. You'll also need to have a Window Manager started on this Xephyr. we recommand to run Metacity, but any other WM should run (twm is successfully used too).

+

=== Linux hints ===

+

+

==== use another DISPLAY to save time ====

+

SWTBot requires tested application to have focus in order to work well. If it happens on the DISPLAY you're working on, then you have to wait for tests to end before you can go on working. It's a waste of time. On Linux, you can run your test on another DISPLAY, so you can keep on working while tests are running. You can use '''Xephyr''' for that, since it allows you to see what is happening in another window. You'll also need to have a Window Manager started on this Xephyr. we recommand to run '''metacity'''.

<pre>

<pre>

$ Xephyr -screen 1024x768 :51 &

$ Xephyr -screen 1024x768 :51 &

Line 15:

Line 18:

$ ...command that runs SWTBot tests...

$ ...command that runs SWTBot tests...

</pre>

</pre>

+

+

The DISPLAY can be set from Eclipse Run configuration, in the Environment tab.

+

+

=== Windows hints ===

+

+

==== Use Cygwin/X ====

+

+

Never tested...

== On Jenkins ==

== On Jenkins ==

−

Use [https://wiki.jenkins-ci.org/display/JENKINS/Xvnc+Plugin Xvnc] or [https://wiki.jenkins-ci.org/display/JENKINS/Xvfb+Plugin Xvfb plugin| in you job to start on X session on a new DISPLAY. Then invoke a "Shell build step" to start a window manager (metacity or twm are working fine, others should be fine too)

+

=== Linux hints ===

+

* Use [https://wiki.jenkins-ci.org/display/JENKINS/Xvnc+Plugin Xvnc] or [https://wiki.jenkins-ci.org/display/JENKINS/Xvfb+Plugin Xvfb] Jenkins plugin in you job to start on X session on a new DISPLAY.

+

* Invoke a "Shell build step" to start a window manager: ''metacity'' is recommended, some other may work too, but the oldest ones (such as twm) are known to make some tests failing

+

+

=== Windows hints ===

+

* Do Not install Jenkins as a service: it causes focus issues that prevent SWTBot from working well.

= With Maven and Tycho =

= With Maven and Tycho =

−

Tycho tests can be run in SWTBot as normal surefire test. The only difference is SWTBot requires '''<useUIHarness>true</useUIHarness> and <useUIThread>false</useUIThread>'''

+

Tycho tests can be run in SWTBot as normal surefire test. First. you need to make sure SWTBot bundles are available in your [[Tycho/Target Platform#Target platform configuration|target platform]]. Then, the only difference is SWTBot requires '''<useUIHarness>true</useUIHarness>''' and '''<useUIThread>false</useUIThread>'''

<source lang="xml">

<source lang="xml">

Line 42:

Line 58:

</source>

</source>

−

+

Debug can be enabled using the tycho-surefire-plugin [http://www.eclipse.org/tycho/sitedocs/tycho-surefire/tycho-surefire-plugin/test-mojo.html#debugPort -DdebugPort] flag on command-line.

* If you're using PDE/Build, those bundles must be installed in your target-platform. If you don't use a target-platform definition, then it has to be installed in the Eclipse which hosts your PDE/Build using the following instructions.

+

* If you're trying to run tests on an existing application, you'll need to install SWTBot stuff directly in the application (from installer UI or using the following instructions

See [[Equinox/p2/Director_application|Director app wiki page]] for details and this [http://wiki.eclipse.org/Equinox_p2_director_application/Examples/Install_into_eclipse_using_SDKProfile examples for installing with Ant].

+

+

=== or unzipping manually (deprecated) ===

−

=== or Manually ===

+

This approach is deprecated because installing bundles just by unzipping does not ensure a successful installation. Using p2 is much better as it will generally work, and if it does not, it tells you why. Please also note that this approach is not supported/tested since SWTBot 2.1.0.

* Download the '''Headless Testing Framework''' for running tests from within ant. This file is called named something like org.eclipse.swtbot.eclipse.test-2.0.0.187-dev.zip

* Download the '''Headless Testing Framework''' for running tests from within ant. This file is called named something like org.eclipse.swtbot.eclipse.test-2.0.0.187-dev.zip

Line 83:

Line 109:

** org.apache.log4j

** org.apache.log4j

−

=== Setup ===

+

== Installing your SWTBot test plugin ==

−

Your folder structure should look like the following:

+

* If you're using PDE/Build, then your test bundle needs to be either available in the workspace then built and installed at the same time as your other bundle, or installed in the target-platform.

−

+

* If you're trying to run tests on an existing application, you'll need to install SWTBot stuff directly in the application (from installer UI or using the following instructions. This can be achieved using the p2.director [http://help.eclipse.org/indigo/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/p2_director.html cammand-line] or [http://wiki.eclipse.org/Equinox_p2_director_application/Examples/Install_into_eclipse_using_SDKProfile Ant task].

$ TEST_CLASS=com.yourcompany.product.test.AllTessts # see http://github.com/ketan/swtbot/blob/master/org.eclipse.swtbot.eclipse.finder.test/src/org/eclipse/swtbot/eclipse/finder/AllTests.java for an example

+

# /path/to/your/application must be replaced by the path to your application, which contains the plugins/ folder

−

$ TEST_APPLICATION_ID=com.yourcompany.example.application # the id of the application that needs to be tested

+

# /path/to/your/workspace is the location of the workspace that will be used to run tests. It can be a non-existing/empty folder, so a new workspace will be created; or an existing workspace folder, which will be reused for the test execution

−

$ WORKSPACE=/path/to/your/workspace

+

## Which test to run?

−

$ TEST_PRODUCT_ID=com.yourcompany.product # optional, if you're not using a product, please do not add the -product argument in the command below

+

# com.yourcompany.test.bundle must be replaced by the Bundle-SymbolicName of the bundle which contains the test you want to run

# com.yourcompany.product.test.AllTests must be replaced by the name of the Test class you want to run

+

## On what application should the test run?

+

# com.yourcompany.product (optional) is the RCP product you want to start while running testss, If you are not using a product, please do not add the -product argument in the command below. Examples: org.eclipse.sdk, com.jboss.jbds.product...

+

# com.yourcompany.application is the id of the application that needs to be tested. Example: org.eclipse.ui.ide.workbench

This will run the test specified by TEST_CLASS and generate the test output in ECLIPSE_HOME/TEST_CLASS.xml. This output can be parsed using junitreport ant task.

This will run the test specified by TEST_CLASS and generate the test output in ECLIPSE_HOME/TEST_CLASS.xml. This output can be parsed using junitreport ant task.

Line 174:

Line 182:

The ${library-file} is part of the '''Headless Test Framework''' and can be viewed at http://github.com/ketan/swtbot/blob/master/org.eclipse.swtbot.eclipse.junit4.headless/library.xml. This ant script performs the actual launch for the tests using the command line above.

The ${library-file} is part of the '''Headless Test Framework''' and can be viewed at http://github.com/ketan/swtbot/blob/master/org.eclipse.swtbot.eclipse.junit4.headless/library.xml. This ant script performs the actual launch for the tests using the command line above.

+

+

=== Debugging from Eclipse ===

+

+

You can enable debug using standard JVM debug flags on your test process ''-Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=y'' and then using Eclipse debug "Remote Java Application", bind it to port 8000 (as specified by ''socket'' in command-line).

+

+

= On an already packaged RCP application =

+

+

== Alter an RCP application to install and run your tests ==

+

+

# Your tests must be available in a p2 repository/update-site

+

# Use p2 UI or [http://help.eclipse.org/indigo/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/p2_director.html p2 director] in install SWTBot + your test bundles from update-sites into you application

+

# Use the command-line described earlier to start SWTBot test execution on your application (think about setting the '''-product''' and/or '''-application''' parameters)

+

+

You can debug this from Eclipse using the command-line arguments described earlier.

+

+

== Or, use your IDE to run tests on an existing application ==

+

+

# Install SWTBot in your IDE to access the SWTBot configuration menus

+

# Create a Target Platform made of your application + SWTBot runtime.

+

# Import your test bundles as projects in your workspace

+

# Then use the "SWTBot tests" wizard to configure the execution: think about including all Target Platform + SWTBot + your tests bundles; and configure product to refer to your application.

Environment requirements

On Mac and Windows, you can only run SWTBot tests in the main UI session, and you have to wait for tests to finish before you can keep on working.
On Linux, you need to have a X session started with a Window Manager. GTK must be installed.

Locally

Linux hints

use another DISPLAY to save time

SWTBot requires tested application to have focus in order to work well. If it happens on the DISPLAY you're working on, then you have to wait for tests to end before you can go on working. It's a waste of time. On Linux, you can run your test on another DISPLAY, so you can keep on working while tests are running. You can use Xephyr for that, since it allows you to see what is happening in another window. You'll also need to have a Window Manager started on this Xephyr. we recommand to run metacity.

The DISPLAY can be set from Eclipse Run configuration, in the Environment tab.

Windows hints

Use Cygwin/X

Never tested...

On Jenkins

Linux hints

Use Xvnc or Xvfb Jenkins plugin in you job to start on X session on a new DISPLAY.

Invoke a "Shell build step" to start a window manager: metacity is recommended, some other may work too, but the oldest ones (such as twm) are known to make some tests failing

Windows hints

Do Not install Jenkins as a service: it causes focus issues that prevent SWTBot from working well.

With Maven and Tycho

Tycho tests can be run in SWTBot as normal surefire test. First. you need to make sure SWTBot bundles are available in your target platform. Then, the only difference is SWTBot requires <useUIHarness>true</useUIHarness> and <useUIThread>false</useUIThread>

A Screencast

Installing headless Testing Framework

If you're using PDE/Build, those bundles must be installed in your target-platform. If you don't use a target-platform definition, then it has to be installed in the Eclipse which hosts your PDE/Build using the following instructions.

If you're trying to run tests on an existing application, you'll need to install SWTBot stuff directly in the application (from installer UI or using the following instructions

With p2 (recommanded)

From your favourite RCP application using p2, run, by replacing SWTBot site by the SWTBot update site of the version you want to use

or unzipping manually (deprecated)

This approach is deprecated because installing bundles just by unzipping does not ensure a successful installation. Using p2 is much better as it will generally work, and if it does not, it tells you why. Please also note that this approach is not supported/tested since SWTBot 2.1.0.

Download the Headless Testing Framework for running tests from within ant. This file is called named something like org.eclipse.swtbot.eclipse.test-2.0.0.187-dev.zip

You'll need the following plugins from swtbot (you don't need all the swtbot packages)

org.eclipse.swtbot.swt.finder

org.eclipse.swtbot.eclipse.finder

org.hamcrest

org.junit4(recommended) you may also use org.junit

org.apache.log4j

Installing your SWTBot test plugin

If you're using PDE/Build, then your test bundle needs to be either available in the workspace then built and installed at the same time as your other bundle, or installed in the target-platform.

If you're trying to run tests on an existing application, you'll need to install SWTBot stuff directly in the application (from installer UI or using the following instructions. This can be achieved using the p2.director cammand-line or Ant task.

Executing

The key is to run the org.eclipse.swtbot.eclipse.junit4.headless.swtbottestapplication

Command-line

Here's a command line argument that's used to execute the tests:

## Where to run the tests?# /path/to/your/application must be replaced by the path to your application, which contains the plugins/ folder# /path/to/your/workspace is the location of the workspace that will be used to run tests. It can be a non-existing/empty folder, so a new workspace will be created; or an existing workspace folder, which will be reused for the test execution## Which test to run?# com.yourcompany.test.bundle must be replaced by the Bundle-SymbolicName of the bundle which contains the test you want to run# com.yourcompany.product.test.AllTests must be replaced by the name of the Test class you want to run## On what application should the test run?# com.yourcompany.product (optional) is the RCP product you want to start while running testss, If you are not using a product, please do not add the -product argument in the command below. Examples: org.eclipse.sdk, com.jboss.jbds.product...# com.yourcompany.application is the id of the application that needs to be tested. Example: org.eclipse.ui.ide.workbench
java \
-Xms256M-Xmx768M -XX:MaxPermSize=512M #Memory settings and other VM args such as System properties settings \-jar/path/to/your/application/plugins/org.eclipse.equinox.launcher_*.jar \
-application org.eclipse.swtbot.eclipse.junit4.headless.swtbottestapplication \
-product com.yourcompany.product # optional, only if you are working with a product \-testApplication com.yourcompany.application \
-data/path/to/your/workspace \
-testPluginName com.yourcompany.test.bundle \
formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,/path/to/reports/com.yourcompany.product.test.AllTests.xml \
formatter=org.apache.tools.ant.taskdefs.optional.junit.PlainJUnitResultFormatter \
-className com.yourcompany.product.test.AllTests \
-os linux -ws gtk -arch x86_64 #Adapt to your os/ws/arch \-consoleLog-debug

This will run the test specified by TEST_CLASS and generate the test output in ECLIPSE_HOME/TEST_CLASS.xml. This output can be parsed using junitreport ant task.

Debugging from Eclipse

You can enable debug using standard JVM debug flags on your test process -Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=y and then using Eclipse debug "Remote Java Application", bind it to port 8000 (as specified by socket in command-line).

On an already packaged RCP application

Alter an RCP application to install and run your tests

Your tests must be available in a p2 repository/update-site

Use p2 UI or p2 director in install SWTBot + your test bundles from update-sites into you application

Use the command-line described earlier to start SWTBot test execution on your application (think about setting the -product and/or -application parameters)

You can debug this from Eclipse using the command-line arguments described earlier.

Or, use your IDE to run tests on an existing application

Install SWTBot in your IDE to access the SWTBot configuration menus

Create a Target Platform made of your application + SWTBot runtime.

Import your test bundles as projects in your workspace

Then use the "SWTBot tests" wizard to configure the execution: think about including all Target Platform + SWTBot + your tests bundles; and configure product to refer to your application.