|
|
|
[
Permlink
| « Hide
]
Raghu Venkataramana - 21/Apr/06 01:40 AM
It will be good to have this before 1.0
I recommend that we add ideas/suggestions to this issue
The following are the (some of the) requirements of such an UI: 1. A test definition should be easily definable using the objects. a) Appropriate input fields must be used for defininig components of the test (eg. Textfield for name, filefield for a repository), etc., b) When defining tests, the UI should be able to understand and replace 'predefined' variables - eg. You may have an environment variable pointing to the root directory of your application's tests. 2. The preconditions, transactions and teardowns should appear as components of the test - represented as links. When you expand these links, approriate definition UI should be shown. 3. It should be possible to display / edit the contents of each transaction script, precondition script / teardown script from the UI itself The UI application should have the abilitiy to define the items that are today defined in the global-configs
Should allow configuration of XML file that is used to 'fine tune' show_objects method.
Updating the first draft of the UI Proposal. This PDF file gives a detailed description of what is expected to be seen in the WET UI.
This is actually fixed. The WET UI has got most of the features that were initially thought of. However it needs a lot more work. All these should be wriiten up as separate issues.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||