kwin/autotests/wayland
Martin Gräßlin 5200a484ce [autotest] Adjust LockScreenTest to fix that KSldApp goes to Locked state
So far KSldApp was always either in state AcquiringLock or Unlocked
during the tests. Due to a fix in WaylandServer it now can also enter
the Locked state. But this is timing related and also depends on whether
the greeter works at all. E.g. on build.kde.org the greeter fails to
start, so it never enters the Locked state.

The adjusted test now considers that the state might have changed to
Locked and expects one additional signal to be emitted.
2016-02-17 09:41:17 +01:00
..
CMakeLists.txt
decoration_input_test.cpp
dont_crash_glxgears.cpp
input_stacking_order.cpp
internal_window.cpp
kwin_wayland_test.cpp
kwin_wayland_test.h
lockscreen.cpp
move_resize_window_test.cpp Fix typo 2016-02-11 09:34:19 +01:00
pointer_input.cpp
quick_tiling_test.cpp
start_test.cpp
touch_input_test.cpp
transient_no_input_test.cpp