"Yes/No" buttons aren't clear as to what is being answered

[Nicholas Skaggs]

Basing on feedback on some of the early users, the buttons are confusing. It's not clear what yes/no is referring to. In a test context, I would expect something like pass/fail, not yes/no. Either way, the question is implied and not asked directly.

In addition, it's not clear what exactly we are asking. What does a 'NO' mean? I believe we want a NO (or really a fail or a better word) if for ANY reason, the tester cannot complete all the steps listed. We should tell them this is what we want.

[Brendan Donegan (brendan-donegan)]

This is a tricky one as it involves the conflict between the way tests are presented in Checkbox and the way they are presented in PractiTest. In Checkbox 'tests' take the form:

Prerequisites
Steps
Verification

Where verification is phrased as a question like?

'Did the system connect to the network'?

In PractiTest tests are written as 'Action - Expected Result' pairs.

One workaround would be to add a default 'question' at the end of every test like:

'Were the results of all steps as expected'?

[Zygmunt Krynicki (zyga)]

UX design, ack, change and land