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

150 lines
6.8 KiB
Text
Raw Normal View History

Move backends/ to plugins/platforms/ Summary: Source code reorganization: The base class AbstractBackend got renamed to Platform, thus the "backends" are "platforms" now. As they are plugins they should go together with other KWin plugins which are nowadays in the folder plugins. So new location is plugins/platforms/ Reviewers: #plasma, sebas Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1353
2016-04-08 06:49:42 +00:00
add_definitions(-DKWINBACKENDPATH="${CMAKE_BINARY_DIR}/plugins/platforms/virtual/KWinWaylandVirtualBackend.so")
[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(-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
########################################################
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)
set( testMoveResize_SRCS move_resize_window_test.cpp kwin_wayland_test.cpp )
add_executable(testMoveResize ${testMoveResize_SRCS})
target_link_libraries( testMoveResize kwin Qt5::Test XCB::ICCCM)
add_test(kwin-testMoveResize testMoveResize)
ecm_mark_as_test(testMoveResize)
endif()
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
[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)
[autotests] New test for input on window decoration First test case is whether wheel events are forwarded correctly. From the code it seems to me like up/down is inversed. Needs manual testing. As this requires working decorations it's possible that this test will fail on build.kde.org.
2016-02-04 10:18:45 +00:00
########################################################
# Decoration input test
########################################################
set( testDecorationInput_SRCS decoration_input_test.cpp kwin_wayland_test.cpp )
add_executable(testDecorationInput ${testDecorationInput_SRCS})
target_link_libraries( testDecorationInput kwin Qt5::Test)
add_test(kwin-testDecorationInput testDecorationInput)
ecm_mark_as_test(testDecorationInput)
[autotest] Add a test for a KWin internal QWindow The test creates a QRasterWindow which through KWin's internal QPA is considered an internal window. In the test methods we simulate various pointer events (enter/leave, press/release, wheel).
2016-02-05 14:39:04 +00:00
########################################################
# Internal Window test
########################################################
set( testInternalWindow_SRCS internal_window.cpp kwin_wayland_test.cpp )
add_executable(testInternalWindow ${testInternalWindow_SRCS})
target_link_libraries( testInternalWindow kwin Qt5::Test)
add_test(kwin-testInternalWindow testInternalWindow)
ecm_mark_as_test(testInternalWindow)
[autotest] Add test for touch input Basic test validating: * multiple touch points are handled * cancel is handled
2016-02-09 10:35:15 +00:00
########################################################
# Touch Input Test
########################################################
set( testTouchInput_SRCS touch_input_test.cpp kwin_wayland_test.cpp )
add_executable(testTouchInput ${testTouchInput_SRCS})
target_link_libraries( testTouchInput kwin Qt5::Test)
add_test(kwin-testTouchInput testTouchInput)
ecm_mark_as_test(testTouchInput)
[autotest] Test case for stacking order changes should change focus A new test case which ensures that when stacking order changes the pointer focus gets re-evaluated and updated. I was positively surprised to notice that this already works. Noticed two other problems while writing the test case: * warping pointer does not re-evaluate the pointer pos * deleting a ShellSurface (client) does not destroy the ShellClient (server)
2016-02-11 09:47:21 +00:00
########################################################
# Input Stacking Order Test
########################################################
set( testInputStackingOrder_SRCS input_stacking_order.cpp kwin_wayland_test.cpp )
add_executable(testInputStackingOrder ${testInputStackingOrder_SRCS})
target_link_libraries( testInputStackingOrder kwin Qt5::Test)
add_test(kwin-testInputStackingOrder testInputStackingOrder)
ecm_mark_as_test(testInputStackingOrder)
[autotest] Add test for internal pointer warping When warping a pointer through Cursor::setPos it should be processed just like any other pointer event. It should generate enter/leave event, create motion events, etc. This is currently not the case as the test shows.
2016-02-11 11:48:42 +00:00
########################################################
# Pointer Input Test
########################################################
set( testPointerInput_SRCS pointer_input.cpp kwin_wayland_test.cpp )
add_executable(testPointerInput ${testPointerInput_SRCS})
target_link_libraries( testPointerInput kwin Qt5::Test)
add_test(kwin-testPointerInput testPointerInput)
ecm_mark_as_test(testPointerInput)
[plugins/qpa] Implement a custom QPlatformCursor This makes QCursor::pos and QCursor::setPos function correctly. KWin actually wouldn't need it as KWin has the KWin::Cursor replacement, but it allows Qt internal API to have it function correctly and also the zoom effect does use QCursor::setPos.
2016-02-17 11:42:12 +00:00
########################################################
# PlatformCursorTest
########################################################
set( testPlatformCursor_SRCS platformcursor.cpp kwin_wayland_test.cpp )
add_executable(testPlatformCursor ${testPlatformCursor_SRCS})
target_link_libraries( testPlatformCursor kwin Qt5::Test)
add_test(kwin-testPlatformCursor testPlatformCursor)
ecm_mark_as_test(testPlatformCursor)
[autotest] Don't crash when cancel animation from animationEnded in scripted effect Canceling the animation in the animationEnded handler triggers a crash. This is due to multiple lists being iterated and manipulated at the same time. This adds a test case which simulates the crashy situation. REVIEW: 126975
2016-02-02 17:25:36 +00:00
########################################################
# Don't crash cancel animation test
########################################################
set( testDontCrashCancelAnimation_SRCS dont_crash_cancel_animation.cpp kwin_wayland_test.cpp )
add_executable(testDontCrashCancelAnimation ${testDontCrashCancelAnimation_SRCS})
target_link_libraries( testDontCrashCancelAnimation kwin Qt5::Test)
add_test(kwin-testDontCrashCancelAnimation testDontCrashCancelAnimation)
ecm_mark_as_test(testDontCrashCancelAnimation)
[autotest] Add test for transient placement positioning Test creates windows and transients for it and verifies the position. For decorated windows the position is currently broken as it does not consider the adjusted client position.
2016-03-03 12:32:50 +00:00
########################################################
# Transient Placement Test
########################################################
set( testTransientPlacmenet_SRCS transient_placement.cpp kwin_wayland_test.cpp )
add_executable(testTransientPlacmenet ${testTransientPlacmenet_SRCS})
target_link_libraries( testTransientPlacmenet kwin Qt5::Test)
add_test(kwin-testTransientPlacmenet testTransientPlacmenet)
ecm_mark_as_test(testTransientPlacmenet)
Add a debugging console to KWin Summary: The idea behind the debugging console is to have a feature comparable to xprop and xwininfo just for Wayland. We cannot have command line utils as that violates the security restrictions, thus it needs to be exposed directly in KWin. The debugging console is invoked through DBus: qdbus org.kde.KWin /KWin showDebugConsole This opens a window with a tree view. The DebugConsoleModel which is used by the tree view groups all windows into four categories: * x11 clients (that is Workspace::clientList() and Workspace::desktopList()) * x11 unmanaged (Workspace::unmanagedList()) * wayland shell clients (WaylandServer::clients()) * wayland internal clients (KWin's own QWindows - WaylandServer::internalClients()) Each window is a child to one of the four categories. Each window itself has all it's QProperties exposed as children. This allows to properly inspect KWin's internal knowledge for windows and should make it easier to investigate problems. E.g. what's a window's geometry, what's it's window type and so on. The debugging console is intended as a developer tool and not expected to be used by users. That's why it's invokation is rather hidden. Due to the fact that it's internal to KWin it results in: * no window decoration * stealing keyboard focus * no way to resize, close, move from KWin side * rendered above all other windows There is a dedicated close button to get rid of it again. While the console is shown it's hardly possible to interact with the system in a normal way anymore. This is something which might be improved in future. At the moment the model is able to update when windows are added/removed, but not yet when a property changes. Due to the lack of interaction with the existing system, that's not a high priority at the moment, but can be added in future. Reviewers: #plasma Differential Revision: https://phabricator.kde.org/D1146
2016-03-14 09:23:52 +00:00
########################################################
# Debug Console Test
########################################################
set( testDebugConsole_SRCS debug_console_test.cpp kwin_wayland_test.cpp )
add_executable(testDebugConsole ${testDebugConsole_SRCS})
target_link_libraries( testDebugConsole kwin Qt5::Test)
add_test(kwin-testDebugConsole testDebugConsole)
ecm_mark_as_test(testDebugConsole)
Strut sanity checking: ignore struts which would exclude a complete screen Summary: Mostly meant for multi-screen setups: we don't want that a strut set on a window on screen 0 results in screen 1 completely being excluded. Even if that's strictly seen a client bug, it's better to just ignore the strut from KWin's side. The sanity check is implemented in Client::adjustedClientArea. From a pure standard point of view this change is a EWMH violation and thus can cause regressions: struts by clients no longer working. A test case for struts is added, including some invalid combinations whose strut is ignored with this change. Reviewers: #plasma Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1386
2016-04-11 15:24:08 +00:00
########################################################
# Struts Test
########################################################
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)
set( testStruts_SRCS struts_test.cpp kwin_wayland_test.cpp )
add_executable(testStruts ${testStruts_SRCS})
target_link_libraries( testStruts kwin Qt5::Test XCB::ICCCM)
add_test(kwin-testStruts testStruts)
ecm_mark_as_test(testStruts)
endif()
Reference in a new issue Copy permalink