Make the window stacking tests a little less verbose
Bug #1123649 reported by
Sam Spilsbury
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Compiz |
Confirmed
|
Low
|
Sam Spilsbury | ||
Bug Description
Currently in our window stacking tests, there is a lot of verbose repetition of the following:
25 + ASSERT_TRUE (Advance (dpy, ct::WaitForEven
26 + DefaultRootWindow (dpy),
27 + PropertyNotify,
28 + -1,
29 + -1,
30 + matcher)));
That could better be expressed as something like:
CountdownStackE
| Changed in compiz: | |
| status: | New → Confirmed |
| assignee: | nobody → Sam Spilsbury (smspillaz) |
| importance: | Undecided → Low |
| milestone: | none → 0.9.9.2 |
Revision history for this message
| Brandon Schaefer (brandontschaefer) wrote | #1 |
| Changed in compiz: | |
| milestone: | 0.9.9.2 → 0.9.10.0 |
| Changed in compiz: | |
| milestone: | 0.9.10.0 → 0.9.10.2 |
| Changed in compiz: | |
| milestone: | 0.9.10.2 → 0.9.11.0 |
To post a comment you must log in.
Very true, I attempted this in my branch but it ended up just hanging...and never received the event. For me I had it pass the display and the matcher, though expanding this to number of events would work as well.