[UX] Inconsistent user experience between providers and tests from the same provider
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Checkbox Converged |
Fix Released
|
High
|
Unassigned |
Bug Description
The UX of using checkbox touch is different depending on which provider you are using.
When you are using manual tests, in the verification page you will get:
Small buttons at the bottom for Yes No. To skip the test you have a button in the header.
In the QML tests, the verification part of it is not part of a "real" verification, but coded directly in the test itself.
This makes the experience inconsistent
Camera test:
Two big "Pass" "Fail" (instead of Yes/NO) and a small "Restart" button.
Haptics:
A small button to activate the haptics, and three big buttons this time, one for Pass, one for Fail, one for Skip
Edges:
Two big (but smaller) buttons to "Start" or "Skip the test" (instead of just Skip) to start the test.
In the verification, three big buttons (but again, smaller), this time with the labels "Yes", "No" and "Skip the test"
Virtual Keyboard:
Same as edges
Long press:
"Press and Hold" and two small buttos "Skip the test" "Fail the test"
Battery discharge:
A small button to Skip
Now that we have a relative small amount of tests, we should define the UX and make it consistent throughout the application.
summary: |
- [UX] Inconsistent user experience between providers + [UX] Inconsistent user experience between providers and tests |
summary: |
- [UX] Inconsistent user experience between providers and tests + [UX] Inconsistent user experience between providers and tests from the + same provider |
Changed in checkbox-touch: | |
status: | New → Confirmed |
Changed in checkbox-converged: | |
status: | Triaged → Fix Released |
The first step would be making all qml-native tests consistent.
Next, we should decide whether we want to let qml-native tests 'reuse' the verification screen of manual tests through some simple API. If not, we should define how the verification UI for the test should look like.