-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Labels
enhancementNew feature or requestNew feature or request
Description
When Assertions2.call(...) is used to verify that a test case does not throw an exception but actually does, the failure output is not informative. The current output looks like this:
org.opentest4j.AssertionFailedError: ...
context = {
}
Expected :null
Actual :null
This does not clearly convey the issue, making debugging harder.
Prposed changes:
Update the failure message to provide meaningful information:
- Expected: No exception thrown
- Actual: The actual exception that was thrown, including its type and message
Example of Desired Output
org.opentest4j.AssertionFailedError: ...
context = {
}
Expected : No exception thrown
Actual : java.lang.IllegalArgumentException: Invalid argument
This would make debugging easier by clearly indicating what went wrong.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request