In this post we would like to clarify methods available for automated testing of Wt or JWt applications.

The most straight forward method is to implement server-based tests using WTestEnvironment. In this way one can define scripts which are server-side only, and which can be used to test functional aspects of an application. Because no browser is involved the test isn’t end-to-end (but it does capture everything in your application, it just does not test correct rendering by the Wt library). It may also be quite labor intensive to develop these scripts.

An attractive alternative are browser-based tests which are available through a number of frameworks (such as Selenium). These framewoks typically have an interactive script recorder where one can record scripts which can be replayed in one or more different browsers. This has obvious benefits over the previous method, but requires more tooling (and plumbing).

There are a few reasons however why Wt or JWt applications do not get along with browser-based automated testing frameworks, out of the box. Auto-generated id’s change from session to session and can thus not be used to identify a widget. Hard-coding an ID (using WWidget::setId() is really not recommended because it breaks possible reuse of your widgets, and widget reuse is really something we wish for you to have!

Fortunately, Selenium supports custom Locator Builders as extensions, and this is just what we need to make Selenium able to record test cases for Wt and JWt applications.

More than a few weeks late, we apologize, but all the better for it: 3.3.0 !

Here are the main links:

A new release candidate. Hopefully the last one as it might start to look ridiculous … !

Here are the main links:

A few more bug fixes we couldn’t hold you back !

Here are the main links:

A second release candidate for 3.3.0 … keep the feedback coming !

Here are the main links:

We uploaded a first release candidate for 3.3.0.

Here are the main links:

With only a few changes compared to 3.2.3 RC2, we are pleased to make 3.2.3 final.

Here are the main links:

You pulled 3.2.3 RC1 through the wrench, grilled the layout implementation, and got us great bug reports. Thanks! The result is RC2.

Here are the main links:

A new version of the library, with a typical mix of bug fixes and new features.

Here are the main links:

We uploaded final release packages for 3.2.2.

Updated 27 July 2012 ! We’ve identified and fixed a number of issues in the (new) layout managers which we released as 3.2.2-p1.

Here are the main links: