This is the home page for the WET Web Testing Project. You will find useful information / titbits about the WET project here. Please add information, comments / tips to the Wiki if you find something that is not there already
|Work in progress|
Being a wiki, this is always a 'Work in progress' site. You will find many links that dont work yet. This page is almost like the contents page of a book. As and when we realize that there are sections / articles that need to be added to the Wiki, we just add a link to this page in the appropriate section. The 'hyperlinked' page may not exist at the time of adding. It will be put on a later day.
If you navigate to a link and find that the page has not been created or does not have enough information and you happen to know about that topic, please help the community of testers by adding the required information there.
|Feature works for 1.0 only|
In various places you will find the icon . This means that the said feature is not applicable for WET versions less than 1.0
As on 18th May 2007, we are working feverishly towards releasing the alpha version(we hope that it will be released on 20th May). If you dont find the installer for 1.0 yet then please check back after a couple days
This section contains more information and links for using WET to automate your web applications. WET has two layers:
- WET Core Layer - The core layer is responsible for handling the actual task of automating web applications. The WET Core Layer comprises of a set of APIs which control a remote browser. This layer is like the 'heart' of WET. The core layer is written in ruby.
- WET UI Layer - A UI layer which assists in easy creation of WET scripts, this has been developed using C#.
All Web applications are not created equal. WET has some nifty configuration parameters that lets you configure it to produce better results with your application under test. These are captured in this section.
- Customizing the attributes used for object identification - In the WET UI, you must have observed that WET automatically uses a different set of attributes to identify different objects. For example, when a 'Link' is encountered, the link's text is used as the primary identifier; When a textfield is encountered, the textfield's label is used as the primary identifier and so on. On what basis does WET assume as to which element can be identified by what attributes? Well, it actually doesn't assume but picks it up from an xml configuration file. You can modify this xml configuration file to better suit your application under test.
This is the place where you can find information for developing WET. If you are interested in contributing to the WET code, help in bug fixes or creating extensions using WET, this is the right place for you.
Before starting, make sure that you are subscribed to the WET developer's forum where you can find information w.r.t. developing WET. The wet developer forum is at: Developer forum