Details
-
Type:
Improvement
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.1
-
Fix Version/s: 2.2
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
Somewhere deep down in the runScenario logic, you could benefit from a try/catch(Throwable)/wrap-rethrow
The wrapping exception could add textual information on the step that is failing. Catch throwable because you're not just catching AssertionErrors, you're catching Selenium timeouts.
Activity

Field | Original Value | New Value |
---|---|---|
Summary | Can JUnit 3, 4, TestNG test-runners decorate Exceptions a bit more clearly ? | Unit-test runners should decorate Exceptions a bit more clearly |
Fix Version/s | 2.2 [ 14670 ] |

Attachment | step_in_exception.txt [ 39202 ] |

Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Paul - can you please provide an example or a patch detailing what you mean by "a bit more clearly"?