The description should retain $output information when being reported

[Marc Tardif]

Hello,

According to my experience, output is captured for both manual and shell plugin since it's possible to use the $output syntax in the description. However, it seems it's only logged for the shell plugin.

Currently, I'm working on some test cases that, after gathering certain information, show it to the user and ask something such as "Is this correct?". Since from time to time a human error or a change in the pass criteria could happen, I think it would be nice to have the output of those commands in the report so that when reviewing old results it could be found what was the information that was supplied to the tester to decide the test result.

Do you agree on this?

Best regards,
    Javier

[Daniel Manrique (roadmr)]

Javier,

This bug just turned 2 years old, so as a birthday present I'd like to close it, but I'd like to get your confirmation on whether this feature is already implemented in recent Checkbox versions. I seem to remember that all the text we capture in the comments box gets added to the report but I'd prefer you to confirm if it works the way you want now.

Thanks for your time.

[Javier Collado (javier.collado)]

@Daniel

This problem is still present.

[Brendan Donegan (brendan-donegan)]

This really can't be high priority if it's been open for 3 years. I'll change to medium

[Jeff Lane  (bladernr)]

Agreed with Last Year Brendan... but even more so, demoting it to Low... we only have 3 jobs that use this feature, in total, none of which are part of certification. I'm actually inclined to call this a wont-fix, but perhaps it's worth looking at at some point.