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

56 lines
2.6 KiB
Text
Raw Normal View History

[autotest] Welcome to integration testing KWin This is the beginning of a new testing era for KWin: finally we are able to test against a running KWin. This works by making use of the new virtual framebuffer backend for Wayland. It starts a specific Application subclass which is mostly a fork of ApplicationWayland. The individual tests are able to influence the socket name and the size of the virtual screen. This is supposed to be done in initTestCase. To know when KWin is fully started one can use the workspaceCreated signal of KWin::Application. KWin is not started in another process, but the kwin library is used, so the test has pretty much full introspection to everything going on inside KWin. It can access the Workspace, WaylandServer, fake input events through InputRedirection and so on. Once the test KWin is running it's possible to connect to it using KWayland::Client library. This allows to introspect the Workspace to see whether all worked as expected (e.g. correct stacking order, active window and so on). This first autotest is mostly meant to illustrate how to setup a test and how one can use KWayland::Client to interact with the mock KWin. For more tests it is suggested to move the connections to the Wayland server in the init() and cleanup() methods. The change also affects the qpa plugin: the specific check to only run in binaries called kwin_wayland doesn't hold any more. This can now be overwritten by an env variable. Please note that this first test will probably fail in the CI system as it might not have XWayland which is needed by KWin.
2015-10-02 13:04:57 +00:00
add_definitions(-DKWINBACKENDPATH="${CMAKE_BINARY_DIR}/backends/virtual/KWinWaylandVirtualBackend.so")
add_definitions(-DKWINQPAPATH="${CMAKE_BINARY_DIR}/plugins/qpa/")
########################################################
# Test Start
########################################################
set( testStart_SRCS start_test.cpp kwin_wayland_test.cpp )
add_executable(testStart ${testStart_SRCS})
target_link_libraries( testStart kwin Qt5::Test)
add_test(kwin-testStart testStart)
ecm_mark_as_test(testStart)
[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
########################################################
# Transient Window without input test
########################################################
set( testTransientNoInput_SRCS transient_no_input_test.cpp kwin_wayland_test.cpp )
add_executable(testTransientNoInput ${testTransientNoInput_SRCS})
target_link_libraries( testTransientNoInput kwin Qt5::Test)
add_test(kwin-testTransientNoInput testTransientNoInput)
ecm_mark_as_test(testTransientNoInput)
[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
########################################################
# Quick Tiling test
########################################################
set( testQuickTiling_SRCS quick_tiling_test.cpp kwin_wayland_test.cpp )
add_executable(testQuickTiling ${testQuickTiling_SRCS})
target_link_libraries( testQuickTiling kwin Qt5::Test)
add_test(kwin-testQuickTiling testQuickTiling)
ecm_mark_as_test(testQuickTiling)
[autotests] Test case for 10ad9262a184e1afc088bee35b7fa4c188d9d63f The problem we had was closing a glxgears through an Aurorae theme crashed KWin inside QtQuick. This test case simulates the sequence: 1. starts glxgears 2. wait till we have a Client for it 3. send mouse move to guessed close button position 4. send mouse press/release at that position 5. verify the window is closed 6. verify glxgears exits With the given commit reverted this crashes, with it in place it passes. Please note: on CI it might fail as glxgears is not yet installed. [1] Also we cannot enforce using Aurorae from the test yet, though on the CI system it should get picked automatically as no other deco plugin should be installed. [1] Sysadmin ticket already created
2015-10-22 08:08:49 +00:00
Allow moving of Wayland windows So far only moving through useractions menu is possible and only through cursor control (mouse events are lost). A basic first autotest is added to validate the moving of Windows.
2015-10-26 08:17:46 +00:00
########################################################
# Move/Resize window test
########################################################
set( testMoveResize_SRCS move_resize_window_test.cpp kwin_wayland_test.cpp )
add_executable(testMoveResize ${testMoveResize_SRCS})
target_link_libraries( testMoveResize kwin Qt5::Test)
add_test(kwin-testMoveResize testMoveResize)
ecm_mark_as_test(testMoveResize)
[autotests] Test case for 10ad9262a184e1afc088bee35b7fa4c188d9d63f The problem we had was closing a glxgears through an Aurorae theme crashed KWin inside QtQuick. This test case simulates the sequence: 1. starts glxgears 2. wait till we have a Client for it 3. send mouse move to guessed close button position 4. send mouse press/release at that position 5. verify the window is closed 6. verify glxgears exits With the given commit reverted this crashes, with it in place it passes. Please note: on CI it might fail as glxgears is not yet installed. [1] Also we cannot enforce using Aurorae from the test yet, though on the CI system it should get picked automatically as no other deco plugin should be installed. [1] Sysadmin ticket already created
2015-10-22 08:08:49 +00:00
########################################################
# Don't Crash For glxgears
########################################################
set( testDontCrashGlxgears_SRCS dont_crash_glxgears.cpp kwin_wayland_test.cpp )
add_executable(testDontCrashGlxgears ${testDontCrashGlxgears_SRCS})
target_link_libraries( testDontCrashGlxgears kwin Qt5::Test)
add_test(kwin-testDontCrashGlxgears testDontCrashGlxgears)
ecm_mark_as_test(testDontCrashGlxgears)
[autotest] Add a test for locking the screen First test case is to ensure that pointer motion events trigger a leave event on the surface the pointer is on. The test case shows errors in the input handling. More tests need to be added.
2016-02-01 14:10:00 +00:00
########################################################
# Lock screen integration test
########################################################
set( testLockScreen_SRCS lockscreen.cpp kwin_wayland_test.cpp )
add_executable(testLockScreen ${testLockScreen_SRCS})
target_link_libraries( testLockScreen kwin Qt5::Test)
add_test(kwin-testLockScreen testLockScreen)
ecm_mark_as_test(testLockScreen)
Reference in a new issue Copy permalink