The future of automated web testing is open source

Release Notes for 1.0.0


	License Download Prerequisites Install guide

Release Notes - WET - Version 1.0.0

Major revamp

The WET UI has undergone a major revamp in this release with the following two issues having been addressed:

[WET-308] - Disintegrate the WET UI
[WET-171] - Create the Browser DOM Wrapper directly from C#

The WET UI in 0.9.8 was a single MDI application in which all the features of WET UI was packed into! This was not only confusing but was also hiding the real strength of WET. The second big bottleneck in the WET UI was the RPC Server - Both these issues have been addressed.

To see a more detailed description about release 1.0 and the philosophy readjustment see the link at the Open QA Wiki
To get a brief overview about the new components in the disintegrated WET UI, see this Wiki Page

In the process of addressing these two issues, various other bugs were adressed!
WET-171 addressed many issues like [WET-261], [WET-263], [WET-270], [WET-291], [WET-292], [WET-318], etc.
As a process of implementing the fix for WET-308, the following issues were addressed: [WET-67], [WET-77], [WET-294], [WET-313], [WET-250], [WET-354], [WET-288], [WET-289]

Other New Features and Improvements

[WET-2] - Provide support for Form Submit - WET now has support to submit forms. This is typically required in those pages in which there is usually only a textfield but no button associated with it. In such cases, the user has to hit the enter key to continue navigation. Using WET, you can do this by calling the form_submit method on the input field
[WET-66] - Ability to access <span> and <div> elements. A new method container.element_by_tagname has been added due to which any html element can be accessed now in WET
[WET-232] - Allow more flexibility while using preconditions and teardowns - Starting from WET 1.0, any WET test can be used as a precondition. There is nothing special required. The only limitation (and this in fact is a design principle) is that only of the transaction in that test can be used.
[WET-361] - CSV datatable is now supported thereby letting openoffice users to harness the power of datatables
[WET-175] - WET UI recognizes wrong values for labels when adjacent items are other input elements. Wet is now smarter when it comes to identifying labels
[WET-253] - The results of executing batch files are now saved to a file whose name is similar to the batch file itself. Previously they were all getting saved to one single file - 'BatchResults.html' which was preventing multiple batches to be executed together
Support for Watir 1.5

Important bug fixes

[WET-180] - The check_dialog_exists() method is not working
[WET-183] - Escape new lines in test definition fields that are represented by textareas (eg. Description)
[WET-214] - In the object depot two elements were sometimes getting added with the same name
[WET-217] - When a xml RPC fails, it doesnot retry - Sometimes when an action failed due to temporary xml rpc issues, then the script was not getting generated. Now WET is more resliliant and retries for 3 times if xml rpc connections fail.
[WET-239], [WET-290] - Elements containing return character, backslash () & double quote (") are NOT properly prefixed with proper escape characters
[WET-242] - When we open an exisitng Test definition and click on New from the File menu,the save prompt is shown
[WET-243] - The name of the elements (or treenodes) in the ObjectStoreManager gets changed even when clicked on Cancel Button
[WET-245] - When we right click on wet tray icon and click on exit and when we click on No,the wet tray icon disappears from the system tray
[WET-248] - Can't get File Download Dialog to work with WET GEM 0.9.1.394
[WET-252] - On certain installations you get an error form (xmltreeview resize- null reference exception) and WET doesn't start

Issues fixed since 1.0

[WET-301] - With more than one parameter in parameterized object depot definitinon, processing is incorrect
[WET-305] - Default testdefintion generates parameter as 'iterations' . it should be testdata.iterations
[WET-307] - Excel to XML Parser is not included with the wet installer
[WET-339] - Installer should install batchrunner - Batchrunner was not seen in an obvious place in previous installers.

WET is a opensource automated web testing tool which uses Watir as the library to drive web pages. WET drives an IE Browser directly and so the automated testing done using WET is equivalent to how a user would drive the web pages. WET extends the scripting abilities of Watir and also offers the convenience of recorders. It is licensed under LGPL and BSD style open source licenses.