Download Saros Test Framework

Background
Motivation
The original motivation was to find an appropriate GUI testing tool for Saros. Our requirements were:
‣ To test a minimal scenario of Saros, at least two Saros instances are needed, which may be not even at
the same computer. So the GUI testing tool for Saros should support distributed testing.
‣ The event source (activated by an application) and the event target (verified by another application)
are not in the same application and possibly not even at the same computer. So the GUI testing tool
should be able to control the test procedure synchronously.
‣ Saros is an Eclipse plugin project, so the tool should also support high-level operations on widgets of
Eclipse without great effort.
‣ Saros developers are familiar with Java, so it would be better to write test scripts with Java, e.g. JUnit
tests.
Evaluation
In his thesis3, the founder of STF Sandor Szücs intensively evaluated which methods and tools are most
suitable for our testing needs. Refer to this thesis for more information on this.
Conclusion
Based on these requirement the GUI testing tool SWTBot is outstanding among other candidates which
work with JUnit and can test SWT and Eclipse applications. It only does not support synchronization and
distribution. Finally, Sandor decided to write a tool himself that would overcome the shortcomings of
SWTBot. The result is STF.
3
http://www.inf.fu-berlin.de/inst/ag-se/theses/Szuecs10-DPPVI.pdf
13