Skip to main content
Jump to: navigation, search

Difference between revisions of "SWTBot/Proposal"

(changed goal to make it sensitive to other projects.)
m (fixed email addresses for spam bots.)
Line 31: Line 31:
'''Initial committers'''
'''Initial committers'''
* Ketan Padegaonkar (
* Ketan Padegaonkar (ketanpadegaonkar at gmail)
* Sriram Narayanan (
* Sriram Narayanan (ram at
'''Potential committers''' (individuals who have contributed patches)
'''Potential committers''' (individuals who have contributed patches)
Line 42: Line 42:
* ThoughtWorks Studios (
* ThoughtWorks Studios (
* Nirav Thaker (nirav.thaker at gmail)
* Nirav Thaker (nirav.thaker at gmail)
* Ravi Chodavarapu (
* Ravi Chodavarapu (rchodava at

Revision as of 22:47, 11 May 2008


SWTBot ( is a functional testing tool for SWT/Eclipse based applications. That eases and supports testing of multithreaded applications. SWTBot is capable of playback and recording of SWTBot Java "scripts", there are plans to provide scripting support for various other languages including JRuby(, and Groovy(

SWTBot is proposed as an open source project under the Eclipse Technology Project ( This proposal is still in the Project Proposal Phase, and this proposal is being made in order to call for more community participation.

Background and Goal

SWTBot has demonstrated some interesting capabilities ( and very early on, and is being supported by a few contributors.

The goal of SWTBot is to provide a lightweight functional testing tool for SWT and Eclipse, and make it easy for developers and non-developers to automate testing of applications written using Eclipse.

Packaging and Deployment

SWTBot currently ships in the form of an eclipse update site, and also an independent .zip/.tgz download, and it would continue to ship in these forms.

Project Scope

The scope of SWTBot is to make writing tests for SWT and Eclipse application easier not just for developers who understand the technologies, but also for Quality Analysts who understand the application and not the underlying technologies used to build them.

SWTBot should integrate well with JUnit so as to make execution and reporting of tests independent of Eclipse, yet integrate will with eclipse. This would mean that SWTBot tests can be run as an ant task as part of Continuous Integration using CruiseControl.

There are also efforts by individuals to port SWTBot to eRCP/eSWT.

Future Work

It is proposed that SWTBot should provide APIs that enable for scripting languages based on the JVM. This would mean that scripts could potentially be written using JRuby ( or Groovy(

To make writing scripts easier, it is also proposed for better Eclipse integration, introspection of the application, and basic support for scripting/debugging.



  • Chris Aniszczyk
  • Someone else

Initial committers

  • Ketan Padegaonkar (ketanpadegaonkar at gmail)
  • Sriram Narayanan (ram at

Potential committers (individuals who have contributed patches)

  • Cedric Chabanois (cedric.chabanois at
  • Lechner Sami (lechner.sami at gmail)

Interested parties

  • PDE (Chris Aniszczyk)
  • ThoughtWorks Studios (
  • Nirav Thaker (nirav.thaker at gmail)
  • Ravi Chodavarapu (rchodava at

Back to the top