"Yes/No" buttons aren't clear as to what is being answered
Bug #1492319 reported by
Nicholas Skaggs
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Checkbox Converged |
Fix Released
|
High
|
Maciej Kisielewski | ||
Ubuntu Community Testing |
Fix Released
|
High
|
Unassigned |
Bug Description
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.
Related branches
lp://qastaging/~kissiel/checkbox/fix-1492319-yes-no-rename
- Zygmunt Krynicki (community): Approve
-
Diff: 21 lines (+2/-2)1 file modifiedcheckbox-touch/components/TestVerificationPage.qml (+2/-2)
Changed in ubuntu-community-testing: | |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in checkbox-converged: | |
importance: | Undecided → High |
milestone: | none → 1.2.2 |
Changed in checkbox-converged: | |
milestone: | 1.2.2 → 1.2.3 |
Changed in checkbox-converged: | |
status: | Triaged → In Progress |
assignee: | nobody → Maciej Kisielewski (kissiel) |
Changed in checkbox-converged: | |
status: | In Progress → Fix Committed |
Changed in ubuntu-community-testing: | |
status: | Confirmed → Fix Committed |
Changed in ubuntu-community-testing: | |
status: | Fix Committed → Fix Released |
Changed in checkbox-converged: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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'?