History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: WET-308
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: Unassigned
Reporter: Raghu Venkataramana
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
WET

Disintegrate the WET UI

Created: 23/Jan/07 03:19 AM   Updated: 18/Apr/07 11:13 PM
Component/s: Script Assistant
Affects Version/s: 0.9.8 Final, 0.9.8_Patch
Fix Version/s: 1.0.0

Issue Links:
Dependency
 
This issue is depended on by:
WET-256 When path for certain test definition... Major Closed
WET-262 Context Menu is not shown for element... Major Closed
WET-289 Results path is overwritten by the WE... Major Closed
WET-250 Provide a mechanism for the test defi... Major Closed


 Description  « Hide
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.



 All   Comments   Change History      Sort Order:
Raghu Venkataramana - 23/Jan/07 03:23 AM
Please comment / vote on this issue. This is a very important issue and will make a big difference to the 1.0 release.

Raghu Venkataramana - 23/Jan/07 03:39 AM
If we decide to go with WET-308, then there will be no need to fix this at all.

Raghu Venkataramana - 23/Jan/07 03:51 AM
No need to fix this issue if WET-308 is implemented

Raghu Venkataramana - 23/Jan/07 03:52 AM
This issue's significance comes down remarkably if WET-308 is implemented.

Raghu Venkataramana - 23/Jan/07 03:56 AM
Implementing WET-308 would mean that this problem automatically gets fixed.

Ian - 23/Jan/07 04:25 AM
I think this would be useful. I currently use the UI to identify objects and to get the correct syntax for statements. (docs are still not very useful so I use this instead). I don't use the UI to write my tests, I copy/paste the generated code into another editor.

Raghu Venkataramana - 23/Mar/07 03:37 AM
This one is almost done. (1), (2) and (3) have been completed. What still needs to be done is that that a separate application needs to be created for the simulated Browser. Saraswathi Bhat is currently working on that. Once that is completed, the simulated Browser's action must be transfered to a script.

Raghu Venkataramana - 02/Apr/07 10:10 PM
The disintegration of the simulated browser itself is completed. But before moving to the 'transfer the actions to a script' part, Browser DOM wrapper in C# must be completed.

Raghu Venkataramana - 18/Apr/07 11:13 PM
The disintegration part itself has been completed. There are various issues in the 'discrete' components itself but those have to be addressed separately