trivago / cluecumber

Clear and concise reporting for the Cucumber BDD JSON format.
https://www.softwaretester.blog
Apache License 2.0
268 stars 89 forks source link

Assumption message for Skipped scenario #299

Closed OxygeneIV closed 1 year ago

OxygeneIV commented 1 year ago

Hi, pretty new in the Cluecumber field...

I do get a Skipped scenario when using Assumptions and Failed scenario for Assertions, e.g:

Assumptions.assumeTrue(5 == 4, "Nothing available, stopping test");  => Skipped
Assertions.assertEquals(5 == 4, "Nothing available, stopping test");  => Failed

I do however not see the Assumption message for the skipped test which makes it hard to know the reason for Skipping. Since we do not want a failed (red) test in these situations, it would be nice in the UI to quickly see the "assume message" along the Scenario name, as it is now for Assertions.

Perhaps there is another way to display a message for Assumed-skipped tests without having to click on the Scenario link for further details.

/M

lunmag commented 1 year ago

V 2.9.4, using maven Note, tests with assume is defined as Aborted: image

bischoffdev commented 1 year ago

Hello, this is the Cluecumber project, not Cucumber. So I don't think this is the right place for your question.

bischoffdev commented 1 year ago

...or did I misunderstand it and you are talking about the reporting in this case? If so, please attach a minimal code example for your case.

OxygeneIV commented 1 year ago

Yes, the reporting:

Typical Java code: Assumptions.assumeTrue(5 == 4, "No V75 available, stopping test");

I'd like the Assume message to appear as for Assertions (at arrow position) image

bischoffdev commented 1 year ago

Can you attach a json file so I can check out if these messages are in there? Because if they are not, there is no way to display those.

lunmag commented 1 year ago

Had to rename due to extension validation...

cucumber.json.txt

bischoffdev commented 1 year ago

Perfect, thank you! Will investigate now.

bischoffdev commented 1 year ago

I can see the issue, fixing it now.

bischoffdev commented 1 year ago

image

Fixed, releasing it now for v3.0.1.

bischoffdev commented 1 year ago

Release done.