yukijoou/kwin
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
kwin/src/wayland/autotests/client/test_wayland_output.cpp

549 lines
22 KiB
C++
Raw Normal View History

KWayland: Convert license headers to SPDX Summary: Convert license headers to SPDX expressions and add license files as required by REUSE specification. Reviewers: zzag Reviewed By: zzag Subscribers: kde-frameworks-devel Tags: #frameworks Maniphest Tasks: T11550 Differential Revision: https://phabricator.kde.org/D28058
2020-03-15 15:19:28 +00:00
/*
SPDX-FileCopyrightText: 2014 Martin Gräßlin <mgraesslin@kde.org>
[kwin_wayland] Move Wayland::Output into dedicated source files At the same time adding an autotest for the Output, moving the listener into the Output class and providing enums for Subpixel and Transform. KWin now requires wl_ouput interface version 2 as that allows us to emit the changed signal in a better way. The unit test is not yet capable of testing everything, we need a mock Wayland server which is more flexible.
2014-08-19 14:08:02 +00:00
KWayland: Convert license headers to SPDX Summary: Convert license headers to SPDX expressions and add license files as required by REUSE specification. Reviewers: zzag Reviewed By: zzag Subscribers: kde-frameworks-devel Tags: #frameworks Maniphest Tasks: T11550 Differential Revision: https://phabricator.kde.org/D28058
2020-03-15 15:19:28 +00:00
SPDX-License-Identifier: LGPL-2.1-only OR LGPL-3.0-only OR LicenseRef-KDE-Accepted-LGPL
*/
[kwin_wayland] Move Wayland::Output into dedicated source files At the same time adding an autotest for the Output, moving the listener into the Output class and providing enums for Subpixel and Transform. KWin now requires wl_ouput interface version 2 as that allows us to emit the changed signal in a better way. The unit test is not yet capable of testing everything, we need a mock Wayland server which is more flexible.
2014-08-19 14:08:02 +00:00
// Qt
Remove qt include prefixx
2018-11-06 06:22:36 +00:00
#include <QtTest>
[kwin_wayland] Move Wayland::Output into dedicated source files At the same time adding an autotest for the Output, moving the listener into the Output class and providing enums for Subpixel and Transform. KWin now requires wl_ouput interface version 2 as that allows us to emit the changed signal in a better way. The unit test is not yet capable of testing everything, we need a mock Wayland server which is more flexible.
2014-08-19 14:08:02 +00:00
// KWin
Fix build
2020-04-29 13:59:23 +00:00
#include "KWayland/Client/connection_thread.h"
#include "KWayland/Client/event_queue.h"
#include "KWayland/Client/dpms.h"
#include "KWayland/Client/output.h"
#include "KWayland/Client/registry.h"
Add a build system Framework style build system which generates two libraries: * KF5WaylandClient * KF5WaylandServer autotests are adjusted to compile again. They need to be changed to use the libraries once the export header gets generated.
2014-09-17 12:35:33 +00:00
#include "../../src/server/display.h"
[autotests] Extend tests for Dpms REVIEW: 125018
2015-09-01 12:02:38 +00:00
#include "../../src/server/dpms_interface.h"
Add a build system Framework style build system which generates two libraries: * KF5WaylandClient * KF5WaylandServer autotests are adjusted to compile again. They need to be changed to use the libraries once the export header gets generated.
2014-09-17 12:35:33 +00:00
#include "../../src/server/output_interface.h"
[kwin_wayland] Move Wayland::Output into dedicated source files At the same time adding an autotest for the Output, moving the listener into the Output class and providing enums for Subpixel and Transform. KWin now requires wl_ouput interface version 2 as that allows us to emit the changed signal in a better way. The unit test is not yet capable of testing everything, we need a mock Wayland server which is more flexible.
2014-08-19 14:08:02 +00:00
// Wayland
#include <wayland-client-protocol.h>
class TestWaylandOutput : public QObject
{
Q_OBJECT
public:
explicit TestWaylandOutput(QObject *parent = nullptr);
private Q_SLOTS:
void init();
void cleanup();
void testRegistry();
Send only current wl_output mode Non-current output modes were deprecated due to various reasons, e.g. it's not possible to remove some nodes; two modes can have the same resolution and the refresh rate but different flags, but wl_output.mode fails to communicate that properly; the usefulness of non-current modes is questionable. For more details, please refer to [1]. [1] https://gitlab.freedesktop.org/wayland/wayland/-/issues/92
2021-04-04 17:05:10 +00:00
void testModeChange();
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
void testScaleChange();
[kwin_wayland] Move Wayland::Output into dedicated source files At the same time adding an autotest for the Output, moving the listener into the Output class and providing enums for Subpixel and Transform. KWin now requires wl_ouput interface version 2 as that allows us to emit the changed signal in a better way. The unit test is not yet capable of testing everything, we need a mock Wayland server which is more flexible.
2014-08-19 14:08:02 +00:00
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
void testSubPixel_data();
void testSubPixel();
void testTransform_data();
void testTransform();
[kwin_wayland] Move Wayland::Output into dedicated source files At the same time adding an autotest for the Output, moving the listener into the Output class and providing enums for Subpixel and Transform. KWin now requires wl_ouput interface version 2 as that allows us to emit the changed signal in a better way. The unit test is not yet capable of testing everything, we need a mock Wayland server which is more flexible.
2014-08-19 14:08:02 +00:00
[autotests] Extend tests for Dpms REVIEW: 125018
2015-09-01 12:02:38 +00:00
void testDpms_data();
void testDpms();
[autotest] Extend tests for Dpms modes Summary: Now also tests: * requesting mode from client side * update supported change on server side Reviewers: #plasma Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1357
2016-04-08 09:42:51 +00:00
void testDpmsRequestMode_data();
void testDpmsRequestMode();
[kwin_wayland] Move Wayland::Output into dedicated source files At the same time adding an autotest for the Output, moving the listener into the Output class and providing enums for Subpixel and Transform. KWin now requires wl_ouput interface version 2 as that allows us to emit the changed signal in a better way. The unit test is not yet capable of testing everything, we need a mock Wayland server which is more flexible.
2014-08-19 14:08:02 +00:00
private:
Port namespaces and includes
2020-04-29 14:56:38 +00:00
KWaylandServer::Display *m_display;
KWaylandServer::OutputInterface *m_serverOutput;
Use namespace KWayland::Client instead of KWin::WaylandServer It's no longer part of KWin.
2014-09-17 14:17:26 +00:00
KWayland::Client::ConnectionThread *m_connection;
[autotest] Make TestWaylandOutput more robust If we use a thread for the connection we should also have an EventQueue.
2015-05-12 11:16:57 +00:00
KWayland::Client::EventQueue *m_queue;
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
QThread *m_thread;
[kwin_wayland] Move Wayland::Output into dedicated source files At the same time adding an autotest for the Output, moving the listener into the Output class and providing enums for Subpixel and Transform. KWin now requires wl_ouput interface version 2 as that allows us to emit the changed signal in a better way. The unit test is not yet capable of testing everything, we need a mock Wayland server which is more flexible.
2014-08-19 14:08:02 +00:00
};
static const QString s_socketName = QStringLiteral("kwin-test-wayland-output-0");
TestWaylandOutput::TestWaylandOutput(QObject *parent)
: QObject(parent)
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
, m_display(nullptr)
, m_serverOutput(nullptr)
, m_connection(nullptr)
, m_thread(nullptr)
[kwin_wayland] Move Wayland::Output into dedicated source files At the same time adding an autotest for the Output, moving the listener into the Output class and providing enums for Subpixel and Transform. KWin now requires wl_ouput interface version 2 as that allows us to emit the changed signal in a better way. The unit test is not yet capable of testing everything, we need a mock Wayland server which is more flexible.
2014-08-19 14:08:02 +00:00
{
}
void TestWaylandOutput::init()
{
Port namespaces and includes
2020-04-29 14:56:38 +00:00
using namespace KWaylandServer;
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
delete m_display;
m_display = new Display(this);
Allow accepting client connections on multiple sockets libwayland-server allows the wl_display accept client connections on more than one socket. We currently don't listen on multiple sockets, but it would be nice if Display supported such operation mode.
2020-10-19 15:52:56 +00:00
m_display->addSocketName(s_socketName);
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
m_display->start();
QVERIFY(m_display->isRunning());
Remove factory methods in Display The main reason why we have factory methods is that up to some point, kwayland had its own signal to indicate when globals have to be removed. Now that all globals add destroy listeners for the wl_display object, we don't have that signal. Most factory methods are equivalent to doing new T(display). Besides adding unnecessary boilerplate code, another reason to get rid of the factory methods is to reduce the amount of merge conflicts. If several persons work on implementing wayland protocols at the same time, sooner or later someone will have to resolve merge conflicts in Display.
2020-12-09 20:13:19 +00:00
m_serverOutput = new OutputInterface(m_display, this);
[autotests] Extend test for OutputInterface Just adds more test conditions to the already existing test.
2016-06-13 17:19:06 +00:00
QCOMPARE(m_serverOutput->pixelSize(), QSize());
QCOMPARE(m_serverOutput->refreshRate(), 60000);
Send only current wl_output mode Non-current output modes were deprecated due to various reasons, e.g. it's not possible to remove some nodes; two modes can have the same resolution and the refresh rate but different flags, but wl_output.mode fails to communicate that properly; the usefulness of non-current modes is questionable. For more details, please refer to [1]. [1] https://gitlab.freedesktop.org/wayland/wayland/-/issues/92
2021-04-04 17:05:10 +00:00
m_serverOutput->setMode(QSize(1024, 768));
[autotests] Extend test for OutputInterface Just adds more test conditions to the already existing test.
2016-06-13 17:19:06 +00:00
QCOMPARE(m_serverOutput->pixelSize(), QSize(1024, 768));
QCOMPARE(m_serverOutput->refreshRate(), 60000);
[autotests] Extend tests for Dpms REVIEW: 125018
2015-09-01 12:02:38 +00:00
QCOMPARE(m_serverOutput->isDpmsSupported(), false);
Fix test after OutputInterface: Initialize output in Off state ctest passes again
2020-05-19 13:11:27 +00:00
QCOMPARE(m_serverOutput->dpmsMode(), OutputInterface::DpmsMode::Off);
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
// setup connection
Use namespace KWayland::Client instead of KWin::WaylandServer It's no longer part of KWin.
2014-09-17 14:17:26 +00:00
m_connection = new KWayland::Client::ConnectionThread;
Port all connects This is mostly all automatic from clazy, though it got confused by a few namespace issues.
2021-02-25 13:48:11 +00:00
QSignalSpy connectedSpy(m_connection, &KWayland::Client::ConnectionThread::connected);
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
m_connection->setSocketName(s_socketName);
m_thread = new QThread(this);
m_connection->moveToThread(m_thread);
m_thread->start();
m_connection->initConnection();
QVERIFY(connectedSpy.wait());
[autotest] Make TestWaylandOutput more robust If we use a thread for the connection we should also have an EventQueue.
2015-05-12 11:16:57 +00:00
m_queue = new KWayland::Client::EventQueue(this);
QVERIFY(!m_queue->isValid());
m_queue->setup(m_connection);
QVERIFY(m_queue->isValid());
[kwin_wayland] Move Wayland::Output into dedicated source files At the same time adding an autotest for the Output, moving the listener into the Output class and providing enums for Subpixel and Transform. KWin now requires wl_ouput interface version 2 as that allows us to emit the changed signal in a better way. The unit test is not yet capable of testing everything, we need a mock Wayland server which is more flexible.
2014-08-19 14:08:02 +00:00
}
void TestWaylandOutput::cleanup()
{
[autotest] Make TestWaylandOutput more robust If we use a thread for the connection we should also have an EventQueue.
2015-05-12 11:16:57 +00:00
if (m_queue) {
delete m_queue;
m_queue = nullptr;
}
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
if (m_thread) {
m_thread->quit();
m_thread->wait();
delete m_thread;
m_thread = nullptr;
}
delete m_connection;
m_connection = nullptr;
delete m_display;
m_display = nullptr;
Destroy all clients before destroying wl_display One of the most disappointing things when writing autotests is dealing with a race condition where destructor requests are processed after all globals have been destroyed. With this change, the Display object will destroy all clients and their resources before destroying the wl_display object. The good thing about doing so is that shut down logic becomes simple. We don't have to assume that wl_resource objects can outlive their wl_global objects, etc. The bad thing is that it exposed a couple of pre-existing latent bugs in the data device and the xdg foreign code. closes plasma/kwayland-server#2
2020-10-30 13:36:24 +00:00
// these are the children of the display
m_serverOutput = nullptr;
[kwin_wayland] Move Wayland::Output into dedicated source files At the same time adding an autotest for the Output, moving the listener into the Output class and providing enums for Subpixel and Transform. KWin now requires wl_ouput interface version 2 as that allows us to emit the changed signal in a better way. The unit test is not yet capable of testing everything, we need a mock Wayland server which is more flexible.
2014-08-19 14:08:02 +00:00
}
void TestWaylandOutput::testRegistry()
{
Port namespaces and includes
2020-04-29 14:56:38 +00:00
QSignalSpy globalPositionChangedSpy(m_serverOutput, &KWaylandServer::OutputInterface::globalPositionChanged);
[autotests] Extend test for OutputInterface Just adds more test conditions to the already existing test.
2016-06-13 17:19:06 +00:00
QVERIFY(globalPositionChangedSpy.isValid());
QCOMPARE(m_serverOutput->globalPosition(), QPoint(0, 0));
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
m_serverOutput->setGlobalPosition(QPoint(100, 50));
[autotests] Extend test for OutputInterface Just adds more test conditions to the already existing test.
2016-06-13 17:19:06 +00:00
QCOMPARE(m_serverOutput->globalPosition(), QPoint(100, 50));
QCOMPARE(globalPositionChangedSpy.count(), 1);
// changing again should not trigger signal
m_serverOutput->setGlobalPosition(QPoint(100, 50));
QCOMPARE(globalPositionChangedSpy.count(), 1);
Port namespaces and includes
2020-04-29 14:56:38 +00:00
QSignalSpy physicalSizeChangedSpy(m_serverOutput, &KWaylandServer::OutputInterface::physicalSizeChanged);
[autotests] Extend test for OutputInterface Just adds more test conditions to the already existing test.
2016-06-13 17:19:06 +00:00
QVERIFY(physicalSizeChangedSpy.isValid());
QCOMPARE(m_serverOutput->physicalSize(), QSize());
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
m_serverOutput->setPhysicalSize(QSize(200, 100));
[autotests] Extend test for OutputInterface Just adds more test conditions to the already existing test.
2016-06-13 17:19:06 +00:00
QCOMPARE(m_serverOutput->physicalSize(), QSize(200, 100));
QCOMPARE(physicalSizeChangedSpy.count(), 1);
// changing again should not trigger signal
m_serverOutput->setPhysicalSize(QSize(200, 100));
QCOMPARE(physicalSizeChangedSpy.count(), 1);
Add explicit done to OutputInterface and deprecate zxdg_output_v1.done if version 3 is used. In zxdg_output_v1 version 3, done is deprecated and should be replaced with wl_output.done. This makes automatically send done upon change not suitable for the usage. OutputInterface user should now use done() explicitly to send the update. CCBUG: 433224
2021-03-18 01:14:44 +00:00
m_serverOutput->done();
[kwin_wayland] Move Wayland::Output into dedicated source files At the same time adding an autotest for the Output, moving the listener into the Output class and providing enums for Subpixel and Transform. KWin now requires wl_ouput interface version 2 as that allows us to emit the changed signal in a better way. The unit test is not yet capable of testing everything, we need a mock Wayland server which is more flexible.
2014-08-19 14:08:02 +00:00
Use namespace KWayland::Client instead of KWin::WaylandServer It's no longer part of KWin.
2014-09-17 14:17:26 +00:00
KWayland::Client::Registry registry;
Port all connects This is mostly all automatic from clazy, though it got confused by a few namespace issues.
2021-02-25 13:48:11 +00:00
QSignalSpy announced(&registry, &KWayland::Client::Registry::outputAnnounced);
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
registry.create(m_connection->display());
[kwin_wayland] Move Wayland::Output into dedicated source files At the same time adding an autotest for the Output, moving the listener into the Output class and providing enums for Subpixel and Transform. KWin now requires wl_ouput interface version 2 as that allows us to emit the changed signal in a better way. The unit test is not yet capable of testing everything, we need a mock Wayland server which is more flexible.
2014-08-19 14:08:02 +00:00
QVERIFY(registry.isValid());
registry.setup();
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
wl_display_flush(m_connection->display());
[kwin_wayland] Move Wayland::Output into dedicated source files At the same time adding an autotest for the Output, moving the listener into the Output class and providing enums for Subpixel and Transform. KWin now requires wl_ouput interface version 2 as that allows us to emit the changed signal in a better way. The unit test is not yet capable of testing everything, we need a mock Wayland server which is more flexible.
2014-08-19 14:08:02 +00:00
QVERIFY(announced.wait());
Use namespace KWayland::Client instead of KWin::WaylandServer It's no longer part of KWin.
2014-09-17 14:17:26 +00:00
KWayland::Client::Output output;
[kwin_wayland] Move Wayland::Output into dedicated source files At the same time adding an autotest for the Output, moving the listener into the Output class and providing enums for Subpixel and Transform. KWin now requires wl_ouput interface version 2 as that allows us to emit the changed signal in a better way. The unit test is not yet capable of testing everything, we need a mock Wayland server which is more flexible.
2014-08-19 14:08:02 +00:00
QVERIFY(!output.isValid());
QCOMPARE(output.geometry(), QRect());
QCOMPARE(output.globalPosition(), QPoint());
QCOMPARE(output.manufacturer(), QString());
QCOMPARE(output.model(), QString());
QCOMPARE(output.physicalSize(), QSize());
QCOMPARE(output.pixelSize(), QSize());
QCOMPARE(output.refreshRate(), 0);
QCOMPARE(output.scale(), 1);
Use namespace KWayland::Client instead of KWin::WaylandServer It's no longer part of KWin.
2014-09-17 14:17:26 +00:00
QCOMPARE(output.subPixel(), KWayland::Client::Output::SubPixel::Unknown);
QCOMPARE(output.transform(), KWayland::Client::Output::Transform::Normal);
[kwin_wayland] Move Wayland::Output into dedicated source files At the same time adding an autotest for the Output, moving the listener into the Output class and providing enums for Subpixel and Transform. KWin now requires wl_ouput interface version 2 as that allows us to emit the changed signal in a better way. The unit test is not yet capable of testing everything, we need a mock Wayland server which is more flexible.
2014-08-19 14:08:02 +00:00
Port all connects This is mostly all automatic from clazy, though it got confused by a few namespace issues.
2021-02-25 13:48:11 +00:00
QSignalSpy outputChanged(&output, &KWayland::Client::Output::changed);
[kwin_wayland] Move Wayland::Output into dedicated source files At the same time adding an autotest for the Output, moving the listener into the Output class and providing enums for Subpixel and Transform. KWin now requires wl_ouput interface version 2 as that allows us to emit the changed signal in a better way. The unit test is not yet capable of testing everything, we need a mock Wayland server which is more flexible.
2014-08-19 14:08:02 +00:00
QVERIFY(outputChanged.isValid());
[client] Track all created Outputs and add static get method Summary: This change starts to track all Outputs and introduces a static method to get an Output* for a wl_output* in case the wl_output* is known to Output. This is needed for the enter and leave events on wl_surface. Reviewers: #plasma_on_wayland Subscribers: plasma-devel Tags: #plasma_on_wayland Differential Revision: https://phabricator.kde.org/D2526
2016-08-22 08:02:28 +00:00
auto o = registry.bindOutput(announced.first().first().value<quint32>(), announced.first().last().value<quint32>());
QVERIFY(!KWayland::Client::Output::get(o));
output.setup(o);
QCOMPARE(KWayland::Client::Output::get(o), &output);
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
wl_display_flush(m_connection->display());
[kwin_wayland] Move Wayland::Output into dedicated source files At the same time adding an autotest for the Output, moving the listener into the Output class and providing enums for Subpixel and Transform. KWin now requires wl_ouput interface version 2 as that allows us to emit the changed signal in a better way. The unit test is not yet capable of testing everything, we need a mock Wayland server which is more flexible.
2014-08-19 14:08:02 +00:00
QVERIFY(outputChanged.wait());
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
QCOMPARE(output.geometry(), QRect(100, 50, 1024, 768));
QCOMPARE(output.globalPosition(), QPoint(100, 50));
QCOMPARE(output.manufacturer(), QStringLiteral("org.kde.kwin"));
[kwin_wayland] Move Wayland::Output into dedicated source files At the same time adding an autotest for the Output, moving the listener into the Output class and providing enums for Subpixel and Transform. KWin now requires wl_ouput interface version 2 as that allows us to emit the changed signal in a better way. The unit test is not yet capable of testing everything, we need a mock Wayland server which is more flexible.
2014-08-19 14:08:02 +00:00
QCOMPARE(output.model(), QStringLiteral("none"));
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
QCOMPARE(output.physicalSize(), QSize(200, 100));
[kwin_wayland] Move Wayland::Output into dedicated source files At the same time adding an autotest for the Output, moving the listener into the Output class and providing enums for Subpixel and Transform. KWin now requires wl_ouput interface version 2 as that allows us to emit the changed signal in a better way. The unit test is not yet capable of testing everything, we need a mock Wayland server which is more flexible.
2014-08-19 14:08:02 +00:00
QCOMPARE(output.pixelSize(), QSize(1024, 768));
QCOMPARE(output.refreshRate(), 60000);
QCOMPARE(output.scale(), 1);
// for xwayland output it's unknown
Use namespace KWayland::Client instead of KWin::WaylandServer It's no longer part of KWin.
2014-09-17 14:17:26 +00:00
QCOMPARE(output.subPixel(), KWayland::Client::Output::SubPixel::Unknown);
[kwin_wayland] Move Wayland::Output into dedicated source files At the same time adding an autotest for the Output, moving the listener into the Output class and providing enums for Subpixel and Transform. KWin now requires wl_ouput interface version 2 as that allows us to emit the changed signal in a better way. The unit test is not yet capable of testing everything, we need a mock Wayland server which is more flexible.
2014-08-19 14:08:02 +00:00
// for xwayland transform is normal
Use namespace KWayland::Client instead of KWin::WaylandServer It's no longer part of KWin.
2014-09-17 14:17:26 +00:00
QCOMPARE(output.transform(), KWayland::Client::Output::Transform::Normal);
[kwin_wayland] Move Wayland::Output into dedicated source files At the same time adding an autotest for the Output, moving the listener into the Output class and providing enums for Subpixel and Transform. KWin now requires wl_ouput interface version 2 as that allows us to emit the changed signal in a better way. The unit test is not yet capable of testing everything, we need a mock Wayland server which is more flexible.
2014-08-19 14:08:02 +00:00
}
Send only current wl_output mode Non-current output modes were deprecated due to various reasons, e.g. it's not possible to remove some nodes; two modes can have the same resolution and the refresh rate but different flags, but wl_output.mode fails to communicate that properly; the usefulness of non-current modes is questionable. For more details, please refer to [1]. [1] https://gitlab.freedesktop.org/wayland/wayland/-/issues/92
2021-04-04 17:05:10 +00:00
void TestWaylandOutput::testModeChange()
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
{
Add support for Modes in Output
2014-09-23 13:56:13 +00:00
using namespace KWayland::Client;
Use namespace KWayland::Client instead of KWin::WaylandServer It's no longer part of KWin.
2014-09-17 14:17:26 +00:00
KWayland::Client::Registry registry;
Port all connects This is mostly all automatic from clazy, though it got confused by a few namespace issues.
2021-02-25 13:48:11 +00:00
QSignalSpy announced(&registry, &KWayland::Client::Registry::outputAnnounced);
[autotest] Make TestWaylandOutput more robust If we use a thread for the connection we should also have an EventQueue.
2015-05-12 11:16:57 +00:00
registry.setEventQueue(m_queue);
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
registry.create(m_connection->display());
QVERIFY(registry.isValid());
registry.setup();
wl_display_flush(m_connection->display());
QVERIFY(announced.wait());
Use namespace KWayland::Client instead of KWin::WaylandServer It's no longer part of KWin.
2014-09-17 14:17:26 +00:00
KWayland::Client::Output output;
Port all connects This is mostly all automatic from clazy, though it got confused by a few namespace issues.
2021-02-25 13:48:11 +00:00
QSignalSpy outputChanged(&output, &KWayland::Client::Output::changed);
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
QVERIFY(outputChanged.isValid());
Port all connects This is mostly all automatic from clazy, though it got confused by a few namespace issues.
2021-02-25 13:48:11 +00:00
QSignalSpy modeAddedSpy(&output, &KWayland::Client::Output::modeAdded);
Add support for Modes in Output
2014-09-23 13:56:13 +00:00
QVERIFY(modeAddedSpy.isValid());
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
output.setup(registry.bindOutput(announced.first().first().value<quint32>(), announced.first().last().value<quint32>()));
wl_display_flush(m_connection->display());
QVERIFY(outputChanged.wait());
Send only current wl_output mode Non-current output modes were deprecated due to various reasons, e.g. it's not possible to remove some nodes; two modes can have the same resolution and the refresh rate but different flags, but wl_output.mode fails to communicate that properly; the usefulness of non-current modes is questionable. For more details, please refer to [1]. [1] https://gitlab.freedesktop.org/wayland/wayland/-/issues/92
2021-04-04 17:05:10 +00:00
QCOMPARE(modeAddedSpy.count(), 1);
QCOMPARE(modeAddedSpy.at(0).first().value<Output::Mode>().size, QSize(1024, 768));
Add support for Modes in Output
2014-09-23 13:56:13 +00:00
QCOMPARE(modeAddedSpy.at(0).first().value<Output::Mode>().refreshRate, 60000);
Send only current wl_output mode Non-current output modes were deprecated due to various reasons, e.g. it's not possible to remove some nodes; two modes can have the same resolution and the refresh rate but different flags, but wl_output.mode fails to communicate that properly; the usefulness of non-current modes is questionable. For more details, please refer to [1]. [1] https://gitlab.freedesktop.org/wayland/wayland/-/issues/92
2021-04-04 17:05:10 +00:00
QCOMPARE(modeAddedSpy.at(0).first().value<Output::Mode>().flags, Output::Mode::Flags(Output::Mode::Flag::Current));
Add support for Modes in Output
2014-09-23 13:56:13 +00:00
QCOMPARE(modeAddedSpy.at(0).first().value<Output::Mode>().output, QPointer<Output>(&output));
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
QCOMPARE(output.pixelSize(), QSize(1024, 768));
Send only current wl_output mode Non-current output modes were deprecated due to various reasons, e.g. it's not possible to remove some nodes; two modes can have the same resolution and the refresh rate but different flags, but wl_output.mode fails to communicate that properly; the usefulness of non-current modes is questionable. For more details, please refer to [1]. [1] https://gitlab.freedesktop.org/wayland/wayland/-/issues/92
2021-04-04 17:05:10 +00:00
QCOMPARE(output.refreshRate(), 60000);
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
// change once more
Send only current wl_output mode Non-current output modes were deprecated due to various reasons, e.g. it's not possible to remove some nodes; two modes can have the same resolution and the refresh rate but different flags, but wl_output.mode fails to communicate that properly; the usefulness of non-current modes is questionable. For more details, please refer to [1]. [1] https://gitlab.freedesktop.org/wayland/wayland/-/issues/92
2021-04-04 17:05:10 +00:00
m_serverOutput->setMode(QSize(1280, 1024), 90000);
[autotests] Extend test for OutputInterface Just adds more test conditions to the already existing test.
2016-06-13 17:19:06 +00:00
QCOMPARE(m_serverOutput->refreshRate(), 90000);
Add explicit done to OutputInterface and deprecate zxdg_output_v1.done if version 3 is used. In zxdg_output_v1 version 3, done is deprecated and should be replaced with wl_output.done. This makes automatically send done upon change not suitable for the usage. OutputInterface user should now use done() explicitly to send the update. CCBUG: 433224
2021-03-18 01:14:44 +00:00
m_serverOutput->done();
Send only current wl_output mode Non-current output modes were deprecated due to various reasons, e.g. it's not possible to remove some nodes; two modes can have the same resolution and the refresh rate but different flags, but wl_output.mode fails to communicate that properly; the usefulness of non-current modes is questionable. For more details, please refer to [1]. [1] https://gitlab.freedesktop.org/wayland/wayland/-/issues/92
2021-04-04 17:05:10 +00:00
QVERIFY(outputChanged.wait());
QCOMPARE(modeAddedSpy.count(), 2);
QCOMPARE(modeAddedSpy.at(1).first().value<Output::Mode>().size, QSize(1280, 1024));
QCOMPARE(modeAddedSpy.at(1).first().value<Output::Mode>().refreshRate, 90000);
QCOMPARE(modeAddedSpy.at(1).first().value<Output::Mode>().flags, Output::Mode::Flags(Output::Mode::Flag::Current));
QCOMPARE(modeAddedSpy.at(1).first().value<Output::Mode>().output, QPointer<Output>(&output));
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
QCOMPARE(output.pixelSize(), QSize(1280, 1024));
Send only current wl_output mode Non-current output modes were deprecated due to various reasons, e.g. it's not possible to remove some nodes; two modes can have the same resolution and the refresh rate but different flags, but wl_output.mode fails to communicate that properly; the usefulness of non-current modes is questionable. For more details, please refer to [1]. [1] https://gitlab.freedesktop.org/wayland/wayland/-/issues/92
2021-04-04 17:05:10 +00:00
QCOMPARE(output.refreshRate(), 90000);
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
}
void TestWaylandOutput::testScaleChange()
{
Use namespace KWayland::Client instead of KWin::WaylandServer It's no longer part of KWin.
2014-09-17 14:17:26 +00:00
KWayland::Client::Registry registry;
Port all connects This is mostly all automatic from clazy, though it got confused by a few namespace issues.
2021-02-25 13:48:11 +00:00
QSignalSpy announced(&registry, &KWayland::Client::Registry::outputAnnounced);
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
registry.create(m_connection->display());
QVERIFY(registry.isValid());
registry.setup();
wl_display_flush(m_connection->display());
QVERIFY(announced.wait());
Use namespace KWayland::Client instead of KWin::WaylandServer It's no longer part of KWin.
2014-09-17 14:17:26 +00:00
KWayland::Client::Output output;
Port all connects This is mostly all automatic from clazy, though it got confused by a few namespace issues.
2021-02-25 13:48:11 +00:00
QSignalSpy outputChanged(&output, &KWayland::Client::Output::changed);
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
QVERIFY(outputChanged.isValid());
output.setup(registry.bindOutput(announced.first().first().value<quint32>(), announced.first().last().value<quint32>()));
wl_display_flush(m_connection->display());
QVERIFY(outputChanged.wait());
QCOMPARE(output.scale(), 1);
// change the scale
outputChanged.clear();
[autotests] Extend test for OutputInterface Just adds more test conditions to the already existing test.
2016-06-13 17:19:06 +00:00
QCOMPARE(m_serverOutput->scale(), 1);
Port namespaces and includes
2020-04-29 14:56:38 +00:00
QSignalSpy serverScaleChanged(m_serverOutput, &KWaylandServer::OutputInterface::scaleChanged);
[autotests] Extend test for OutputInterface Just adds more test conditions to the already existing test.
2016-06-13 17:19:06 +00:00
QVERIFY(serverScaleChanged.isValid());
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
m_serverOutput->setScale(2);
[autotests] Extend test for OutputInterface Just adds more test conditions to the already existing test.
2016-06-13 17:19:06 +00:00
QCOMPARE(m_serverOutput->scale(), 2);
Add explicit done to OutputInterface and deprecate zxdg_output_v1.done if version 3 is used. In zxdg_output_v1 version 3, done is deprecated and should be replaced with wl_output.done. This makes automatically send done upon change not suitable for the usage. OutputInterface user should now use done() explicitly to send the update. CCBUG: 433224
2021-03-18 01:14:44 +00:00
m_serverOutput->done();
[autotests] Extend test for OutputInterface Just adds more test conditions to the already existing test.
2016-06-13 17:19:06 +00:00
QCOMPARE(serverScaleChanged.count(), 1);
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
QVERIFY(outputChanged.wait());
QCOMPARE(output.scale(), 2);
[autotests] Extend test for OutputInterface Just adds more test conditions to the already existing test.
2016-06-13 17:19:06 +00:00
// changing to same value should not trigger
m_serverOutput->setScale(2);
QCOMPARE(serverScaleChanged.count(), 1);
QVERIFY(!outputChanged.wait(100));
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
// change once more
outputChanged.clear();
m_serverOutput->setScale(4);
Add explicit done to OutputInterface and deprecate zxdg_output_v1.done if version 3 is used. In zxdg_output_v1 version 3, done is deprecated and should be replaced with wl_output.done. This makes automatically send done upon change not suitable for the usage. OutputInterface user should now use done() explicitly to send the update. CCBUG: 433224
2021-03-18 01:14:44 +00:00
m_serverOutput->done();
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
QVERIFY(outputChanged.wait());
QCOMPARE(output.scale(), 4);
}
void TestWaylandOutput::testSubPixel_data()
{
Use namespace KWayland::Client instead of KWin::WaylandServer It's no longer part of KWin.
2014-09-17 14:17:26 +00:00
using namespace KWayland::Client;
Port namespaces and includes
2020-04-29 14:56:38 +00:00
using namespace KWaylandServer;
Use namespace KWayland::Client instead of KWin::WaylandServer It's no longer part of KWin.
2014-09-17 14:17:26 +00:00
QTest::addColumn<KWayland::Client::Output::SubPixel>("expected");
Port namespaces and includes
2020-04-29 14:56:38 +00:00
QTest::addColumn<KWaylandServer::OutputInterface::SubPixel>("actual");
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
QTest::newRow("none") << Output::SubPixel::None << OutputInterface::SubPixel::None;
QTest::newRow("horizontal/rgb") << Output::SubPixel::HorizontalRGB << OutputInterface::SubPixel::HorizontalRGB;
QTest::newRow("horizontal/bgr") << Output::SubPixel::HorizontalBGR << OutputInterface::SubPixel::HorizontalBGR;
QTest::newRow("vertical/rgb") << Output::SubPixel::VerticalRGB << OutputInterface::SubPixel::VerticalRGB;
QTest::newRow("vertical/bgr") << Output::SubPixel::VerticalBGR << OutputInterface::SubPixel::VerticalBGR;
}
void TestWaylandOutput::testSubPixel()
{
Use namespace KWayland::Client instead of KWin::WaylandServer It's no longer part of KWin.
2014-09-17 14:17:26 +00:00
using namespace KWayland::Client;
Port namespaces and includes
2020-04-29 14:56:38 +00:00
using namespace KWaylandServer;
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
QFETCH(OutputInterface::SubPixel, actual);
[autotests] Extend test for OutputInterface Just adds more test conditions to the already existing test.
2016-06-13 17:19:06 +00:00
QCOMPARE(m_serverOutput->subPixel(), OutputInterface::SubPixel::Unknown);
QSignalSpy serverSubPixelChangedSpy(m_serverOutput, &OutputInterface::subPixelChanged);
QVERIFY(serverSubPixelChangedSpy.isValid());
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
m_serverOutput->setSubPixel(actual);
[autotests] Extend test for OutputInterface Just adds more test conditions to the already existing test.
2016-06-13 17:19:06 +00:00
QCOMPARE(m_serverOutput->subPixel(), actual);
QCOMPARE(serverSubPixelChangedSpy.count(), 1);
// changing to same value should not trigger the signal
m_serverOutput->setSubPixel(actual);
QCOMPARE(serverSubPixelChangedSpy.count(), 1);
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
Use namespace KWayland::Client instead of KWin::WaylandServer It's no longer part of KWin.
2014-09-17 14:17:26 +00:00
KWayland::Client::Registry registry;
Port all connects This is mostly all automatic from clazy, though it got confused by a few namespace issues.
2021-02-25 13:48:11 +00:00
QSignalSpy announced(&registry, &KWayland::Client::Registry::outputAnnounced);
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
registry.create(m_connection->display());
QVERIFY(registry.isValid());
registry.setup();
wl_display_flush(m_connection->display());
QVERIFY(announced.wait());
Use namespace KWayland::Client instead of KWin::WaylandServer It's no longer part of KWin.
2014-09-17 14:17:26 +00:00
KWayland::Client::Output output;
Port all connects This is mostly all automatic from clazy, though it got confused by a few namespace issues.
2021-02-25 13:48:11 +00:00
QSignalSpy outputChanged(&output, &KWayland::Client::Output::changed);
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
QVERIFY(outputChanged.isValid());
output.setup(registry.bindOutput(announced.first().first().value<quint32>(), announced.first().last().value<quint32>()));
wl_display_flush(m_connection->display());
if (outputChanged.isEmpty()) {
QVERIFY(outputChanged.wait());
}
QTEST(output.subPixel(), "expected");
// change back to unknown
outputChanged.clear();
m_serverOutput->setSubPixel(OutputInterface::SubPixel::Unknown);
[autotests] Extend test for OutputInterface Just adds more test conditions to the already existing test.
2016-06-13 17:19:06 +00:00
QCOMPARE(m_serverOutput->subPixel(), OutputInterface::SubPixel::Unknown);
Add explicit done to OutputInterface and deprecate zxdg_output_v1.done if version 3 is used. In zxdg_output_v1 version 3, done is deprecated and should be replaced with wl_output.done. This makes automatically send done upon change not suitable for the usage. OutputInterface user should now use done() explicitly to send the update. CCBUG: 433224
2021-03-18 01:14:44 +00:00
m_serverOutput->done();
[autotests] Extend test for OutputInterface Just adds more test conditions to the already existing test.
2016-06-13 17:19:06 +00:00
QCOMPARE(serverSubPixelChangedSpy.count(), 2);
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
if (outputChanged.isEmpty()) {
QVERIFY(outputChanged.wait());
}
QCOMPARE(output.subPixel(), Output::SubPixel::Unknown);
}
void TestWaylandOutput::testTransform_data()
{
Use namespace KWayland::Client instead of KWin::WaylandServer It's no longer part of KWin.
2014-09-17 14:17:26 +00:00
using namespace KWayland::Client;
Port namespaces and includes
2020-04-29 14:56:38 +00:00
using namespace KWaylandServer;
Use namespace KWayland::Client instead of KWin::WaylandServer It's no longer part of KWin.
2014-09-17 14:17:26 +00:00
QTest::addColumn<KWayland::Client::Output::Transform>("expected");
Port namespaces and includes
2020-04-29 14:56:38 +00:00
QTest::addColumn<KWaylandServer::OutputInterface::Transform>("actual");
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
QTest::newRow("90") << Output::Transform::Rotated90 << OutputInterface::Transform::Rotated90;
QTest::newRow("180") << Output::Transform::Rotated180 << OutputInterface::Transform::Rotated180;
QTest::newRow("270") << Output::Transform::Rotated270 << OutputInterface::Transform::Rotated270;
QTest::newRow("Flipped") << Output::Transform::Flipped << OutputInterface::Transform::Flipped;
QTest::newRow("Flipped 90") << Output::Transform::Flipped90 << OutputInterface::Transform::Flipped90;
QTest::newRow("Flipped 180") << Output::Transform::Flipped180 << OutputInterface::Transform::Flipped180;
QTest::newRow("Flipped 280") << Output::Transform::Flipped270 << OutputInterface::Transform::Flipped270;
}
void TestWaylandOutput::testTransform()
{
Use namespace KWayland::Client instead of KWin::WaylandServer It's no longer part of KWin.
2014-09-17 14:17:26 +00:00
using namespace KWayland::Client;
Port namespaces and includes
2020-04-29 14:56:38 +00:00
using namespace KWaylandServer;
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
QFETCH(OutputInterface::Transform, actual);
[autotests] Extend test for OutputInterface Just adds more test conditions to the already existing test.
2016-06-13 17:19:06 +00:00
QCOMPARE(m_serverOutput->transform(), OutputInterface::Transform::Normal);
QSignalSpy serverTransformChangedSpy(m_serverOutput, &OutputInterface::transformChanged);
QVERIFY(serverTransformChangedSpy.isValid());
m_serverOutput->setTransform(actual);
QCOMPARE(m_serverOutput->transform(), actual);
QCOMPARE(serverTransformChangedSpy.count(), 1);
// changing to same should not trigger signal
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
m_serverOutput->setTransform(actual);
[autotests] Extend test for OutputInterface Just adds more test conditions to the already existing test.
2016-06-13 17:19:06 +00:00
QCOMPARE(serverTransformChangedSpy.count(), 1);
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
Use namespace KWayland::Client instead of KWin::WaylandServer It's no longer part of KWin.
2014-09-17 14:17:26 +00:00
KWayland::Client::Registry registry;
Port all connects This is mostly all automatic from clazy, though it got confused by a few namespace issues.
2021-02-25 13:48:11 +00:00
QSignalSpy announced(&registry, &KWayland::Client::Registry::outputAnnounced);
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
registry.create(m_connection->display());
QVERIFY(registry.isValid());
registry.setup();
wl_display_flush(m_connection->display());
QVERIFY(announced.wait());
Add convenient create methods to Registry These methods allow to create the Interface objects and set them up directly.
2014-09-19 08:42:44 +00:00
KWayland::Client::Output *output = registry.createOutput(announced.first().first().value<quint32>(), announced.first().last().value<quint32>(), &registry);
Port all connects This is mostly all automatic from clazy, though it got confused by a few namespace issues.
2021-02-25 13:48:11 +00:00
QSignalSpy outputChanged(output, &KWayland::Client::Output::changed);
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
QVERIFY(outputChanged.isValid());
wl_display_flush(m_connection->display());
if (outputChanged.isEmpty()) {
QVERIFY(outputChanged.wait());
}
Add convenient create methods to Registry These methods allow to create the Interface objects and set them up directly.
2014-09-19 08:42:44 +00:00
QTEST(output->transform(), "expected");
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
// change back to normal
outputChanged.clear();
m_serverOutput->setTransform(OutputInterface::Transform::Normal);
[autotests] Extend test for OutputInterface Just adds more test conditions to the already existing test.
2016-06-13 17:19:06 +00:00
QCOMPARE(m_serverOutput->transform(), OutputInterface::Transform::Normal);
Add explicit done to OutputInterface and deprecate zxdg_output_v1.done if version 3 is used. In zxdg_output_v1 version 3, done is deprecated and should be replaced with wl_output.done. This makes automatically send done upon change not suitable for the usage. OutputInterface user should now use done() explicitly to send the update. CCBUG: 433224
2021-03-18 01:14:44 +00:00
m_serverOutput->done();
[autotests] Extend test for OutputInterface Just adds more test conditions to the already existing test.
2016-06-13 17:19:06 +00:00
QCOMPARE(serverTransformChangedSpy.count(), 2);
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
if (outputChanged.isEmpty()) {
QVERIFY(outputChanged.wait());
}
Add convenient create methods to Registry These methods allow to create the Interface objects and set them up directly.
2014-09-19 08:42:44 +00:00
QCOMPARE(output->transform(), Output::Transform::Normal);
[kwin_wayland] Initial addition of the WaylandServer module So far this new module contains: * Display * OutputInterface Display manages the server socket and server event loop. In general it's the entry point to any part of the server. OutputInterface is the abstraction for the wl_output interface on server side. An OutputInterface is created through the Display. The auto tests for ConnectionThread and Output are adjusted to use the internal server instead of starting Weston. Especially the Output test could be extended to test much more as we have absolute control over the server now.
2014-08-26 14:07:39 +00:00
}
[autotests] Extend tests for Dpms REVIEW: 125018
2015-09-01 12:02:38 +00:00
void TestWaylandOutput::testDpms_data()
{
using namespace KWayland::Client;
Port namespaces and includes
2020-04-29 14:56:38 +00:00
using namespace KWaylandServer;
[autotests] Extend tests for Dpms REVIEW: 125018
2015-09-01 12:02:38 +00:00
QTest::addColumn<KWayland::Client::Dpms::Mode>("client");
Port namespaces and includes
2020-04-29 14:56:38 +00:00
QTest::addColumn<KWaylandServer::OutputInterface::DpmsMode>("server");
[autotests] Extend tests for Dpms REVIEW: 125018
2015-09-01 12:02:38 +00:00
QTest::newRow("Standby") << Dpms::Mode::Standby << OutputInterface::DpmsMode::Standby;
QTest::newRow("Suspend") << Dpms::Mode::Suspend << OutputInterface::DpmsMode::Suspend;
Fix test after OutputInterface: Initialize output in Off state ctest passes again
2020-05-19 13:11:27 +00:00
QTest::newRow("On") << Dpms::Mode::On << OutputInterface::DpmsMode::On;
[autotests] Extend tests for Dpms REVIEW: 125018
2015-09-01 12:02:38 +00:00
}
void TestWaylandOutput::testDpms()
{
using namespace KWayland::Client;
Port namespaces and includes
2020-04-29 14:56:38 +00:00
using namespace KWaylandServer;
[autotests] Extend tests for Dpms REVIEW: 125018
2015-09-01 12:02:38 +00:00
Fix leak in test Unregister an interface when we're done with it. This also ensures we don't have several running in parallel as well.
2021-04-22 15:31:26 +00:00
DpmsManagerInterface iface(m_display);
[autotests] Extend tests for Dpms REVIEW: 125018
2015-09-01 12:02:38 +00:00
// set Dpms on the Output
QSignalSpy serverDpmsSupportedChangedSpy(m_serverOutput, &OutputInterface::dpmsSupportedChanged);
QVERIFY(serverDpmsSupportedChangedSpy.isValid());
QCOMPARE(m_serverOutput->isDpmsSupported(), false);
m_serverOutput->setDpmsSupported(true);
QCOMPARE(serverDpmsSupportedChangedSpy.count(), 1);
QCOMPARE(m_serverOutput->isDpmsSupported(), true);
KWayland::Client::Registry registry;
registry.setEventQueue(m_queue);
QSignalSpy announced(&registry, &Registry::interfacesAnnounced);
QVERIFY(announced.isValid());
QSignalSpy dpmsAnnouncedSpy(&registry, &Registry::dpmsAnnounced);
QVERIFY(dpmsAnnouncedSpy.isValid());
registry.create(m_connection->display());
QVERIFY(registry.isValid());
registry.setup();
m_connection->flush();
QVERIFY(announced.wait());
QCOMPARE(dpmsAnnouncedSpy.count(), 1);
Output *output = registry.createOutput(registry.interface(Registry::Interface::Output).name, registry.interface(Registry::Interface::Output).version, &registry);
DpmsManager *dpmsManager = registry.createDpmsManager(dpmsAnnouncedSpy.first().first().value<quint32>(), dpmsAnnouncedSpy.first().last().value<quint32>(), &registry);
QVERIFY(dpmsManager->isValid());
Dpms *dpms = dpmsManager->getDpms(output, &registry);
QSignalSpy clientDpmsSupportedChangedSpy(dpms, &Dpms::supportedChanged);
QVERIFY(clientDpmsSupportedChangedSpy.isValid());
QVERIFY(dpms->isValid());
QCOMPARE(dpms->isSupported(), false);
QCOMPARE(dpms->mode(), Dpms::Mode::On);
m_connection->flush();
QVERIFY(clientDpmsSupportedChangedSpy.wait());
QCOMPARE(clientDpmsSupportedChangedSpy.count(), 1);
QCOMPARE(dpms->isSupported(), true);
// and let's change to suspend
QSignalSpy serverDpmsModeChangedSpy(m_serverOutput, &OutputInterface::dpmsModeChanged);
QVERIFY(serverDpmsModeChangedSpy.isValid());
QSignalSpy clientDpmsModeChangedSpy(dpms, &Dpms::modeChanged);
QVERIFY(clientDpmsModeChangedSpy.isValid());
Fix test after OutputInterface: Initialize output in Off state ctest passes again
2020-05-19 13:11:27 +00:00
QCOMPARE(m_serverOutput->dpmsMode(), OutputInterface::DpmsMode::Off);
[autotests] Extend tests for Dpms REVIEW: 125018
2015-09-01 12:02:38 +00:00
QFETCH(OutputInterface::DpmsMode, server);
m_serverOutput->setDpmsMode(server);
QCOMPARE(m_serverOutput->dpmsMode(), server);
QCOMPARE(serverDpmsModeChangedSpy.count(), 1);
QVERIFY(clientDpmsModeChangedSpy.wait());
QCOMPARE(clientDpmsModeChangedSpy.count(), 1);
QTEST(dpms->mode(), "client");
[autotest] Extend tests for Dpms modes Summary: Now also tests: * requesting mode from client side * update supported change on server side Reviewers: #plasma Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1357
2016-04-08 09:42:51 +00:00
// test supported changed
QSignalSpy supportedChangedSpy(dpms, &Dpms::supportedChanged);
QVERIFY(supportedChangedSpy.isValid());
m_serverOutput->setDpmsSupported(false);
QVERIFY(supportedChangedSpy.wait());
QCOMPARE(supportedChangedSpy.count(), 1);
QVERIFY(!dpms->isSupported());
m_serverOutput->setDpmsSupported(true);
QVERIFY(supportedChangedSpy.wait());
QCOMPARE(supportedChangedSpy.count(), 2);
QVERIFY(dpms->isSupported());
Fix test after OutputInterface: Initialize output in Off state ctest passes again
2020-05-19 13:11:27 +00:00
// and switch back to off
m_serverOutput->setDpmsMode(OutputInterface::DpmsMode::Off);
[autotest] Extend tests for Dpms modes Summary: Now also tests: * requesting mode from client side * update supported change on server side Reviewers: #plasma Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1357
2016-04-08 09:42:51 +00:00
QVERIFY(clientDpmsModeChangedSpy.wait());
QCOMPARE(clientDpmsModeChangedSpy.count(), 2);
Fix test after OutputInterface: Initialize output in Off state ctest passes again
2020-05-19 13:11:27 +00:00
QCOMPARE(dpms->mode(), Dpms::Mode::Off);
[autotest] Extend tests for Dpms modes Summary: Now also tests: * requesting mode from client side * update supported change on server side Reviewers: #plasma Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1357
2016-04-08 09:42:51 +00:00
}
void TestWaylandOutput::testDpmsRequestMode_data()
{
using namespace KWayland::Client;
Port namespaces and includes
2020-04-29 14:56:38 +00:00
using namespace KWaylandServer;
[autotest] Extend tests for Dpms modes Summary: Now also tests: * requesting mode from client side * update supported change on server side Reviewers: #plasma Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1357
2016-04-08 09:42:51 +00:00
QTest::addColumn<KWayland::Client::Dpms::Mode>("client");
Port namespaces and includes
2020-04-29 14:56:38 +00:00
QTest::addColumn<KWaylandServer::OutputInterface::DpmsMode>("server");
[autotest] Extend tests for Dpms modes Summary: Now also tests: * requesting mode from client side * update supported change on server side Reviewers: #plasma Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1357
2016-04-08 09:42:51 +00:00
QTest::newRow("Standby") << Dpms::Mode::Standby << OutputInterface::DpmsMode::Standby;
QTest::newRow("Suspend") << Dpms::Mode::Suspend << OutputInterface::DpmsMode::Suspend;
QTest::newRow("Off") << Dpms::Mode::Off << OutputInterface::DpmsMode::Off;
QTest::newRow("On") << Dpms::Mode::On << OutputInterface::DpmsMode::On;
}
void TestWaylandOutput::testDpmsRequestMode()
{
// this test verifies that requesting a dpms change from client side emits the signal on server side
using namespace KWayland::Client;
Port namespaces and includes
2020-04-29 14:56:38 +00:00
using namespace KWaylandServer;
[autotest] Extend tests for Dpms modes Summary: Now also tests: * requesting mode from client side * update supported change on server side Reviewers: #plasma Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1357
2016-04-08 09:42:51 +00:00
// setup code
Fix leak in test Unregister an interface when we're done with it. This also ensures we don't have several running in parallel as well.
2021-04-22 15:31:26 +00:00
DpmsManagerInterface iface(m_display);
[autotest] Extend tests for Dpms modes Summary: Now also tests: * requesting mode from client side * update supported change on server side Reviewers: #plasma Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1357
2016-04-08 09:42:51 +00:00
// set Dpms on the Output
QSignalSpy serverDpmsSupportedChangedSpy(m_serverOutput, &OutputInterface::dpmsSupportedChanged);
QVERIFY(serverDpmsSupportedChangedSpy.isValid());
QCOMPARE(m_serverOutput->isDpmsSupported(), false);
m_serverOutput->setDpmsSupported(true);
QCOMPARE(serverDpmsSupportedChangedSpy.count(), 1);
QCOMPARE(m_serverOutput->isDpmsSupported(), true);
KWayland::Client::Registry registry;
registry.setEventQueue(m_queue);
QSignalSpy announced(&registry, &Registry::interfacesAnnounced);
QVERIFY(announced.isValid());
QSignalSpy dpmsAnnouncedSpy(&registry, &Registry::dpmsAnnounced);
QVERIFY(dpmsAnnouncedSpy.isValid());
registry.create(m_connection->display());
QVERIFY(registry.isValid());
registry.setup();
m_connection->flush();
QVERIFY(announced.wait());
QCOMPARE(dpmsAnnouncedSpy.count(), 1);
Output *output = registry.createOutput(registry.interface(Registry::Interface::Output).name, registry.interface(Registry::Interface::Output).version, &registry);
DpmsManager *dpmsManager = registry.createDpmsManager(dpmsAnnouncedSpy.first().first().value<quint32>(), dpmsAnnouncedSpy.first().last().value<quint32>(), &registry);
QVERIFY(dpmsManager->isValid());
Dpms *dpms = dpmsManager->getDpms(output, &registry);
// and test request mode
QSignalSpy modeRequestedSpy(m_serverOutput, &OutputInterface::dpmsModeRequested);
QVERIFY(modeRequestedSpy.isValid());
QFETCH(Dpms::Mode, client);
dpms->requestMode(client);
QVERIFY(modeRequestedSpy.wait());
QTEST(modeRequestedSpy.last().first().value<OutputInterface::DpmsMode>(), "server");
[autotests] Extend tests for Dpms REVIEW: 125018
2015-09-01 12:02:38 +00:00
}
Switch all auto tests to QTEST_GUILESS_MAIN We don't need a QGuiApplication in the tests.
2014-09-23 10:00:17 +00:00
QTEST_GUILESS_MAIN(TestWaylandOutput)
[kwin_wayland] Move Wayland::Output into dedicated source files At the same time adding an autotest for the Output, moving the listener into the Output class and providing enums for Subpixel and Transform. KWin now requires wl_ouput interface version 2 as that allows us to emit the changed signal in a better way. The unit test is not yet capable of testing everything, we need a mock Wayland server which is more flexible.
2014-08-19 14:08:02 +00:00
#include "test_wayland_output.moc"
Reference in a new issue Copy permalink