We need a specific test for "highest resolution"
Bug #1268576 reported by
Ara Pulido
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Checkbox |
Fix Released
|
High
|
Daniel Manrique | ||
Bug Description
Although we have a test that cycles through all identified resolutions, we don't have a specific test that checks specifically for the "highest resolution".
In our coverage document we specifically have "Highest resolution" under whitelist, so we need to add a specific test for it.
I don't think we have been missing any bug so far, but with discussions around High DPI we need to make sure we are testing that the monitor resolution is detected and shows without artifacts.
Related branches
lp:~roadmr/checkbox/1268576-highest-resolution-test
- Zygmunt Krynicki (community): Approve
-
Diff: 50 lines (+18/-0)3 files modifiedcheckbox-old/data/whitelists/client-cert.whitelist (+1/-0)
checkbox-old/data/whitelists/client-selftest.whitelist (+1/-0)
checkbox-old/jobs/graphics.txt.in (+16/-0)
| tags: | added: scripts |
| Changed in checkbox: | |
| importance: | Undecided → High |
| Changed in checkbox: | |
| assignee: | nobody → Daniel Manrique (roadmr) |
| status: | New → In Progress |
| Changed in checkbox: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
The cycle-resolutions test will provide testing of even the highest detected resolution, so a simple way of handling this would be to just have a test asking the user whether the highest resolution detected by xrandr is indeed the highest one supported by the GPU/screen combination.
Still it's not as simple, because again, it's using dynamic information. We can use the zenity hack. Well I guess figuring this out wil be the core of writing this test.