suspend_advanced doesn't ask a clear yes/no answerable question

[François Tissandier]

Nothing critical, but for some tests, there is simply no question asked. I know it's quite obvious that "yes" means that it's working and "no" that there is a problem, but it could be improved.

Example of a test without a question : power management suspend and resume test. No question, and if it's not working, I'm asked to "mark this test as Failed". Failed is not an option. I just have "yes", "no", "skip".

So it's simply about improving the description and question. Or replacing the "yes" "no" by "successful" "failed" maybe.

[Brendan Donegan (brendan-donegan)]

Hi Francois,

This particular test description is fixed in trunk, and it's our intention to ensure all tests have clear descriptions for the next release. Thanks for pointing this out.

[Brendan Donegan (brendan-donegan)]

My own feeling is that by the time this test has been reached, the tester will know that 'Yes' entails the test worked and 'No' entails it didn't. Still for a cleaner user experience I recommend we update this description, so I've targeted it for the SRU.

[Daniel Manrique (roadmr)]

The test's description now includes a VERIFICATION section that asks "Did your system suspend and resume correctly?". The "mark this test as failed" part remains, and could potentially be amended to say "select `no` to indicate the test failed. I'll mark this Fix Committed and if more confusion arises we could review the text again.