| 2012-08-30 19:53:27 |
Daniel Manrique |
bug |
|
|
added bug |
| 2012-08-30 20:03:23 |
Daniel Manrique |
attachment added |
|
checkbox_0.14.5-amd64-20120830-1555 https://bugs.launchpad.net/ubuntu/+source/checkbox/+bug/1044037/+attachment/3284461/+files/checkbox_0.14.5-amd64-20120830-1555 |
|
| 2012-08-30 20:14:57 |
Daniel Manrique |
description |
The test screen, which is one of the most important in checkbox, was confusing to users we spoke to. A few changes are needed in how the controls are arranged:
- The test result buttons should be made into radiobuttons.
- The comments field should always be present, rather than requiring clicking on a button to reveal it. Users also complained that the field was confusing since it just appears out of nowhere.
- Keyboard shortcuts should be added to the controls, so that testing can be driven with the keyboard.
Since the bulk of these changes are UI related, I was confident I could get this in before UI Freeze, however it ended up requiring a few changes to the code, which need a Feature Freeze exception to be accepted.
This is the old test screen:
http://people.canonical.com/~roadmr/test-screen-bad.png
This is how the new screen looks like:
http://people.canonical.com/~roadmr/checkbox4.png |
The test screen, which is one of the most important in checkbox, was confusing to users we spoke to. A few changes are needed in how the controls are arranged:
- The test result buttons should be made into radiobuttons. The user should always have to select the test result from the radio buttons (Yes, No, Skip) and press Next to jump to the next test. Since some of the tests automatically select a radiobutton based on test outcome, the user experience is more consistent; with the old behavior, the test automatically highlights the yes or no buttons, leaving users wondering if they should press the highlighted button, or Next (which always skips and is thus badly named).
- The comments field should always be present, rather than requiring clicking on a button to reveal it. Users also complained that the field was confusing since it just appears out of nowhere.
- Keyboard shortcuts should be added to the controls, so that testing can be driven with the keyboard.
The benefit of these changes is to make the UI clearer and less quirky (highlighting buttons seems to be a bit unreliable in Qt), to encourage users to comment on test results by making the comments field visible at all times, and to make testing faster by returning the keyboard controls (these were present in the old GTK interface but hadn't been reimplemented in the Qt UI).
Since the bulk of these changes are UI related, I was confident I could get this in before UI Freeze, however it ended up requiring a few changes to the code, which need a Feature Freeze exception to be accepted.
This is the old test screen:
http://people.canonical.com/~roadmr/test-screen-bad.png
This is how the new screen looks like:
http://people.canonical.com/~roadmr/checkbox4.png
Note that a few strings changed: those for the Yes, No, Skip this Test, Previous and Next controls, mainly due to the addition of the marker (& in the case of Qt) for the keyboard shortcuts. |
|
| 2012-08-30 20:26:02 |
Daniel Manrique |
branch linked |
|
lp:~roadmr/ubuntu/quantal/checkbox/0.14.5 |
|
| 2012-08-30 20:26:39 |
Daniel Manrique |
bug |
|
|
added subscriber Ubuntu Release Team |
| 2012-08-31 20:03:57 |
Daniel Manrique |
summary |
[FFe] Controls in the test screen are confusing and should be rearranged. |
[FFe] [UIFe] Controls in the test screen are confusing and should be rearranged. |
|
| 2012-08-31 20:05:27 |
Daniel Manrique |
description |
The test screen, which is one of the most important in checkbox, was confusing to users we spoke to. A few changes are needed in how the controls are arranged:
- The test result buttons should be made into radiobuttons. The user should always have to select the test result from the radio buttons (Yes, No, Skip) and press Next to jump to the next test. Since some of the tests automatically select a radiobutton based on test outcome, the user experience is more consistent; with the old behavior, the test automatically highlights the yes or no buttons, leaving users wondering if they should press the highlighted button, or Next (which always skips and is thus badly named).
- The comments field should always be present, rather than requiring clicking on a button to reveal it. Users also complained that the field was confusing since it just appears out of nowhere.
- Keyboard shortcuts should be added to the controls, so that testing can be driven with the keyboard.
The benefit of these changes is to make the UI clearer and less quirky (highlighting buttons seems to be a bit unreliable in Qt), to encourage users to comment on test results by making the comments field visible at all times, and to make testing faster by returning the keyboard controls (these were present in the old GTK interface but hadn't been reimplemented in the Qt UI).
Since the bulk of these changes are UI related, I was confident I could get this in before UI Freeze, however it ended up requiring a few changes to the code, which need a Feature Freeze exception to be accepted.
This is the old test screen:
http://people.canonical.com/~roadmr/test-screen-bad.png
This is how the new screen looks like:
http://people.canonical.com/~roadmr/checkbox4.png
Note that a few strings changed: those for the Yes, No, Skip this Test, Previous and Next controls, mainly due to the addition of the marker (& in the case of Qt) for the keyboard shortcuts. |
The test screen, which is one of the most important in checkbox, was confusing to users we spoke to. A few changes are needed in how the controls are arranged:
- The test result buttons should be made into radiobuttons. The user should always have to select the test result from the radio buttons (Yes, No, Skip) and press Next to jump to the next test. Since some of the tests automatically select a radiobutton based on test outcome, the user experience is more consistent; with the old behavior, the test automatically highlights the yes or no buttons, leaving users wondering if they should press the highlighted button, or Next (which always skips and is thus badly named).
- The comments field should always be present, rather than requiring clicking on a button to reveal it. Users also complained that the field was confusing since it just appears out of nowhere.
- Keyboard shortcuts should be added to the controls, so that testing can be driven with the keyboard.
The benefit of these changes is to make the UI clearer and less quirky (highlighting buttons seems to be a bit unreliable in Qt), to encourage users to comment on test results by making the comments field visible at all times, and to make testing faster by returning the keyboard controls (these were present in the old GTK interface but hadn't been reimplemented in the Qt UI).
This is the old test screen:
http://people.canonical.com/~roadmr/test-screen-bad.png
This is how the new screen looks like:
http://people.canonical.com/~roadmr/checkbox4.png
Note that a few strings changed: those for the Yes, No, Skip this Test, Previous and Next controls, mainly due to the addition of the marker (& in the case of Qt) for the keyboard shortcuts. |
|
| 2012-09-03 20:21:06 |
Launchpad Janitor |
checkbox (Ubuntu): status |
New |
Confirmed |
|
| 2012-09-03 20:21:16 |
Ibrahim Saed |
bug |
|
|
added subscriber Ibrahim Saed |
| 2012-09-05 19:43:41 |
Steve Langasek |
checkbox (Ubuntu): status |
Confirmed |
New |
|
| 2012-09-10 08:30:43 |
Martin Pitt |
checkbox (Ubuntu): status |
New |
Triaged |
|
| 2012-09-10 08:39:06 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/checkbox |
|
| 2012-09-10 08:40:12 |
Launchpad Janitor |
checkbox (Ubuntu): status |
Triaged |
Fix Released |
|
| 2012-10-02 21:50:13 |
Carsten Gerlach |
tags |
|
ffe uife |
|
