The WET UI undoubtedly offers a lot of 'ease' of use but seems to hide the inherent strengths of WET. Due to the new UI, it appears as though the power of WET is limited to what is seen in the WET UI. This is far from the truth. The truth is that the real power of WET lies in its core layer.

While it is essential to bring down the learning curve for WET, it is also (if not more) essential to give experts a more 'usable' interface. For example, spying objects and creating the object depot using the wet ui makes a life lot easier but at the same time, some of the issues with the WET UI(slow to use, RPC issues) makes it a drag. To counter this, I propose the following:

1) Have a separate application for creating and editing test defintions
2) Have a separate application for viewing browsers in a treeview. Using this, one should be able to add objects to the object depot and do some basic editing
3) Have a separate object depot editor (opensource the xml repository manager)

To bring down the learning curve for the novice user:
The current wet script assistant should be able to perform minimal operations only:
a) Testdefintion created using the wet UI will have all its paths set to some predetermined value
b) Preconditions/teardowns will not be shown in the wet ui at all.
c) Like wise transaction details will not be shown - when you add transactions, only the name of these transactions can be edited.
d) Object depot cannot be edited or even viewed. This will automatically be created.
e) Only test definiton will be saved.