Input tests should be expanded to include a clicking test
Bug #1229631 reported by
Ara Pulido
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Checkbox Provider - Base |
Fix Released
|
High
|
Po-Hsu Lin |
Bug Description
We currently have a local job called input/pointing
It takes the output of xinput to find pointing devices and creates pointing jobs for each of them.
We should have a second one (maybe called input/clicking) that uses the same output and creates tests that explicitly ask to test left, right and middle click (if available) for each of those.
Related branches
lp:~cypressyew/checkbox/input_click_jobs
- Zygmunt Krynicki (community): Approve
- Po-Hsu Lin: Needs Resubmitting
- Ara Pulido (community): Needs Fixing
-
Diff: 56 lines (+27/-0)3 files modifiedproviders/plainbox-provider-certification-client/whitelists/client-cert.whitelist (+2/-0)
providers/plainbox-provider-certification-client/whitelists/client-selftest.whitelist (+2/-0)
providers/plainbox-provider-checkbox/jobs/input.txt.in (+23/-0)
tags: | added: job |
affects: | checkbox → plainbox-provider-checkbox |
Changed in plainbox-provider-checkbox: | |
status: | Triaged → In Progress |
Changed in plainbox-provider-checkbox: | |
status: | In Progress → Fix Committed |
Changed in plainbox-provider-checkbox: | |
milestone: | none → 0.5 |
Changed in plainbox-provider-checkbox: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The existing test resides in checkbox- old/jobs/ input.txt. in. A simple version would just replicate this and replace "pointing" with "clicking", while asking the user to click on buttons and ensure an action results.
Bonus points for a test that updates touchpad_test to support specifying buttons. Currently you can specify scroll directions:
touchpad_test left right
touchpad_test up down
I'm thinking of a modification to allow things like this:
touchpad_test button_left button_middle button_right
the script uses Gtk/Gdk, so a bit of research on how to use these toolkits to capture mouse clicks will be needed.
But for the bug to be solved, a basic manual test would be enough.