How do I view code coverage for my functional tests?

Short answer:

Here’s how…. However, use it only for figuring out what functionality is not covered, not as a workaround for not having enough unit and integrations.

Having to use functional tests to determine percentage of code coverage is IMO a bad smell, avoid as much as possible.

Update site: http://swtbot.sourceforge.net/latest/update-site/

SWTBot 1.2.0 is the 3rd of the 1.x releases of SWTBot was released last night, and there have already been about 200 downloads by the time of writing this blog post.

SWTBot has always believed in release early release often mantra, and pushes out nightly builds out of CruiseControl. From the download stats I’m looking at, there are more downloads of the nightly build than the ‘stable’ available on the sourceforge mirrors.

The highlight of the release is support for view menus and view toolbar.

Thanks to the contributors and adoptors, for patches, criticism, and suggestions for improvement. The release has fixed about 42 issues.

Read more on the detailed release notes and the changelog.

Direct download link: http://sourceforge.net/project/showfiles.php?group_id=188411&package_id=220519&release_id=601136

Update site: http://swtbot.sourceforge.net/latest/update-site/

Some features:

• A recorder API — now you can record SWTBot scripts. Still in beta though.
• Better SWTBot integration in eclipse — now you can run tests within eclipse.
• More API — now you can use more SWT controls using an even richer API.
• More stable than before.

For more details, you can read up on the release notes here.

A lot of folks have asked me if there’s a way I could provide any intermediate builds as and when fixes are checked in into trunk. To address this issue, I’ll be putting in some build scripts to push builds out of the CruiseControl running at ThoughtWorks.

Watch out for this space for an announcement about this…

What’s next, I hear there’s something called eSWT and eRCP out there, there’s also some search engine company doing something similar

Some features:

• A recorder API — now you can record SWTBot scripts.
• Better SWTBot integration in eclipse — now you can run tests within eclipse.
• More API — now you can use more SWT controls using an even richer API.

For more details, you can read up on the release notes here.

Here is a quick list of features supported by SWTBot.

Here is a link to some sample code and screencasts

This time SWTBot makes a profound statement “Hello World“, to demonstrate what SWTBot is able to do. Click here to view full screen.

SWTBot also runs on Linux, although the screencasts are all recorded in Windows. Click here, in case you wish to look at the script that executes this.

This preview was created using Wink.

So here it is. Click here to view full screen.

This is still pre-alpha, as of now, you will see some basic functionality to be able to click on some basic SWT controls. The litmus test would be to eventually run this inside eclipse — to test eclipse itself

This preview was created using Wink.