Results indicate failure but log does not indicate why. Manual tests should attach command output the same way automated tests do

Wouldn't this be the case if the tester marked the test as failed but didn't provide an notes? As the test itself says, "If your system fails to wake at all and must be rebooted, restart System Testing after reboot and mark this test as Failed."

Possibly... we may just need a process change in that case. Something along the lines of "If a test fails, add a note explaining the failure and the bug number opened"

IN the case of automated tests though, some sort of data should be logged for any result (pass or fail, IMO)

What's happening here is that the way things stand, manual tests don't attach the command output, only the content of the text field. My suggestion would be to change the behavior so that if the text field is empty then the command output is attached. Let me know if you agree with this, because the bug description will have to be changed (or maybe raise a new one). There's nothing wrong with the sleep state test specifically at the moment.

+1 as that removes the relying on the tester to remember/care enough to actually add some commentary to the failure.

Title changed accordingly.

Discussed at the Montreal sprint. We need a way to capture both the script output and any comments and then eventually munge those together for results submission.

Bumping to medium due to the dupe.

Since plainbox already does this I don't think we want to ever change checkbox-legacy anymore