Results indicate failure but log does not indicate why. Manual tests should attach command output the same way automated tests do
Bug #769144 reported by
Jeff Lane
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Checkbox (Legacy) |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Another one that appears to have failed, according to the results, but the logs do not give any clue as to why. Just opened this as a reminder that we should fix the test to provide better output.
Changed in checkbox: | |
importance: | Undecided → Low |
To post a comment you must log in.
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."