WET comes with different UI tools that dramatically reduces the testing effort. At the same time, the innovative concept used by WET helps to do away with some of the inherent issues that are part of recorders for test automation.

WET uses Ruby, a powerful object oriented scripting language. that lets you acheive just about any level of automation that they require.

WET tests are defined using Test Definitions. These test definitions allow you to a define a WET test which closely follows the testing process.

Since WET uses Ruby, you can define resuable classes for your utilites which can be shared among various tests. If this were not enough, WET allows you to create <b>sharable library tests, Preconditions and Teardowns</b>. These preconditions and teardowns can be directly defined in the <b>WET test definition</b>.

WET allows runtime identification of objects using multiple parameters. This is required in web pages in which more than one object on the same page have similar attributes(in our experience 70odd% of web applications). This is one of the features that adds to WET's reliability in terms of test execution results.

WET has a very reliable mechanism to handle popups.

WET uses an XML based object depot (aka object repository/object map) for storing the application's object in a centralized location. The object depot allows all scripts in your test suite to share a common set of object definitions. This not only brings down the initial development time, but also increases the maintanability of scripts in a very big way.

WET has built in checkpoints to allow easy verification of a test's expected result with actual result

WET allows tests to be parametrized using either Microsoft Excel or a xml datatable to allow the same set of test steps to be performed against different set of data.

WET's built in result logging mechanism produces a pretty HTML results for all tests