Aleix Pol a3d32fa836 Ensure we start our tests with wayland already initialised ... When debugging modifier_only_shortcut_test in _waylandonly mode I saw that it was failing, among other things, because some aspects were not initialised. This changes every test we have to run the new Test::initWaylandWorkspace() that calls waylandServer()->initWorkspace() but also makes sure that WaylandServer::initialized is emitted before we proceed.		2021-05-10 12:33:43 +00:00
..
scripts
CMakeLists.txt
desktop_switching_animation_test.cpp	Ensure we start our tests with wayland already initialised	2021-05-10 12:33:43 +00:00
maximize_animation_test.cpp	Ensure we start our tests with wayland already initialised	2021-05-10 12:33:43 +00:00
minimize_animation_test.cpp	Ensure we start our tests with wayland already initialised	2021-05-10 12:33:43 +00:00
popup_open_close_animation_test.cpp	Ensure we start our tests with wayland already initialised	2021-05-10 12:33:43 +00:00
scripted_effects_test.cpp
slidingpopups_test.cpp
toplevel_open_close_animation_test.cpp	Ensure we start our tests with wayland already initialised	2021-05-10 12:33:43 +00:00
translucency_test.cpp
windowgeometry_test.cpp
wobbly_shade_test.cpp