You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the changes done by #1625 seem to have an unwanted effect: If a JUnit5 assumption outside of a given()/when()/then() stage is failing, this results in a scenario case with "status": "SUCCESS" in the JSON report and no indication of a skipped test or exception is visible.
Therefore in the HTML report the test scenario is shown as successful and the steps are not completely visible (because the test run stops at the assumption exception).
I would expect that in this case the test result would be "ABORTED" as well (and errorMessage and stackTrace should be recorded).
The text was updated successfully, but these errors were encountered:
Hi, sorry for reacting rather late, missed you in my email feed.
Could you clarify a bit what you mean to make analysis eaiser for me?
So did you place the assumption in a scenario / Junit5 before method or elsewhere?
Hi,
the changes done by #1625 seem to have an unwanted effect: If a JUnit5 assumption outside of a given()/when()/then() stage is failing, this results in a scenario case with
"status": "SUCCESS"
in the JSON report and no indication of a skipped test or exception is visible.Therefore in the HTML report the test scenario is shown as successful and the steps are not completely visible (because the test run stops at the assumption exception).
I would expect that in this case the test result would be "ABORTED" as well (and
errorMessage
andstackTrace
should be recorded).The text was updated successfully, but these errors were encountered: