yukijoou/kwin
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
kwin/autotests/integration/CMakeLists.txt

176 lines
9.6 KiB
Text
Raw Normal View History

Support for syncing the clipboard from X11 to Wayland and vice versa Summary: The clipboard sync is done by a dedicated helper binary launched by KWin. This helper binary is forced to xcb platform to piggy-back on Qt's implementation of the X11 clipboard. In addition it implements the Wayland clipboard - which is much simpler. Reading the Wayland clipboard is based on the implementation in QtWayland. KWin internally knows the DataDeviceInterface belonging to the helper application. Whenever an xwayland client is focussed, this DataDevice is allowed to set the selection and KWin manually updates the current selection in the SeatInterface. By that the sync from X11 to Wayland is implemented. When afterwards a Wayland client is selected, it's sent the current selection which references the X clipboard and a data transfer can be initiated in the normal Wayland way. For the other direction KWin sends the current selection to the helper's DataDevice whenever an xwayland window is focused. The helper application reads the Wayland clipboard and sets it on the X11 clipboard. Thus the Wayland clipboard is synced to X11. The approach used here will also be useful for implementing a clipboard manager (aka klipper). Currently the implementation is not yet fully completed. We need to make sure that the helper application gets restarted in case of a crash. Test Plan: See added test case Reviewers: #plasma_on_wayland, #kwin Subscribers: plasma-devel, kwin Tags: #plasma_on_wayland, #kwin Differential Revision: https://phabricator.kde.org/D1973
2016-06-20 09:21:16 +00:00
add_subdirectory(helper)
[wayland] Honor ShellSurfaceInterface::acceptsKeyboardFocus in ::wantsInput If the surface indicates that it doesn't want keyboard focus we shouldn't give it keyboard focus. This was a problem with Kate's autocompletion tool tip windows. REVIEW: 125553
2015-10-07 17:06:34 +00:00
Adapt build system to also support building against Qt6
2022-03-10 18:11:26 +00:00
add_library(KWinIntegrationTestFramework SHARED)
if (QT_MAJOR_VERSION EQUAL "5")
autotests: Port KWinFrameworkIntegration from source vars to target based apis
2022-04-22 10:38:30 +00:00
ecm_add_qtwayland_client_protocol(KWinIntegrationTestFramework
Adapt build system to also support building against Qt6
2022-03-10 18:11:26 +00:00
PROTOCOL ${WaylandProtocols_DATADIR}/unstable/input-method/input-method-unstable-v1.xml
BASENAME input-method-unstable-v1
)
autotests: Port KWinFrameworkIntegration from source vars to target based apis
2022-04-22 10:38:30 +00:00
ecm_add_qtwayland_client_protocol(KWinIntegrationTestFramework
Adapt build system to also support building against Qt6
2022-03-10 18:11:26 +00:00
PROTOCOL ${WaylandProtocols_DATADIR}/unstable/text-input/text-input-unstable-v3.xml
BASENAME text-input-unstable-v3
)
autotests: Port KWinFrameworkIntegration from source vars to target based apis
2022-04-22 10:38:30 +00:00
ecm_add_qtwayland_client_protocol(KWinIntegrationTestFramework
Adapt build system to also support building against Qt6
2022-03-10 18:11:26 +00:00
PROTOCOL protocols/wlr-layer-shell-unstable-v1.xml
BASENAME wlr-layer-shell-unstable-v1
)
autotests: Port KWinFrameworkIntegration from source vars to target based apis
2022-04-22 10:38:30 +00:00
ecm_add_qtwayland_client_protocol(KWinIntegrationTestFramework
Adapt build system to also support building against Qt6
2022-03-10 18:11:26 +00:00
PROTOCOL ${WaylandProtocols_DATADIR}/stable/xdg-shell/xdg-shell.xml
BASENAME xdg-shell
)
autotests: Port KWinFrameworkIntegration from source vars to target based apis
2022-04-22 10:38:30 +00:00
ecm_add_qtwayland_client_protocol(KWinIntegrationTestFramework
Adapt build system to also support building against Qt6
2022-03-10 18:11:26 +00:00
PROTOCOL ${WaylandProtocols_DATADIR}/unstable/xdg-decoration/xdg-decoration-unstable-v1.xml
BASENAME xdg-decoration-unstable-v1
)
autotests: Port KWinFrameworkIntegration from source vars to target based apis
2022-04-22 10:38:30 +00:00
ecm_add_qtwayland_client_protocol(KWinIntegrationTestFramework
Adapt build system to also support building against Qt6
2022-03-10 18:11:26 +00:00
PROTOCOL ${WaylandProtocols_DATADIR}/unstable/idle-inhibit/idle-inhibit-unstable-v1.xml
BASENAME idle-inhibit-unstable-v1
)
autotests: Port KWinFrameworkIntegration from source vars to target based apis
2022-04-22 10:38:30 +00:00
ecm_add_qtwayland_client_protocol(KWinIntegrationTestFramework
Adapt build system to also support building against Qt6
2022-03-10 18:11:26 +00:00
PROTOCOL ${PLASMA_WAYLAND_PROTOCOLS_DIR}/kde-output-device-v2.xml
BASENAME kde-output-device-v2
)
autotests: Port KWinFrameworkIntegration from source vars to target based apis
2022-04-22 10:38:30 +00:00
ecm_add_qtwayland_client_protocol(KWinIntegrationTestFramework
Adapt build system to also support building against Qt6
2022-03-10 18:11:26 +00:00
PROTOCOL ${PLASMA_WAYLAND_PROTOCOLS_DIR}/kde-output-management-v2.xml
BASENAME kde-output-management-v2
)
else()
Fix some tests not building with Qt 6 Client-side wrappers for input-method-unstable-v1 fail to build because wl_keyboard_interface is referenced in the header file generated by wayland-scanner. Unfortunately, qt6_generate_wayland_protocol_client_sources() forces --include-core-only argument, this is addressed in Qt 6.4.1, but in meanwhile let's ship a copy of Qt6WaylandClientMacros.cmake file until the required Qt version is out.
2022-10-19 14:12:02 +00:00
qt6_generate_wayland_protocol_client_sources(KWinIntegrationTestFramework
NO_INCLUDE_CORE_ONLY
FILES
${WaylandProtocols_DATADIR}/unstable/input-method/input-method-unstable-v1.xml
)
qt6_generate_wayland_protocol_client_sources(KWinIntegrationTestFramework
FILES
${WaylandProtocols_DATADIR}/unstable/text-input/text-input-unstable-v3.xml
${CMAKE_CURRENT_SOURCE_DIR}/protocols/wlr-layer-shell-unstable-v1.xml
${WaylandProtocols_DATADIR}/stable/xdg-shell/xdg-shell.xml
${WaylandProtocols_DATADIR}/unstable/xdg-decoration/xdg-decoration-unstable-v1.xml
${WaylandProtocols_DATADIR}/unstable/idle-inhibit/idle-inhibit-unstable-v1.xml
${PLASMA_WAYLAND_PROTOCOLS_DIR}/kde-output-device-v2.xml
${PLASMA_WAYLAND_PROTOCOLS_DIR}/kde-output-management-v2.xml
Adapt build system to also support building against Qt6
2022-03-10 18:11:26 +00:00
)
endif()
Port autotests/integration/outputmanagement_test to kde_output_management_v2
2021-09-08 09:04:44 +00:00
autotests: Port KWinFrameworkIntegration from source vars to target based apis
2022-04-22 10:38:30 +00:00
target_sources(KWinIntegrationTestFramework PRIVATE
../../src/cursor.cpp
generic_scene_opengl_test.cpp
kwin_wayland_test.cpp
test_helpers.cpp
)
wayland: Link statically KGlobalAccel integration plugin Without the KGlobalAccel integration plugin, Wayland experience will be negatively affected. Therefore it makes little sense to load it at run- time.
2020-11-21 10:16:59 +00:00
target_link_libraries(KWinIntegrationTestFramework
autotests: Use a shared library for the integration test framework Ever since the effects were changed to static, each test of the integration tests includes all the effects. The result of this is that when doing a debug build each test is now 60MiB or more. With the amount of tests, this results in ~8 GiB of diskspace used just for KWin's binary output directory, which is rather excessive. Since the tests all share a common framework library, we can change that library to a shared library and that way avoid linking all the effects into each test. Most of this is shuffling around some link libraries in the integration test CMakeLists, however, I needed to export the Xwayland class as it is used by one of the tests but wasn't exported.
2021-11-29 13:47:16 +00:00
PUBLIC
Qt::Test
KF5::WaylandClient
Wayland::Client
kwin
wayland: Link statically KGlobalAccel integration plugin Without the KGlobalAccel integration plugin, Wayland experience will be negatively affected. Therefore it makes little sense to load it at run- time.
2020-11-21 10:16:59 +00:00
autotests: Use a shared library for the integration test framework Ever since the effects were changed to static, each test of the integration tests includes all the effects. The result of this is that when doing a debug build each test is now 60MiB or more. With the amount of tests, this results in ~8 GiB of diskspace used just for KWin's binary output directory, which is rather excessive. Since the tests all share a common framework library, we can change that library to a shared library and that way avoid linking all the effects into each test. Most of this is shuffling around some link libraries in the integration test CMakeLists, however, I needed to export the Xwayland class as it is used by one of the tests but wasn't exported.
2021-11-29 13:47:16 +00:00
PRIVATE
# Own libraries
KWinXwaylandServerModule
Move source code to src/ directory Once in a while, we receive complaints from other fellow KDE developers about the file organization of kwin. This change addresses some of those complaints by moving all of source code in a separate directory, src/, thus making the project structure more traditional. Things such as tests are kept in their own toplevel directories. This change may wreak havoc on merge requests that add new files to kwin, but if a patch modifies an already existing file, git should be smart enough to figure out that the file has been relocated. We may potentially split the src/ directory further to make navigating the source code easier, but hopefully this is good enough already.
2021-02-09 19:31:40 +00:00
autotests: Use a shared library for the integration test framework Ever since the effects were changed to static, each test of the integration tests includes all the effects. The result of this is that when doing a debug build each test is now 60MiB or more. With the amount of tests, this results in ~8 GiB of diskspace used just for KWin's binary output directory, which is rather excessive. Since the tests all share a common framework library, we can change that library to a shared library and that way avoid linking all the effects into each test. Most of this is shuffling around some link libraries in the integration test CMakeLists, however, I needed to export the Xwayland class as it is used by one of the tests but wasn't exported.
2021-11-29 13:47:16 +00:00
# Static plugins
KWinQpaPlugin
KF5GlobalAccelKWinPlugin
KF5WindowSystemKWinPlugin
KF5IdleTimeKWinPlugin
wayland: Link statically KGlobalAccel integration plugin Without the KGlobalAccel integration plugin, Wayland experience will be negatively affected. Therefore it makes little sense to load it at run- time.
2020-11-21 10:16:59 +00:00
)
Fix builtin effects not loading The api of kcoreaddons_target_static_plugins() has changed so static plugins must be linked with kwin_x11 and kwin_wayland directly.
2022-02-05 23:28:48 +00:00
kcoreaddons_target_static_plugins(KWinIntegrationTestFramework "kwin/effects/plugins" LINK_OPTION "PRIVATE")
autotests: Use a shared library for the integration test framework Ever since the effects were changed to static, each test of the integration tests includes all the effects. The result of this is that when doing a debug build each test is now 60MiB or more. With the amount of tests, this results in ~8 GiB of diskspace used just for KWin's binary output directory, which is rather excessive. Since the tests all share a common framework library, we can change that library to a shared library and that way avoid linking all the effects into each test. Most of this is shuffling around some link libraries in the integration test CMakeLists, however, I needed to export the Xwayland class as it is used by one of the tests but wasn't exported.
2021-11-29 13:47:16 +00:00
set_target_properties(KWinIntegrationTestFramework PROPERTIES CXX_VISIBILITY_PRESET default)
[autotests/integration] Simplify the cmake for creating a test Summary: A dedicated cmake function is added to create a test case. It takes a NAME, the SRCS and additional LIBS. Thus it's integrationTest(NAME myTestCase SRCS test.cpp) to create a standard integration test. In addition kwin_wayland_test.cpp is compiled into a static library to decrease the compile time a little bit. Reviewers: #kwin, #plasma_on_wayland Subscribers: plasma-devel, kwin Tags: #plasma_on_wayland, #kwin Differential Revision: https://phabricator.kde.org/D2052
2016-06-30 06:37:50 +00:00
function(integrationTest)
[autotests] Support Wayland Only in addition to XWayland The integrationTest function takes a new optional argument whether the test supports a Wayland Only mode. If that's the case the test is compiled twice, once (as always) as "foo" with XWayland support and once as "foo_waylandonly" without XWayland support. This way we can ensure that our code always supports both modes. The tests found multiple issues. At the moment fast running tests are sporadically crashing on tear down. This needs further investigation.
2017-09-30 14:35:52 +00:00
set(optionArgs WAYLAND_ONLY)
[autotests/integration] Simplify the cmake for creating a test Summary: A dedicated cmake function is added to create a test case. It takes a NAME, the SRCS and additional LIBS. Thus it's integrationTest(NAME myTestCase SRCS test.cpp) to create a standard integration test. In addition kwin_wayland_test.cpp is compiled into a static library to decrease the compile time a little bit. Reviewers: #kwin, #plasma_on_wayland Subscribers: plasma-devel, kwin Tags: #plasma_on_wayland, #kwin Differential Revision: https://phabricator.kde.org/D2052
2016-06-30 06:37:50 +00:00
set(oneValueArgs NAME)
set(multiValueArgs SRCS LIBS)
[autotests] Support Wayland Only in addition to XWayland The integrationTest function takes a new optional argument whether the test supports a Wayland Only mode. If that's the case the test is compiled twice, once (as always) as "foo" with XWayland support and once as "foo_waylandonly" without XWayland support. This way we can ensure that our code always supports both modes. The tests found multiple issues. At the moment fast running tests are sporadically crashing on tear down. This needs further investigation.
2017-09-30 14:35:52 +00:00
cmake_parse_arguments(ARGS "${optionArgs}" "${oneValueArgs}" "${multiValueArgs}" ${ARGN})
[autotests/integration] Simplify the cmake for creating a test Summary: A dedicated cmake function is added to create a test case. It takes a NAME, the SRCS and additional LIBS. Thus it's integrationTest(NAME myTestCase SRCS test.cpp) to create a standard integration test. In addition kwin_wayland_test.cpp is compiled into a static library to decrease the compile time a little bit. Reviewers: #kwin, #plasma_on_wayland Subscribers: plasma-devel, kwin Tags: #plasma_on_wayland, #kwin Differential Revision: https://phabricator.kde.org/D2052
2016-06-30 06:37:50 +00:00
add_executable(${ARGS_NAME} ${ARGS_SRCS})
autotests: Use a shared library for the integration test framework Ever since the effects were changed to static, each test of the integration tests includes all the effects. The result of this is that when doing a debug build each test is now 60MiB or more. With the amount of tests, this results in ~8 GiB of diskspace used just for KWin's binary output directory, which is rather excessive. Since the tests all share a common framework library, we can change that library to a shared library and that way avoid linking all the effects into each test. Most of this is shuffling around some link libraries in the integration test CMakeLists, however, I needed to export the Xwayland class as it is used by one of the tests but wasn't exported.
2021-11-29 13:47:16 +00:00
target_link_libraries(${ARGS_NAME} KWinIntegrationTestFramework Qt::Test ${ARGS_LIBS})
[autotests] Support new way to run the tests without need to install Summary: KWin was quite good in ensuring that you don't need to install by passing paths to the tests. The new way is much nicer, so code is adjusted for the new way. Also if we require a newer ECM in future we need to support the new way. No guarantee that the tests don't pick something up from the system env, that needs more testing. References: https://community.kde.org/Guidelines_and_HOWTOs/Making_apps_run_uninstalled Test Plan: The tests which loaded helpers pass Reviewers: #kwin, #plasma Subscribers: plasma-devel, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D7543
2017-08-25 16:18:20 +00:00
add_test(NAME kwin-${ARGS_NAME} COMMAND dbus-run-session ${CMAKE_BINARY_DIR}/bin/${ARGS_NAME})
[autotests] Support Wayland Only in addition to XWayland The integrationTest function takes a new optional argument whether the test supports a Wayland Only mode. If that's the case the test is compiled twice, once (as always) as "foo" with XWayland support and once as "foo_waylandonly" without XWayland support. This way we can ensure that our code always supports both modes. The tests found multiple issues. At the moment fast running tests are sporadically crashing on tear down. This needs further investigation.
2017-09-30 14:35:52 +00:00
if (${ARGS_WAYLAND_ONLY})
Fix size restore upon keyboard close in XdgSurfaceClient in XdgSurfaceClient setFrameGeometry is async, so we can't rely on it having the final value immediately. make setVirtualKeyboardGeometry a virtual. in the implementation on setVirtualKeyboardGeometry use requestedFrameGeometry() instead of frameGeometry()
2020-09-01 08:58:46 +00:00
add_executable(${ARGS_NAME}_waylandonly ${ARGS_SRCS} )
[autotests] Support Wayland Only in addition to XWayland The integrationTest function takes a new optional argument whether the test supports a Wayland Only mode. If that's the case the test is compiled twice, once (as always) as "foo" with XWayland support and once as "foo_waylandonly" without XWayland support. This way we can ensure that our code always supports both modes. The tests found multiple issues. At the moment fast running tests are sporadically crashing on tear down. This needs further investigation.
2017-09-30 14:35:52 +00:00
set_target_properties(${ARGS_NAME}_waylandonly PROPERTIES COMPILE_DEFINITIONS "NO_XWAYLAND")
autotests: Use a shared library for the integration test framework Ever since the effects were changed to static, each test of the integration tests includes all the effects. The result of this is that when doing a debug build each test is now 60MiB or more. With the amount of tests, this results in ~8 GiB of diskspace used just for KWin's binary output directory, which is rather excessive. Since the tests all share a common framework library, we can change that library to a shared library and that way avoid linking all the effects into each test. Most of this is shuffling around some link libraries in the integration test CMakeLists, however, I needed to export the Xwayland class as it is used by one of the tests but wasn't exported.
2021-11-29 13:47:16 +00:00
target_link_libraries(${ARGS_NAME}_waylandonly KWinIntegrationTestFramework Qt::Test ${ARGS_LIBS})
[autotests] Support new way to run the tests without need to install Summary: KWin was quite good in ensuring that you don't need to install by passing paths to the tests. The new way is much nicer, so code is adjusted for the new way. Also if we require a newer ECM in future we need to support the new way. No guarantee that the tests don't pick something up from the system env, that needs more testing. References: https://community.kde.org/Guidelines_and_HOWTOs/Making_apps_run_uninstalled Test Plan: The tests which loaded helpers pass Reviewers: #kwin, #plasma Subscribers: plasma-devel, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D7543
2017-08-25 16:18:20 +00:00
add_test(NAME kwin-${ARGS_NAME}-waylandonly COMMAND dbus-run-session ${CMAKE_BINARY_DIR}/bin/${ARGS_NAME}_waylandonly)
[autotests] Support Wayland Only in addition to XWayland The integrationTest function takes a new optional argument whether the test supports a Wayland Only mode. If that's the case the test is compiled twice, once (as always) as "foo" with XWayland support and once as "foo_waylandonly" without XWayland support. This way we can ensure that our code always supports both modes. The tests found multiple issues. At the moment fast running tests are sporadically crashing on tear down. This needs further investigation.
2017-09-30 14:35:52 +00:00
endif()
[autotests/integration] Simplify the cmake for creating a test Summary: A dedicated cmake function is added to create a test case. It takes a NAME, the SRCS and additional LIBS. Thus it's integrationTest(NAME myTestCase SRCS test.cpp) to create a standard integration test. In addition kwin_wayland_test.cpp is compiled into a static library to decrease the compile time a little bit. Reviewers: #kwin, #plasma_on_wayland Subscribers: plasma-devel, kwin Tags: #plasma_on_wayland, #kwin Differential Revision: https://phabricator.kde.org/D2052
2016-06-30 06:37:50 +00:00
endfunction()
integrationTest(NAME testDontCrashGlxgears SRCS dont_crash_glxgears.cpp)
Add KWIN_BUILD_SCREENLOCKER option Allows to build KWin without lockscreen support and thus drops the kscreenlocker dependency. Signed-off-by: Eike Hein <eike.hein@mbition.io>
2022-02-23 13:27:05 +00:00
if (KWIN_BUILD_SCREENLOCKER)
integrationTest(NAME testLockScreen SRCS lockscreen.cpp)
endif()
[autotests] Support Wayland Only in addition to XWayland The integrationTest function takes a new optional argument whether the test supports a Wayland Only mode. If that's the case the test is compiled twice, once (as always) as "foo" with XWayland support and once as "foo_waylandonly" without XWayland support. This way we can ensure that our code always supports both modes. The tests found multiple issues. At the moment fast running tests are sporadically crashing on tear down. This needs further investigation.
2017-09-30 14:35:52 +00:00
integrationTest(WAYLAND_ONLY NAME testDecorationInput SRCS decoration_input_test.cpp)
integrationTest(WAYLAND_ONLY NAME testInternalWindow SRCS internal_window.cpp)
integrationTest(WAYLAND_ONLY NAME testTouchInput SRCS touch_input_test.cpp)
integrationTest(WAYLAND_ONLY NAME testInputStackingOrder SRCS input_stacking_order.cpp)
[autotests/integration] Simplify the cmake for creating a test Summary: A dedicated cmake function is added to create a test case. It takes a NAME, the SRCS and additional LIBS. Thus it's integrationTest(NAME myTestCase SRCS test.cpp) to create a standard integration test. In addition kwin_wayland_test.cpp is compiled into a static library to decrease the compile time a little bit. Reviewers: #kwin, #plasma_on_wayland Subscribers: plasma-devel, kwin Tags: #plasma_on_wayland, #kwin Differential Revision: https://phabricator.kde.org/D2052
2016-06-30 06:37:50 +00:00
integrationTest(NAME testPointerInput SRCS pointer_input.cpp)
integrationTest(NAME testPlatformCursor SRCS platformcursor.cpp)
[autotests] Support Wayland Only in addition to XWayland The integrationTest function takes a new optional argument whether the test supports a Wayland Only mode. If that's the case the test is compiled twice, once (as always) as "foo" with XWayland support and once as "foo_waylandonly" without XWayland support. This way we can ensure that our code always supports both modes. The tests found multiple issues. At the moment fast running tests are sporadically crashing on tear down. This needs further investigation.
2017-09-30 14:35:52 +00:00
integrationTest(WAYLAND_ONLY NAME testDontCrashCancelAnimation SRCS dont_crash_cancel_animation.cpp)
[autotests] Fix typo in autotest name
2019-02-12 12:37:42 +00:00
integrationTest(WAYLAND_ONLY NAME testTransientPlacement SRCS transient_placement.cpp)
[autotests/integration] Simplify the cmake for creating a test Summary: A dedicated cmake function is added to create a test case. It takes a NAME, the SRCS and additional LIBS. Thus it's integrationTest(NAME myTestCase SRCS test.cpp) to create a standard integration test. In addition kwin_wayland_test.cpp is compiled into a static library to decrease the compile time a little bit. Reviewers: #kwin, #plasma_on_wayland Subscribers: plasma-devel, kwin Tags: #plasma_on_wayland, #kwin Differential Revision: https://phabricator.kde.org/D2052
2016-06-30 06:37:50 +00:00
integrationTest(NAME testDebugConsole SRCS debug_console_test.cpp)
integrationTest(NAME testDontCrashEmptyDeco SRCS dont_crash_empty_deco.cpp)
[autotests] Support Wayland Only in addition to XWayland The integrationTest function takes a new optional argument whether the test supports a Wayland Only mode. If that's the case the test is compiled twice, once (as always) as "foo" with XWayland support and once as "foo_waylandonly" without XWayland support. This way we can ensure that our code always supports both modes. The tests found multiple issues. At the moment fast running tests are sporadically crashing on tear down. This needs further investigation.
2017-09-30 14:35:52 +00:00
integrationTest(WAYLAND_ONLY NAME testPlasmaSurface SRCS plasma_surface_test.cpp)
integrationTest(WAYLAND_ONLY NAME testMaximized SRCS maximize_test.cpp)
Rename XdgShellClient to XdgShellWindow The word "client" means different things in wayland and kwin. Use a better word to refer to windows.
2022-04-22 18:11:29 +00:00
integrationTest(WAYLAND_ONLY NAME testXdgShellWindow SRCS xdgshellwindow_test.cpp)
[autotests] Support Wayland Only in addition to XWayland The integrationTest function takes a new optional argument whether the test supports a Wayland Only mode. If that's the case the test is compiled twice, once (as always) as "foo" with XWayland support and once as "foo_waylandonly" without XWayland support. This way we can ensure that our code always supports both modes. The tests found multiple issues. At the moment fast running tests are sporadically crashing on tear down. This needs further investigation.
2017-09-30 14:35:52 +00:00
integrationTest(WAYLAND_ONLY NAME testDontCrashNoBorder SRCS dont_crash_no_border.cpp)
Remove X clipboard sync helper and rename its autotest Summary: With the gneric X selections infrastructure and clipboard support the X clipboard sync helper utility can be removed. Also rename its autotest as it tests the inner workings of the new mechanism since this mechanism was introduced. Test Plan: Autotest still passes under new name. Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: graesslin, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D15063
2018-08-21 20:06:42 +00:00
integrationTest(NAME testXwaylandSelections SRCS xwayland_selections_test.cpp)
Reduce the amount of objects that are compiled several times Summary: We build some objects several times which makes it uncomfortable to develop KWin since every time we modify something a lot of things get rebuilt. This should help a bit although it doesn't solve all the problems. Test Plan: Builds, tests pass Reviewers: #kwin, zzag Reviewed By: #kwin, zzag Subscribers: davidedmundson, zzag, anthonyfieroni, iasensio, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D28445
2020-04-01 22:41:38 +00:00
integrationTest(WAYLAND_ONLY NAME testSceneOpenGL SRCS scene_opengl_test.cpp )
integrationTest(WAYLAND_ONLY NAME testSceneOpenGLES SRCS scene_opengl_es_test.cpp )
[autotests] Support Wayland Only in addition to XWayland The integrationTest function takes a new optional argument whether the test supports a Wayland Only mode. If that's the case the test is compiled twice, once (as always) as "foo" with XWayland support and once as "foo_waylandonly" without XWayland support. This way we can ensure that our code always supports both modes. The tests found multiple issues. At the moment fast running tests are sporadically crashing on tear down. This needs further investigation.
2017-09-30 14:35:52 +00:00
integrationTest(WAYLAND_ONLY NAME testScreenChanges SRCS screen_changes_test.cpp)
[autotest/integration] Add a test case for modifier only shortcuts This test verifies the functionality of modifier only shortcut activation. The base test case uses a helper object which is exported to DBus and has a slot which can get triggered. The test configures the individual modifiers to call that DBus method when the shortcut is triggered. It simulates pressing the modifier and verifies the DBus method was invoked or not.
2016-08-13 12:35:01 +00:00
integrationTest(NAME testModiferOnlyShortcut SRCS modifier_only_shortcut_test.cpp)
autotests: Guard tabbox_test by KWIN_BUILD_TABBOX Signed-off-by: Victoria Fischer <victoria.fischer@mbition.io>
2022-03-03 14:20:20 +00:00
if (KWIN_BUILD_TABBOX)
integrationTest(WAYLAND_ONLY NAME testTabBox SRCS tabbox_test.cpp)
endif()
[autotests] Support Wayland Only in addition to XWayland The integrationTest function takes a new optional argument whether the test supports a Wayland Only mode. If that's the case the test is compiled twice, once (as always) as "foo" with XWayland support and once as "foo_waylandonly" without XWayland support. This way we can ensure that our code always supports both modes. The tests found multiple issues. At the moment fast running tests are sporadically crashing on tear down. This needs further investigation.
2017-09-30 14:35:52 +00:00
integrationTest(WAYLAND_ONLY NAME testWindowSelection SRCS window_selection_test.cpp)
integrationTest(WAYLAND_ONLY NAME testPointerConstraints SRCS pointer_constraints_test.cpp)
integrationTest(WAYLAND_ONLY NAME testKeyboardLayout SRCS keyboard_layout_test.cpp)
integrationTest(WAYLAND_ONLY NAME testKeymapCreationFailure SRCS keymap_creation_failure_test.cpp)
integrationTest(WAYLAND_ONLY NAME testShowingDesktop SRCS showing_desktop_test.cpp)
[QPA] Implement Screen on top of internal Screens API Summary: The test DontCrashUseractionsMenu (Waylandonly) found an issue in our screen handling implementation in the QPA. The code exposed a short time frame between the dummy screen getting destroyed and the first screen being added. This could result in a crash of KWin. There is actually no need to implement Screen on top of Wayland screen. KWin has all the knowledge, so we can also base this on top of the Screens API. Advantages: * no delays due to Wayland roundtrips * handle screen getting removed (was a TODO) * handle resolution changes (was a TODO) The new implementation has a disadvantage that it destroys and readds all screens whenever something around the screen changes. This shouldn't be an issue in practice as it's only for the internal QPA and thus only affects KWin internal windows which is placed in global coordinates anyway. If it turns out to be a problem we need to track better the screen changes - so far those were not tracked at all. Test Plan: Run a few unit tests which change screens Reviewers: #kwin, #plasma Subscribers: plasma-devel, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D8345
2017-10-17 17:13:50 +00:00
integrationTest(WAYLAND_ONLY NAME testDontCrashUseractionsMenu SRCS dont_crash_useractions_menu.cpp)
[autotests] Support Wayland Only in addition to XWayland The integrationTest function takes a new optional argument whether the test supports a Wayland Only mode. If that's the case the test is compiled twice, once (as always) as "foo" with XWayland support and once as "foo_waylandonly" without XWayland support. This way we can ensure that our code always supports both modes. The tests found multiple issues. At the moment fast running tests are sporadically crashing on tear down. This needs further investigation.
2017-09-30 14:35:52 +00:00
integrationTest(WAYLAND_ONLY NAME testKWinBindings SRCS kwinbindings_test.cpp)
Rename LayerShellV1Client to LayerShellV1Window The word "client" means different things in wayland and kwin. Use a better word to refer to windows.
2022-04-22 17:46:41 +00:00
integrationTest(WAYLAND_ONLY NAME testLayerShellV1Window SRCS layershellv1window_test.cpp)
Merge branch 'Plasma/5.11'
2017-10-01 13:26:40 +00:00
integrationTest(WAYLAND_ONLY NAME testVirtualDesktop SRCS virtual_desktop_test.cpp)
Rename XdgShellClient to XdgShellWindow The word "client" means different things in wayland and kwin. Use a better word to refer to windows.
2022-04-22 18:11:29 +00:00
integrationTest(WAYLAND_ONLY NAME testXdgShellWindowRules SRCS xdgshellwindow_rules_test.cpp)
Add support for new IdleInhibition protocol Summary: A small helper class is added which manages inhibiting idle for the ShellClients. So far only very basic functionality is added. That is only the inhibition on the Surface is followed. It is not yet checked whether the ShellClient is visible at all. That needs some changes in ShellClient. BUG: 385956 FIXED-IN: 5.12 Test Plan: New test case passes Reviewers: #kwin, #plasma Subscribers: plasma-devel, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D8856
2017-11-16 20:48:19 +00:00
integrationTest(WAYLAND_ONLY NAME testIdleInhibition SRCS idle_inhibition_test.cpp)
Make sure that effect windows outlive effects Summary: Compositing is suspended/finished in a very hard way fashion, effect windows are destroyed without notifying effects about it. AnimationEffect tries gracefully release deleted windows, but because in some cases(like when suspending compositing) a deleted window can be already destroyed, a segmentation fault can happen. This change adjusts the order in which effect windows and effects are destroyed, so AnimationEffect (and other effects) cannot access dangling pointers. BUG: 400788 FIXED-IN: 5.15.0 Reviewers: #kwin, graesslin Reviewed By: #kwin, graesslin Subscribers: graesslin, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D17311
2018-12-01 16:23:37 +00:00
integrationTest(WAYLAND_ONLY NAME testDontCrashReinitializeCompositor SRCS dont_crash_reinitialize_compositor.cpp)
Introduce a command line option to disable any kind of global shortcuts Summary: This command line option is useful for KWin in embedded use case. That is when KWin is just used as a compositor for one application instead of a complete desktop environment. In such a setup global shortcuts are not wanted and interfere with the application. E.g. one does not want Alt+F4 to close the window, that would render the system unusable. This change introduces a command line option and disables the following event filters and spies: * global shortcuts * modifier only shortcuts * terminate session * virtual terminal switching * screen edges KGlobalAccel still gets inited, otherwise the (non-functional) binary would be launched when KWin registers it's global shortcuts. Test Plan: New test added based on existing tests for the global shortcuts, ctest passes Reviewers: #kwin Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D17304
2018-12-02 12:09:37 +00:00
integrationTest(WAYLAND_ONLY NAME testNoGlobalShortcuts SRCS no_global_shortcuts_test.cpp)
Reduce the amount of objects that are compiled several times Summary: We build some objects several times which makes it uncomfortable to develop KWin since every time we modify something a lot of things get rebuilt. This should help a bit although it doesn't solve all the problems. Test Plan: Builds, tests pass Reviewers: #kwin, zzag Reviewed By: #kwin, zzag Subscribers: davidedmundson, zzag, anthonyfieroni, iasensio, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D28445
2020-04-01 22:41:38 +00:00
integrationTest(WAYLAND_ONLY NAME testBufferSizeChange SRCS buffer_size_change_test.cpp )
[autotests] Fix filename of placement test
2019-09-12 16:45:53 +00:00
integrationTest(WAYLAND_ONLY NAME testPlacement SRCS placement_test.cpp)
Traverse the stacking order backwards when switching between windows Summary: In order to pick the next client to activate we traverse the stacking order from bottom to top and assign to each client a score. The client with the best score will be activated next. Function that assigns score bases its decisions purely on geometry. This may backfire if there are couple maximized or fullscreen clients on the screen - we'll activate the bottom-most client. This change toggles direction we traverse the stacking order. If there are several clients with an identical score, then prefer the top-most client, the one that the user most likely sees at the moment. BUG: 411356 FIXED-IN: 5.17.0 Test Plan: New tests pass. Reviewers: #kwin Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D23521
2019-08-28 08:46:30 +00:00
integrationTest(WAYLAND_ONLY NAME testActivation SRCS activation_test.cpp)
autotests: rename to testInputMethod Relevant class got renamed, also update the test name Related: plasma/kwin!302
2020-09-30 10:28:42 +00:00
integrationTest(WAYLAND_ONLY NAME testInputMethod SRCS inputmethod_test.cpp)
autotests: Convert testScreens into an integration test At the moment, the Screens class is convoluted with ifdefs because of MockScreens. The goal of this change is to reduce the number of usages of the MockScreens class so it is possible to get rid of the ifdefs.
2020-12-21 11:01:38 +00:00
integrationTest(WAYLAND_ONLY NAME testScreens SRCS screens_test.cpp)
autotests: Rewrite testScreenEdges as an integration test Due to the screen edges test not being an integration test, it's very hard to change output related code in libkwin. screens.cpp needs to have a few ifdefs to successfully compile. This change rewrites the screen edges test as an integration test in order to allow us using other components of kwin in screens.cpp and screenedge.cpp without ifdef guards. It's not a one-to-one port.
2021-08-28 08:17:46 +00:00
integrationTest(WAYLAND_ONLY NAME testScreenEdges SRCS screenedges_test.cpp)
autotests: Replace output management test with a more useful test The output management test checks the implementation of output management capabilities in the virtual backend, which is not helpful. This change replaces it with a more useful test that verifies how windows are placed after an output change.
2021-12-10 10:22:19 +00:00
integrationTest(WAYLAND_ONLY NAME testOutputChanges SRCS outputchanges_test.cpp)
Custom quick tiling with configuration ui * Allow to do quick tiling to custom tile geometries, windows will be snapped to tiles when dragged with the shift modifier pressed. * Tile geometries are screen specific. * The global shortcut Meta+T will trigger a fullscreen configuration ui as a QML effect for the tiles which allows to add, remove and resize tiles * UI and behavior is a bit similar to the Windows Fancy Zones addon: https://docs.microsoft.com/en-us/windows/powertoys/fancyzones * Its main scope is to help the workflow with very big monitors, especially ultra wide ones, where most application don't make sense maximized to the full screen (eventually also support games to be full screened to a given tile instead of the whole screen) * it should get also some bindings for scripting, as its ain goal is not to replicate other popular tiling window managers, but should give the popular kwin tiling scripts to have a more robust infrastructure * it will eventually get support for a set of predefined layouts, but this is for a second phase BUG: 438788
2022-12-01 14:39:22 +00:00
integrationTest(WAYLAND_ONLY NAME testTiles SRCS tiles_test.cpp)
[autotest/wayland] Add a test for quick tiling Wayland clients Base test verifies the quick tile positions. No maximization or direct state changes tested yet. Required to have Toplevel and AbstractClient exported. Otherwise we cannot use the SignalSpy.
2015-10-14 07:58:16 +00:00
Use version-less qt DBus macros They work with both Qt5 and Qt6
2021-05-30 23:00:35 +00:00
qt_add_dbus_interfaces(DBUS_SRCS ${CMAKE_BINARY_DIR}/src/org.kde.kwin.VirtualKeyboard.xml)
inputmethod: Refactor VirtualKeyboardDBus to have its own InputMethpd This way we can have it call methods directly instead of connecting to its signals.
2021-02-26 15:16:45 +00:00
integrationTest(WAYLAND_ONLY NAME testVirtualKeyboardDBus SRCS test_virtualkeyboard_dbus.cpp ${DBUS_SRCS})
Make lcms2 a hard dependency When we do more color management stuff we'll need it in more places, making it a hard requirement reduces the amount of needed ifdefs and should make adding color management features a little simpler.
2022-01-10 12:15:54 +00:00
integrationTest(WAYLAND_ONLY NAME testNightColor SRCS nightcolor_test.cpp LIBS KWinNightColorPlugin)
Introduce ColorManager component This change introduces a new component - ColorManager that is responsible for color management stuff. At the moment, it's very naive. It is useful only for updating gamma ramps. But in the future, it will be extended with more CMS-related features. The ColorManager depends on lcms2 library. This is an optional dependency. If lcms2 is not installed, the color manager won't be built. This also fixes the issue where colord and nightcolor overwrite each other's gamma ramps. With this change, the ColorManager will resolve the conflict between two.
2020-11-27 19:37:40 +00:00
Conditionally compile tests which depend on XCB_ICCCM Summary: Move/Resize and Strut tests Wayland tests are affected. Test Plan: Successful compilation when XCB_ICCCM is not found Reviewers: graesslin Reviewed By: graesslin Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1476
2016-04-25 09:27:00 +00:00
if (XCB_ICCCM_FOUND)
[autotests/integration] Simplify the cmake for creating a test Summary: A dedicated cmake function is added to create a test case. It takes a NAME, the SRCS and additional LIBS. Thus it's integrationTest(NAME myTestCase SRCS test.cpp) to create a standard integration test. In addition kwin_wayland_test.cpp is compiled into a static library to decrease the compile time a little bit. Reviewers: #kwin, #plasma_on_wayland Subscribers: plasma-devel, kwin Tags: #plasma_on_wayland, #kwin Differential Revision: https://phabricator.kde.org/D2052
2016-06-30 06:37:50 +00:00
integrationTest(NAME testMoveResize SRCS move_resize_window_test.cpp LIBS XCB::ICCCM)
integrationTest(NAME testStruts SRCS struts_test.cpp LIBS XCB::ICCCM)
integrationTest(NAME testShade SRCS shade_test.cpp LIBS XCB::ICCCM)
integrationTest(NAME testDontCrashAuroraeDestroyDeco SRCS dont_crash_aurorae_destroy_deco.cpp LIBS XCB::ICCCM)
integrationTest(NAME testPlasmaWindow SRCS plasmawindow_test.cpp LIBS XCB::ICCCM)
[autotests/integration] Add new test case for screenedge client show A test to simulate auto-hiding panels. Preparation step for making the slidingpopups effect working again for auto-hiding panels. The test case simulates creating a panel at the screen edge, hides it through the property and shows it again through the edge.
2016-07-14 07:45:03 +00:00
integrationTest(NAME testScreenEdgeClientShow SRCS screenedge_client_show_test.cpp LIBS XCB::ICCCM)
Force windows of type desktop to be opaque Summary: Plasmashell's desktop windows are RGBA which forces the compositor to perform blending and render the background. That is absolutely pointless as there is no window behind the desktop window it could blend to. All it does is destroying KWin's more optimized code path and forcing additional rendering which will never be visible (including shader push/pop). With this change KWin forces desktop windows (both X11 and Wayland) to be considered as opaque by setting the depth to 24. Thus blending is disabled and the background is not rendered. Test Plan: Verified with apitrace that KWin goes in the opaque rendering path for desktop windows. Reviewers: #kwin, #plasma Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D2382
2016-08-09 11:50:29 +00:00
integrationTest(NAME testX11DesktopWindow SRCS desktop_window_x11_test.cpp LIBS XCB::ICCCM)
[autotests] Add a test case for pointer enter/leave of X windows This test simulates the situation that pointer leave on an X surface does not send the XCB_LEAVE_NOTIFY event to the X window.
2016-08-23 07:15:05 +00:00
integrationTest(NAME testXwaylandInput SRCS xwayland_input_test.cpp LIBS XCB::ICCCM)
[autotests/integration] Add test case for rule matching on window role New test infrastructure which supports testing window rules at runtime. Test exposes problem of window rules not able to match window roles in a case insensitive manner. CCBUG: 367554
2016-08-25 11:23:06 +00:00
integrationTest(NAME testWindowRules SRCS window_rules_test.cpp LIBS XCB::ICCCM)
Rename X11Client to X11Window The word "client" means different things in wayland and kwin. Use a better word to refer to windows.
2022-04-22 17:54:31 +00:00
integrationTest(NAME testX11Window SRCS x11_window_test.cpp LIBS XCB::ICCCM)
[autotests] Add test case for quick tiling on X11 Exposes our regressions of X11 quick tiling when a window is vertically maximized. CCBUG: 376155
2017-02-14 06:29:38 +00:00
integrationTest(NAME testQuickTiling SRCS quick_tiling_test.cpp LIBS XCB::ICCCM)
[autotests] Add test case for Client window shortcut Registers a shortcut on a window and triggers it.
2017-07-20 17:00:01 +00:00
integrationTest(NAME testGlobalShortcuts SRCS globalshortcuts_test.cpp LIBS XCB::ICCCM)
Generalize constrainedStackingOrder for group transients and ordinary transients Summary: We don't really have to have two different code paths for group transients and ordinary transients. For now, AbstractClient::hasTransient is good enough to check the relationship between potential parent and the transient. In long term, we need to "invert" the relationship, instead of checking whether given parent window has a transient, we should check whether given transient is a transient for a given window so we can keep Deleted transients above their old parents. Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D15893
2018-10-02 05:39:31 +00:00
integrationTest(NAME testStackingOrder SRCS stacking_order_test.cpp LIBS XCB::ICCCM)
Add a dbus method getWindowInfo returning same data as queryWindowInfo Summary: This dbus method is intended to be used by the kwin rules dialog. KWin can pass the internal id to the rules dialog through a command line argument (or similar way) and the dialog can query the information through the dbus call for the provided id. Thus it's possible to implement one way to query the information which works on both X11 and Wayland without any windowing system specific functionality. Test Plan: See new added integration test Reviewers: #kwin Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D17433
2018-12-08 16:06:51 +00:00
integrationTest(NAME testDbusInterface SRCS dbus_interface_test.cpp LIBS XCB::ICCCM)
xwayland: Restart the Xwayland server after it has crashed If the Xwayland process has crashed due to some bug, the user should still be able to start applications in Xwayland mode. There is no reason to restart the whole session just to be able to launch some application that doesn't have native support for Wayland.
2020-08-27 09:05:28 +00:00
integrationTest(NAME testXwaylandServerCrash SRCS xwaylandserver_crash_test.cpp LIBS XCB::ICCCM)
integrationTest(NAME testXwaylandServerRestart SRCS xwaylandserver_restart_test.cpp LIBS XCB::ICCCM)
[autotests/integration] Add a first test case for activities Verifies the condition from D1982 with expected_fail. That is sets a Client on non existing activities and expects that it should be on all activities.
2016-08-12 10:52:47 +00:00
if (KWIN_BUILD_ACTIVITIES)
integrationTest(NAME testActivities SRCS activities_test.cpp LIBS XCB::ICCCM)
endif()
Conditionally compile tests which depend on XCB_ICCCM Summary: Move/Resize and Strut tests Wayland tests are affected. Test Plan: Successful compilation when XCB_ICCCM is not found Reviewers: graesslin Reviewed By: graesslin Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1476
2016-04-25 09:27:00 +00:00
endif()
[autotest/integration] Add a test case for screenedge usage in Scripts A new sub-directory scripting is added in autotests/integration to gather all test cases related to scripting. The first added test case verifies the activation of screen edges. For that it loads a helper script, which reserves an edge based on config. When the edge is triggered showing desktop is activated.
2016-08-02 07:12:57 +00:00
add_subdirectory(scripting)
Ensure that EffectsHandlerImpl::slotClientShown is only invoked once per Window Summary: This fixes a regression introduced with a1afeded6ae63e47d39fc08480e929c0451c51e8. The connections were setup every the windowShown signal got emitted. This caused effects to get multiple singals and start multiple animations which then do not get cancelled correctly. The incorrect behavior was most visible in the translucency effect which did not cancel the move animation and the window stayed translucent. BUG: 366081 Test Plan: New test case which simulates the behavior of the translucency effect. Reviewers: #kwin, #plasma, sebas Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D2346
2016-08-03 14:12:23 +00:00
add_subdirectory(effects)
[scenes/opengl] Fix overlapping shadow tiles Summary: This problem appears if shadow corner tiles are too big and some window has size smaller than 2 * shadowTileSize. This change tries to address the problem above by exclusing overlapping tile parts. If there are any two overlapping corners then tile between them(top/right/bottom/left) is not rendered. Also, because some corner tile parts can be excluded, corner tiles are expected to be symmetrical(i.e. if we remove right half from the top-left tile and left half from the top-right tile and stick them together, they still look fine, there are no misalignments, etc). Most shadows(e.g. shadows from Breeze) have such behaviour. No tiles are overlapping {F5728514, layout=center, size=full} Overlapping tiles {F5728516, layout=center, size=full} And this is how it supposed to be {F5728517, layout=center, size=full} Test Plan: * apply D11069 to Breeze * in System Settings/Application Style/Window Decorations, choose "Very Large" shadow size * open Konsole * resize it to a minimum possible size Reviewers: #kwin, graesslin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: davidedmundson, ngraham, anemeth, abetts, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D10811
2018-06-07 08:48:05 +00:00
add_subdirectory(fakes)
Reference in a new issue Copy permalink