Difference between revisions of "SWTBot/Generator"
|(2 intermediate revisions by one other user not shown)|
|Line 1:||Line 1:|
== Screencast ==
== Screencast ==
Revision as of 03:25, 14 January 2013
|Open Bugzilla tickets|
|Open Gerrit reviews|
Purpose and limitations
What it does
The test generator can be enabled on any Eclipse-based application at runtime. It monitors at UI events as they are performed by user and the generate some pieces of code that can be reused later in automated tests to playback user actions.
Some conceptual limitations of UI recorders (which are true for SWTBot Generator, but also for Selenium or other recorder/playback engines):
- There are several ways to identify a widget, the recorder will choose only one, that may not be the best
- The recorder understand "atomic" UI operation, which may be too fined-grained compared to what you want to test
- The generator is not aware of your code style and tastes, so it may generate code that is not conform to your standards
- The generator doesn't know what to check, it's just a bot: it's your role to add assertions and other checks
All those points mean that the generation of code is only something that makes you save time by replacing some code writting, but the generated code always needs to be reviewed and enriched with assertions and probably improved.
A limitation that is specific to this recorder and Eclipse is that it does not (yet) support GEF.
How to get the maximal benefit from it
Speed up the process of creating a test: instead of writing directly code, start by running your test scenario with the generator enabled. You'll get a huge part of your code already written down, ready to go into a TestCase. Then improve that code is necessary and add your assertions and checks.
Ask users to provide their scenarios as code: If possible, when a user has a bug, ask him to start the recorder (you could embed its enablement in a higher-level menu - Help > Record usage scenario -to prevent end-users from doing complex operations); and ask your users to post the generated code. It will reduce the gap between users reports and unit tests.
Here is a screencast presenting SWTBot Recorder and Generator: https://vimeo.com/55953990
The Test recorder and generator is a single plugin to install in any RCP application (may it be your Eclipse IDE, or a bundled RCP application. You can get it from the SWTBot update-site/p2 repository (starting from version 2.0.6).
With p2 UI: TODO screenshot of installation
With p2 director, install bundle org.eclipse.swtbot.generator:
java -jar plugins/org.eclipse.equinox.laucher_*.jar -application org.eclipse.equinox.p2.director -repository <choose_a_SWTBot_p2_repo> -installIU org.eclipse.swtbot.generator
Ensure the org.eclipse.swtbot.generator bundle is part of your Lauch Configuration TODO: screenshot
Set the -Dorg.eclipse.swtbot.generator.enable=true system property TODO: screenshot
From a RCP app
Ensure org.eclipse.swtbot.generator bundle is installed in your application (use ls or OSGi console at runtime to check that).
Set the -Dorg.eclipse.swtbot.generator.enable=true system property in your config.ini. Example for JBoss Developer Studio, in jbdevstudio/studio/jbdevstudio.ini, line 17:
The generator window generates code, copy-paste it where you want
The Generator places some SWT listeners that look at events and generate code from each event. A Generator support is just a set of "rules" that are classes that process (or not) the current event to generate some code. Processing an event is divided in 2 pieces:
- Create an accessor for the widget (eg: bot.button("blah")
- create an action on the widget (eg: .click())
Contribute your own Bot support
There is an extension point for that in org.eclipse.swtbot.generator. We recommend you to get the source for the org.eclipse.swtbot.generator plugin and see what's in it. The default SWTBot support is installed as an extension too, so you can take it as an example.
The contributions tools and process are the same as for any SWTBot part. See SWTBot/Contributing.