|
If you were logged in you would be able to see more operations.
|
|
|
| Compatibility: |
backwards compatible
|
|
The TestCompound and Waitfor both skip actions when a condition fails/is not reached in a period of time. for both of these, it would help users if the reason for failure were included in an error message.
-the Condition interface could be extended with a ConditionWithCause interface that returned an explanation (and optionally, an exception?)
-the standard conditions could explain their failure, the web page condition would return the error code and failing page, etc.
-the not/and/or would return the nested causes with the relevant boolean logic operations applied.
The WaitFor and TestCompound components would include the reason when failing
|
|
Description
|
The TestCompound and Waitfor both skip actions when a condition fails/is not reached in a period of time. for both of these, it would help users if the reason for failure were included in an error message.
-the Condition interface could be extended with a ConditionWithCause interface that returned an explanation (and optionally, an exception?)
-the standard conditions could explain their failure, the web page condition would return the error code and failing page, etc.
-the not/and/or would return the nested causes with the relevant boolean logic operations applied.
The WaitFor and TestCompound components would include the reason when failing |
Show » |
|
Improvement
Resolved
Major
subclass Condition interface with one that provides a reason for a condition failing