
| Key: |
WET-55
|
| Type: |
New Feature
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Raghu Venkataramana
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
WET
Created: 17/May/06 08:00 AM
Updated: 18/Jun/07 10:11 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
1.4
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
Currently we have a batch runner in WET. But this is limited in its functionality and can only run a set of test definitions in a sequence. What we actually need is a more dedicted test suite runner through which complex interactions between tests can be defined.
For example:, you may want to say that Test1 should only be run if Test5 has passed or Test6 is to be run if Test1 fails and so on.
I am logging this issue here as a place to keep a track of all the requirements for such a suite runner. Please post your ideas/ suggestions here as either comments or sub tasks
|
|
Description
|
Currently we have a batch runner in WET. But this is limited in its functionality and can only run a set of test definitions in a sequence. What we actually need is a more dedicted test suite runner through which complex interactions between tests can be defined.
For example:, you may want to say that Test1 should only be run if Test5 has passed or Test6 is to be run if Test1 fails and so on.
I am logging this issue here as a place to keep a track of all the requirements for such a suite runner. Please post your ideas/ suggestions here as either comments or sub tasks |
Show » |
| There are no comments yet on this issue.
|
|