isa/mutter
1
0
Fork 0
mirror of https://github.com/brl/mutter.git synced 2024-11-23 16:40:41 -05:00
Code Issues Packages Projects Releases Wiki Activity
67425bf653
mutter/src/tests/monitor-unit-tests.c

8925 lines
242 KiB
C
Raw Normal View History

tests: Add basic monitor configuration tests The added test checks that two monitors are lied out on a row next to each other. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-05 05:40:44 -05:00
/* -*- mode: C; c-file-style: "gnu"; indent-tabs-mode: nil; -*- */
/*
* Copyright (C) 2016 Red Hat, Inc.
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License as
* published by the Free Software Foundation; either version 2 of the
* License, or (at your option) any later version.
*
* This program is distributed in the hope that it will be useful, but
* WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, see <http://www.gnu.org/licenses/>.
*/
#include "config.h"
#include "tests/monitor-unit-tests.h"
#include "backends/meta-backend-private.h"
monitor-manager: Make MetaCrtc a GObject Turn MetaCrtc into a GObject and move it to a separate file. This changes the storage format, resulting in changing the API for accessing MetaCrtcs from using an array, to using a GList. https://bugzilla.gnome.org/show_bug.cgi?id=785381
2017-03-28 00:35:19 -04:00
#include "backends/meta-crtc.h"
monitor-manager: Move logical monitor into its own file https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-12 21:37:11 -05:00
#include "backends/meta-logical-monitor.h"
tests: Check that the monitors are properly generated https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-12 21:58:41 -05:00
#include "backends/meta-monitor.h"
tests: Add monitor config migration tests So far some basic testing, including: * Test that the migrated configuration is applicable * Test that a monitors.xml with multiple configurations are translated * Test rotation * Test tiled monitor discovery (well, test a made up tiled monitor configuration since I don't have a real one) https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-08-10 05:12:39 -04:00
#include "backends/meta-monitor-config-migration.h"
#include "backends/meta-monitor-config-store.h"
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
#include "backends/meta-orientation-manager.h"
Make MetaOutput a GObject Turn MetaOutput into a GObject and move it to a separate file. This changes the storage format, resulting in changing the API for accessing MetaOutputs from using an array, to using a GList. https://bugzilla.gnome.org/show_bug.cgi?id=785381
2017-03-24 05:35:51 -04:00
#include "backends/meta-output.h"
tests/monitor-unit-tests: Add window tiling hot plug test This test that we handle hot plugs correctly together with tiled windows. https://gitlab.gnome.org/GNOME/mutter/merge_requests/912
2019-11-01 08:38:25 -04:00
#include "core/window-private.h"
backend: Move lid-is-closed handling to MetaBackend Rather than handle UpClient in both MetaBackend (to reset the idletime when the lid is opened), and in MetaMonitorManager and MetaMonitorConfigManager (to turn the screen under the lid on/off depending on its status), move the ability to get the lid status from UPower or mock it in one place, in MetaBackend.
2018-04-16 14:07:45 -04:00
#include "meta-backend-test.h"
tests: Make monitor unit tests create initial config This way we have both the test setup and testing in the same file. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-05 08:28:22 -05:00
#include "tests/meta-monitor-manager-test.h"
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
#include "tests/meta-sensors-proxy-mock.h"
tests: Move monitor test helpers to a helper file Both the monitor unit tests and monitor store unit tests will want to check whether the config manager is used and set custom configuration files. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 22:41:05 -05:00
#include "tests/monitor-test-utils.h"
tests: Rename test-utils.c/h to meta-test-utils.c/h Otherwise it'll conflict with other files with identical filenames, if one would add src/tests/ to the include path, which will happen in a later commit. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-04-20 12:39:53 -04:00
#include "tests/meta-test-utils.h"
tests: Move 'wait-for-X11-display' helper to MetaContextTest Gets rid of a un-prefixed helper function relying on a global singleton. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-11 03:35:04 -04:00
#include "tests/unit-tests.h"
monitor-unit-tests: Also run a X11 client while testing We already ran a Wayland client to test various Wayland paths. What was missing to also run a X11 client was to hook in the X11 async waiter wires, so do that and run both types of clients. https://bugzilla.gnome.org/show_bug.cgi?id=790207
2018-02-06 02:39:06 -05:00
#include "x11/meta-x11-display-private.h"
tests: Make monitor unit tests create initial config This way we have both the test setup and testing in the same file. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-05 08:28:22 -05:00
tests: Make monitor test case setup more declarative In order to more easily create more test cases, make the test case setup more declarative. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 00:54:32 -05:00
static MonitorTestCase initial_test_case = {
.setup = {
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0
}
},
.n_modes = 1,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125
},
{
.crtc = 1,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 1 },
.n_possible_crtcs = 1,
tests: Check that the monitors are properly generated https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-12 21:58:41 -05:00
.width_mm = 220,
.height_mm = 124
tests: Make monitor test case setup more declarative In order to more easily create more test cases, make the test case setup more declarative. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 00:54:32 -05:00
}
},
.n_outputs = 2,
.crtcs = {
{
.current_mode = 0
},
{
.current_mode = 0
}
},
.n_crtcs = 2
tests: Also make test case verification declarative Set up the expected result in a declarative way in the same place as the test case setup is declared. This way we have a completely declarative way to create test cases. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 01:18:28 -05:00
},
.expect = {
tests: Check that the monitors are properly generated https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-12 21:58:41 -05:00
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
monitor-unit-tests: Check monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-14 04:23:44 -05:00
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.0,
monitor-unit-tests: Check monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-14 04:23:44 -05:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
tests/monitor-unit-tests: Check current monitor mode Check both that current mode is up to date, and that deriving it again won't change it. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-05 23:43:22 -05:00
.current_mode = 0,
tests: Check that the monitors are properly generated https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-12 21:58:41 -05:00
.width_mm = 222,
.height_mm = 125
},
{
.outputs = { 1 },
.n_outputs = 1,
monitor-unit-tests: Check monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-14 04:23:44 -05:00
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.0,
monitor-unit-tests: Check monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-14 04:23:44 -05:00
.crtc_modes = {
{
.output = 1,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
tests/monitor-unit-tests: Check current monitor mode Check both that current mode is up to date, and that deriving it again won't change it. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-05 23:43:22 -05:00
.current_mode = 0,
tests: Check that the monitors are properly generated https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-12 21:58:41 -05:00
.width_mm = 220,
.height_mm = 124
}
},
.n_monitors = 2,
tests: Also make test case verification declarative Set up the expected result in a declarative way in the same place as the test case setup is declared. This way we have a completely declarative way to create test cases. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 01:18:28 -05:00
.logical_monitors = {
{
monitor-unit-tests: Check monitor <-> logical monitor relationships Make sure that each logical monitor owns the expected actual monitors. This currently needs special care when dealing with laptop lid the configuration, as the MetaMonitorConfigManager path still deosn't handle restoring the previous configuration, meaning the logical monitor with the external monitor will continue being primary. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 01:09:55 -05:00
.monitors = { 0 },
.n_monitors = 1,
tests: Also make test case verification declarative Set up the expected result in a declarative way in the same place as the test case setup is declared. This way we have a completely declarative way to create test cases. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 01:18:28 -05:00
.layout = { .x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
},
{
monitor-unit-tests: Check monitor <-> logical monitor relationships Make sure that each logical monitor owns the expected actual monitors. This currently needs special care when dealing with laptop lid the configuration, as the MetaMonitorConfigManager path still deosn't handle restoring the previous configuration, meaning the logical monitor with the external monitor will continue being primary. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 01:09:55 -05:00
.monitors = { 1 },
.n_monitors = 1,
tests: Also make test case verification declarative Set up the expected result in a declarative way in the same place as the test case setup is declared. This way we have a completely declarative way to create test cases. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 01:18:28 -05:00
.layout = { .x = 1024, .y = 0, .width = 1024, .height = 768 },
.scale = 1
}
},
.n_logical_monitors = 2,
monitor-unit-tests: Check handling of the primary presentation flags The main output of the main (first) monitor of a primary logical monitor should have the MetaOutput::is_primary field set; all other outputs should have it not set. All outputs associated with a logical monitor with presentation set should have MetaOutput::is_presentation set. No other outputs should have it set. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 00:09:21 -05:00
.primary_logical_monitor = 0,
tests: Also make test case verification declarative Set up the expected result in a declarative way in the same place as the test case setup is declared. This way we have a completely declarative way to create test cases. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 01:18:28 -05:00
.n_outputs = 2,
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
.crtcs = {
{
.current_mode = 0,
},
{
.current_mode = 0,
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
.x = 1024,
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
}
},
tests: Also make test case verification declarative Set up the expected result in a declarative way in the same place as the test case setup is declared. This way we have a completely declarative way to create test cases. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 01:18:28 -05:00
.n_crtcs = 2,
.screen_width = 1024 * 2,
.screen_height = 768
tests: Make monitor test case setup more declarative In order to more easily create more test cases, make the test case setup more declarative. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 00:54:32 -05:00
}
};
tests: Add basic monitor configuration tests The added test checks that two monitors are lied out on a row next to each other. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-05 05:40:44 -05:00
tests/utils: Prefix TestClient with Meta Soon we'll expose it via a libmutter-test library. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-06 17:34:36 -04:00
static MetaTestClient *wayland_monitor_test_client = NULL;
static MetaTestClient *x11_monitor_test_client = NULL;
tests/monitor-unit-tests: Run a client while testing Run a client while testing and check that it's alive when checking each monitor configuration. https://bugzilla.gnome.org/show_bug.cgi?id=730551
2017-08-18 02:37:53 -04:00
monitor-unit-tests: Also run a X11 client while testing We already ran a Wayland client to test various Wayland paths. What was missing to also run a X11 client was to hook in the X11 async waiter wires, so do that and run both types of clients. https://bugzilla.gnome.org/show_bug.cgi?id=790207
2018-02-06 02:39:06 -05:00
#define WAYLAND_TEST_CLIENT_NAME "wayland_monitor_test_client"
#define WAYLAND_TEST_CLIENT_WINDOW "window1"
#define X11_TEST_CLIENT_NAME "x11_monitor_test_client"
#define X11_TEST_CLIENT_WINDOW "window1"
static gboolean
monitor_tests_alarm_filter (MetaX11Display *x11_display,
XSyncAlarmNotifyEvent *event,
gpointer data)
{
tests/utils: Prefix TestClient with Meta Soon we'll expose it via a libmutter-test library. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-06 17:34:36 -04:00
return meta_test_client_process_x11_event (x11_monitor_test_client,
x11_display, event);
monitor-unit-tests: Also run a X11 client while testing We already ran a Wayland client to test various Wayland paths. What was missing to also run a X11 client was to hook in the X11 async waiter wires, so do that and run both types of clients. https://bugzilla.gnome.org/show_bug.cgi?id=790207
2018-02-06 02:39:06 -05:00
}
tests/monitor-unit-tests: Run a client while testing Run a client while testing and check that it's alive when checking each monitor configuration. https://bugzilla.gnome.org/show_bug.cgi?id=730551
2017-08-18 02:37:53 -04:00
monitor-unit-tests: Check orientation changes with transformed panels Ensure that orientation changes still work as expected when using a panel that has some native transformation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 06:14:44 -05:00
static void
on_monitors_changed (gboolean *monitors_changed)
{
*monitors_changed = TRUE;
}
tests/monitor-unit-tests: Run a client while testing Run a client while testing and check that it's alive when checking each monitor configuration. https://bugzilla.gnome.org/show_bug.cgi?id=730551
2017-08-18 02:37:53 -04:00
static void
tests: Move 'wait-for-X11-display' helper to MetaContextTest Gets rid of a un-prefixed helper function relying on a global singleton. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-11 03:35:04 -04:00
create_monitor_test_clients (MetaContext *context)
tests/monitor-unit-tests: Run a client while testing Run a client while testing and check that it's alive when checking each monitor configuration. https://bugzilla.gnome.org/show_bug.cgi?id=730551
2017-08-18 02:37:53 -04:00
{
GError *error = NULL;
tests: Move 'wait-for-X11-display' helper to MetaContextTest Gets rid of a un-prefixed helper function relying on a global singleton. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-11 03:35:04 -04:00
wayland_monitor_test_client = meta_test_client_new (context,
WAYLAND_TEST_CLIENT_NAME,
tests/utils: Prefix TestClient with Meta Soon we'll expose it via a libmutter-test library. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-06 17:34:36 -04:00
META_WINDOW_CLIENT_TYPE_WAYLAND,
&error);
monitor-unit-tests: Also run a X11 client while testing We already ran a Wayland client to test various Wayland paths. What was missing to also run a X11 client was to hook in the X11 async waiter wires, so do that and run both types of clients. https://bugzilla.gnome.org/show_bug.cgi?id=790207
2018-02-06 02:39:06 -05:00
if (!wayland_monitor_test_client)
g_error ("Failed to launch Wayland test client: %s", error->message);
tests: Move 'wait-for-X11-display' helper to MetaContextTest Gets rid of a un-prefixed helper function relying on a global singleton. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-11 03:35:04 -04:00
x11_monitor_test_client = meta_test_client_new (context,
X11_TEST_CLIENT_NAME,
tests/utils: Prefix TestClient with Meta Soon we'll expose it via a libmutter-test library. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-06 17:34:36 -04:00
META_WINDOW_CLIENT_TYPE_X11,
&error);
monitor-unit-tests: Also run a X11 client while testing We already ran a Wayland client to test various Wayland paths. What was missing to also run a X11 client was to hook in the X11 async waiter wires, so do that and run both types of clients. https://bugzilla.gnome.org/show_bug.cgi?id=790207
2018-02-06 02:39:06 -05:00
if (!x11_monitor_test_client)
g_error ("Failed to launch X11 test client: %s", error->message);
tests/monitor-unit-tests: Set up async waiter after X11 client We'll have two persistent client connections alive for the whole test, one X11 client, and one Wayland client. So in order to be able to set up the async waiter, do so after setting up the X11 client, as after that we know we'll have a MetaX11Display ready to use. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1681>
2021-01-22 03:53:24 -05:00
meta_x11_display_set_alarm_filter (meta_get_display ()->x11_display,
monitor_tests_alarm_filter, NULL);
tests/utils: Prefix TestClient with Meta Soon we'll expose it via a libmutter-test library. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-06 17:34:36 -04:00
if (!meta_test_client_do (wayland_monitor_test_client, &error,
"create", WAYLAND_TEST_CLIENT_WINDOW,
NULL))
monitor-unit-tests: Also run a X11 client while testing We already ran a Wayland client to test various Wayland paths. What was missing to also run a X11 client was to hook in the X11 async waiter wires, so do that and run both types of clients. https://bugzilla.gnome.org/show_bug.cgi?id=790207
2018-02-06 02:39:06 -05:00
g_error ("Failed to create Wayland window: %s", error->message);
tests/utils: Prefix TestClient with Meta Soon we'll expose it via a libmutter-test library. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-06 17:34:36 -04:00
if (!meta_test_client_do (x11_monitor_test_client, &error,
"create", X11_TEST_CLIENT_WINDOW,
NULL))
monitor-unit-tests: Also run a X11 client while testing We already ran a Wayland client to test various Wayland paths. What was missing to also run a X11 client was to hook in the X11 async waiter wires, so do that and run both types of clients. https://bugzilla.gnome.org/show_bug.cgi?id=790207
2018-02-06 02:39:06 -05:00
g_error ("Failed to create X11 window: %s", error->message);
tests/monitor-unit-tests: Run a client while testing Run a client while testing and check that it's alive when checking each monitor configuration. https://bugzilla.gnome.org/show_bug.cgi?id=730551
2017-08-18 02:37:53 -04:00
tests/utils: Prefix TestClient with Meta Soon we'll expose it via a libmutter-test library. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-06 17:34:36 -04:00
if (!meta_test_client_do (wayland_monitor_test_client, &error,
"show", WAYLAND_TEST_CLIENT_WINDOW,
NULL))
monitor-unit-tests: Also run a X11 client while testing We already ran a Wayland client to test various Wayland paths. What was missing to also run a X11 client was to hook in the X11 async waiter wires, so do that and run both types of clients. https://bugzilla.gnome.org/show_bug.cgi?id=790207
2018-02-06 02:39:06 -05:00
g_error ("Failed to show the window: %s", error->message);
tests/monitor-unit-tests: Run a client while testing Run a client while testing and check that it's alive when checking each monitor configuration. https://bugzilla.gnome.org/show_bug.cgi?id=730551
2017-08-18 02:37:53 -04:00
tests/utils: Prefix TestClient with Meta Soon we'll expose it via a libmutter-test library. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-06 17:34:36 -04:00
if (!meta_test_client_do (x11_monitor_test_client, &error,
"show", X11_TEST_CLIENT_WINDOW,
NULL))
tests/monitor-unit-tests: Run a client while testing Run a client while testing and check that it's alive when checking each monitor configuration. https://bugzilla.gnome.org/show_bug.cgi?id=730551
2017-08-18 02:37:53 -04:00
g_error ("Failed to show the window: %s", error->message);
}
static void
tests/utils: Prefix TestClient with Meta Soon we'll expose it via a libmutter-test library. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-06 17:34:36 -04:00
check_test_client_state (MetaTestClient *test_client)
tests/monitor-unit-tests: Run a client while testing Run a client while testing and check that it's alive when checking each monitor configuration. https://bugzilla.gnome.org/show_bug.cgi?id=730551
2017-08-18 02:37:53 -04:00
{
GError *error = NULL;
tests/utils: Prefix TestClient with Meta Soon we'll expose it via a libmutter-test library. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-06 17:34:36 -04:00
if (!meta_test_client_wait (test_client, &error))
tests/monitor-unit-tests: Move test client sanity check into helper https://gitlab.gnome.org/GNOME/mutter/merge_requests/912
2019-11-01 08:35:38 -04:00
{
g_error ("Failed to sync test client '%s': %s",
tests/utils: Prefix TestClient with Meta Soon we'll expose it via a libmutter-test library. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-06 17:34:36 -04:00
meta_test_client_get_id (test_client), error->message);
tests/monitor-unit-tests: Move test client sanity check into helper https://gitlab.gnome.org/GNOME/mutter/merge_requests/912
2019-11-01 08:35:38 -04:00
}
}
monitor-unit-tests: Also run a X11 client while testing We already ran a Wayland client to test various Wayland paths. What was missing to also run a X11 client was to hook in the X11 async waiter wires, so do that and run both types of clients. https://bugzilla.gnome.org/show_bug.cgi?id=790207
2018-02-06 02:39:06 -05:00
tests/monitor-unit-tests: Move test client sanity check into helper https://gitlab.gnome.org/GNOME/mutter/merge_requests/912
2019-11-01 08:35:38 -04:00
static void
check_monitor_test_clients_state (void)
{
check_test_client_state (wayland_monitor_test_client);
check_test_client_state (x11_monitor_test_client);
tests/monitor-unit-tests: Run a client while testing Run a client while testing and check that it's alive when checking each monitor configuration. https://bugzilla.gnome.org/show_bug.cgi?id=730551
2017-08-18 02:37:53 -04:00
}
static void
monitor-unit-tests: Also run a X11 client while testing We already ran a Wayland client to test various Wayland paths. What was missing to also run a X11 client was to hook in the X11 async waiter wires, so do that and run both types of clients. https://bugzilla.gnome.org/show_bug.cgi?id=790207
2018-02-06 02:39:06 -05:00
destroy_monitor_test_clients (void)
tests/monitor-unit-tests: Run a client while testing Run a client while testing and check that it's alive when checking each monitor configuration. https://bugzilla.gnome.org/show_bug.cgi?id=730551
2017-08-18 02:37:53 -04:00
{
GError *error = NULL;
tests/utils: Prefix TestClient with Meta Soon we'll expose it via a libmutter-test library. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-06 17:34:36 -04:00
if (!meta_test_client_quit (wayland_monitor_test_client, &error))
monitor-unit-tests: Also run a X11 client while testing We already ran a Wayland client to test various Wayland paths. What was missing to also run a X11 client was to hook in the X11 async waiter wires, so do that and run both types of clients. https://bugzilla.gnome.org/show_bug.cgi?id=790207
2018-02-06 02:39:06 -05:00
g_error ("Failed to quit Wayland test client: %s", error->message);
tests/utils: Prefix TestClient with Meta Soon we'll expose it via a libmutter-test library. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-06 17:34:36 -04:00
if (!meta_test_client_quit (x11_monitor_test_client, &error))
monitor-unit-tests: Also run a X11 client while testing We already ran a Wayland client to test various Wayland paths. What was missing to also run a X11 client was to hook in the X11 async waiter wires, so do that and run both types of clients. https://bugzilla.gnome.org/show_bug.cgi?id=790207
2018-02-06 02:39:06 -05:00
g_error ("Failed to quit X11 test client: %s", error->message);
tests/utils: Prefix TestClient with Meta Soon we'll expose it via a libmutter-test library. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-06 17:34:36 -04:00
meta_test_client_destroy (wayland_monitor_test_client);
meta_test_client_destroy (x11_monitor_test_client);
tests/monitor-unit-tests: Run a client while testing Run a client while testing and check that it's alive when checking each monitor configuration. https://bugzilla.gnome.org/show_bug.cgi?id=730551
2017-08-18 02:37:53 -04:00
monitor-unit-tests: Also run a X11 client while testing We already ran a Wayland client to test various Wayland paths. What was missing to also run a X11 client was to hook in the X11 async waiter wires, so do that and run both types of clients. https://bugzilla.gnome.org/show_bug.cgi?id=790207
2018-02-06 02:39:06 -05:00
meta_x11_display_set_alarm_filter (meta_get_display ()->x11_display,
NULL, NULL);
tests/monitor-unit-tests: Run a client while testing Run a client while testing and check that it's alive when checking each monitor configuration. https://bugzilla.gnome.org/show_bug.cgi?id=730551
2017-08-18 02:37:53 -04:00
}
tests: Also make test case verification declarative Set up the expected result in a declarative way in the same place as the test case setup is declared. This way we have a completely declarative way to create test cases. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 01:18:28 -05:00
static void
meta_test_monitor_initial_linear_config (void)
{
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&initial_test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
tests: Also make test case verification declarative Set up the expected result in a declarative way in the same place as the test case setup is declared. This way we have a completely declarative way to create test cases. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 01:18:28 -05:00
}
tests/monitor: Test two crtcs, one output https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 02:15:25 -05:00
static void
emulate_hotplug (MetaMonitorTestSetup *test_setup)
{
MetaBackend *backend = meta_get_backend ();
MetaMonitorManager *monitor_manager =
meta_backend_get_monitor_manager (backend);
MetaMonitorManagerTest *monitor_manager_test =
META_MONITOR_MANAGER_TEST (monitor_manager);
meta_monitor_manager_test_emulate_hotplug (monitor_manager_test, test_setup);
tests/monitor-unit-tests: Sleep some after each hot plug Give clients (such as Xwayland) a chance to bind the wl_output global before we continue, otherwise there is an significant risk that mutter won't see the bind request until after the next hot plug which might have destroyed the global object. https://bugzilla.gnome.org/show_bug.cgi?id=730551
2017-08-18 02:32:02 -04:00
g_usleep (G_USEC_PER_SEC / 100);
tests/monitor: Test two crtcs, one output https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 02:15:25 -05:00
}
monitor-unit-tests: Add tests to verify config manager history Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2021-07-27 12:01:47 -04:00
static void
meta_test_monitor_config_store_set_current_on_empty (void)
{
g_autoptr (MetaMonitorsConfig) linear_config = NULL;
MetaBackend *backend = meta_get_backend ();
MetaMonitorManager *monitor_manager =
meta_backend_get_monitor_manager (backend);
MetaMonitorConfigManager *config_manager = monitor_manager->config_manager;
MetaMonitorsConfig *old_current;
linear_config = meta_monitor_config_manager_create_linear (config_manager);
old_current = meta_monitor_config_manager_get_current (config_manager);
g_assert_null (old_current);
g_assert_nonnull (linear_config);
meta_monitor_config_manager_set_current (config_manager, linear_config);
g_assert (meta_monitor_config_manager_get_current (config_manager) ==
linear_config);
g_assert (meta_monitor_config_manager_get_current (config_manager) !=
old_current);
g_assert_null (meta_monitor_config_manager_get_previous (config_manager));
g_assert_null (meta_monitor_config_manager_pop_previous (config_manager));
}
monitor-manager: Add config relationships and use it for orientation events When we get an orientation event we don't care about keeping track of the configuration changes, but actually we can consider the new configuration just a variant of the previous one, adapted to floating device hardware events, so we only want to apply it if possible, but we don't want to keep a record of it for reverting capabilities. Doing that would in fact, break the ability of reverting back to an actual temporary or persistent configuration. For example when device orientation events happen while we're waiting for an user resolution change confirmation, we would save our new rotated configuration in the history, making then impossible to revert back to the original persistent one. So in such case, don't keep track of those configurations in the history, but only keep track of the last one as current, checking whether the new current is child or sibling of the previously one. Fixes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1221 Related to: https://gitlab.gnome.org/GNOME/mutter/-/issues/646 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-01 09:53:55 -04:00
static void
meta_test_monitor_config_store_set_current_with_parent_on_empty (void)
{
g_autoptr (MetaMonitorsConfig) parent_config = NULL;
g_autoptr (MetaMonitorsConfig) child_config1 = NULL;
g_autoptr (MetaMonitorsConfig) child_config2 = NULL;
g_autoptr (MetaMonitorsConfig) child_config3 = NULL;
g_autoptr (MetaMonitorsConfig) linear_config = NULL;
g_autoptr (MetaMonitorsConfig) fallback_config = NULL;
MetaBackend *backend = meta_get_backend ();
MetaMonitorManager *monitor_manager =
meta_backend_get_monitor_manager (backend);
MetaMonitorConfigManager *config_manager = monitor_manager->config_manager;
MetaMonitorsConfig *old_current;
parent_config = meta_monitor_config_manager_create_linear (config_manager);
child_config1 = meta_monitor_config_manager_create_linear (config_manager);
meta_monitors_config_set_parent_config (child_config1, parent_config);
old_current = meta_monitor_config_manager_get_current (config_manager);
g_assert_null (old_current);
g_assert_nonnull (child_config1);
meta_monitor_config_manager_set_current (config_manager, child_config1);
g_assert (meta_monitor_config_manager_get_current (config_manager) ==
child_config1);
g_assert (meta_monitor_config_manager_get_current (config_manager) !=
old_current);
g_assert_null (meta_monitor_config_manager_get_previous (config_manager));
g_assert_null (meta_monitor_config_manager_pop_previous (config_manager));
child_config2 = meta_monitor_config_manager_create_linear (config_manager);
meta_monitors_config_set_parent_config (child_config2, parent_config);
g_assert (child_config2->parent_config == parent_config);
old_current = meta_monitor_config_manager_get_current (config_manager);
g_assert_nonnull (old_current->parent_config);
meta_monitor_config_manager_set_current (config_manager, child_config2);
g_assert (meta_monitor_config_manager_get_current (config_manager) ==
child_config2);
g_assert (meta_monitor_config_manager_get_current (config_manager) !=
old_current);
g_assert_null (meta_monitor_config_manager_get_previous (config_manager));
g_assert_null (meta_monitor_config_manager_pop_previous (config_manager));
child_config3 = meta_monitor_config_manager_create_linear (config_manager);
meta_monitors_config_set_parent_config (child_config3, child_config2);
old_current = meta_monitor_config_manager_get_current (config_manager);
g_assert_nonnull (old_current->parent_config);
meta_monitor_config_manager_set_current (config_manager, child_config3);
g_assert (meta_monitor_config_manager_get_current (config_manager) ==
child_config3);
g_assert (meta_monitor_config_manager_get_current (config_manager) !=
old_current);
g_assert_null (meta_monitor_config_manager_get_previous (config_manager));
g_assert_null (meta_monitor_config_manager_pop_previous (config_manager));
linear_config = meta_monitor_config_manager_create_linear (config_manager);
g_assert_null (linear_config->parent_config);
old_current = meta_monitor_config_manager_get_current (config_manager);
g_assert_nonnull (old_current->parent_config);
meta_monitor_config_manager_set_current (config_manager, linear_config);
g_assert (meta_monitor_config_manager_get_current (config_manager) ==
linear_config);
g_assert (meta_monitor_config_manager_get_current (config_manager) !=
old_current);
g_assert (meta_monitor_config_manager_get_previous (config_manager) ==
child_config3);
fallback_config =
meta_monitor_config_manager_create_fallback (config_manager);
g_assert_null (fallback_config->parent_config);
old_current = meta_monitor_config_manager_get_current (config_manager);
g_assert_null (old_current->parent_config);
meta_monitor_config_manager_set_current (config_manager, fallback_config);
g_assert (meta_monitor_config_manager_get_current (config_manager) ==
fallback_config);
g_assert (meta_monitor_config_manager_get_current (config_manager) !=
old_current);
g_assert (meta_monitor_config_manager_get_previous (config_manager) ==
linear_config);
g_assert (meta_monitor_config_manager_pop_previous (config_manager) ==
linear_config);
g_assert (meta_monitor_config_manager_get_previous (config_manager) ==
child_config3);
g_assert (meta_monitor_config_manager_pop_previous (config_manager) ==
child_config3);
g_assert_null (meta_monitor_config_manager_get_previous (config_manager));
g_assert_null (meta_monitor_config_manager_pop_previous (config_manager));
}
monitor-unit-tests: Add tests to verify config manager history Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2021-07-27 12:01:47 -04:00
static void
meta_test_monitor_config_store_set_current (void)
{
g_autoptr (MetaMonitorsConfig) linear_config = NULL;
g_autoptr (MetaMonitorsConfig) fallback_config = NULL;
MetaBackend *backend = meta_get_backend ();
MetaMonitorManager *monitor_manager =
meta_backend_get_monitor_manager (backend);
MetaMonitorConfigManager *config_manager = monitor_manager->config_manager;
MetaMonitorsConfig *old_current;
fallback_config =
meta_monitor_config_manager_create_fallback (config_manager);
linear_config = meta_monitor_config_manager_create_linear (config_manager);
g_assert_nonnull (linear_config);
g_assert_nonnull (fallback_config);
meta_monitor_config_manager_set_current (config_manager, fallback_config);
g_assert (meta_monitor_config_manager_get_current (config_manager) ==
fallback_config);
old_current = meta_monitor_config_manager_get_current (config_manager);
meta_monitor_config_manager_set_current (config_manager, linear_config);
g_assert (old_current != linear_config);
g_assert_nonnull (old_current);
g_assert (meta_monitor_config_manager_get_current (config_manager) ==
linear_config);
g_assert (meta_monitor_config_manager_get_previous (config_manager) ==
old_current);
g_assert (meta_monitor_config_manager_pop_previous (config_manager) ==
old_current);
g_assert_null (meta_monitor_config_manager_get_previous (config_manager));
g_assert_null (meta_monitor_config_manager_pop_previous (config_manager));
}
monitor-manager: Add config relationships and use it for orientation events When we get an orientation event we don't care about keeping track of the configuration changes, but actually we can consider the new configuration just a variant of the previous one, adapted to floating device hardware events, so we only want to apply it if possible, but we don't want to keep a record of it for reverting capabilities. Doing that would in fact, break the ability of reverting back to an actual temporary or persistent configuration. For example when device orientation events happen while we're waiting for an user resolution change confirmation, we would save our new rotated configuration in the history, making then impossible to revert back to the original persistent one. So in such case, don't keep track of those configurations in the history, but only keep track of the last one as current, checking whether the new current is child or sibling of the previously one. Fixes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1221 Related to: https://gitlab.gnome.org/GNOME/mutter/-/issues/646 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-01 09:53:55 -04:00
static void
meta_test_monitor_config_store_set_current_with_parent (void)
{
g_autoptr (MetaMonitorsConfig) child_config = NULL;
g_autoptr (MetaMonitorsConfig) other_child = NULL;
g_autoptr (MetaMonitorsConfig) linear_config = NULL;
g_autoptr (MetaMonitorsConfig) fallback_config = NULL;
MetaBackend *backend = meta_get_backend ();
MetaMonitorManager *monitor_manager =
meta_backend_get_monitor_manager (backend);
MetaMonitorConfigManager *config_manager = monitor_manager->config_manager;
MetaMonitorsConfig *old_current;
linear_config = meta_monitor_config_manager_create_linear (config_manager);
g_assert_null (linear_config->parent_config);
old_current = meta_monitor_config_manager_get_current (config_manager);
g_assert_null (old_current);
meta_monitor_config_manager_set_current (config_manager, linear_config);
g_assert (meta_monitor_config_manager_get_current (config_manager) ==
linear_config);
g_assert (meta_monitor_config_manager_get_current (config_manager) !=
old_current);
g_assert_null (meta_monitor_config_manager_get_previous (config_manager));
g_assert_null (meta_monitor_config_manager_pop_previous (config_manager));
fallback_config = meta_monitor_config_manager_create_fallback (config_manager);
g_assert_nonnull (fallback_config);
g_assert_null (fallback_config->parent_config);
old_current = meta_monitor_config_manager_get_current (config_manager);
g_assert_nonnull (old_current);
g_assert_null (old_current->parent_config);
meta_monitor_config_manager_set_current (config_manager, fallback_config);
g_assert (meta_monitor_config_manager_get_current (config_manager) ==
fallback_config);
g_assert (meta_monitor_config_manager_get_current (config_manager) !=
old_current);
g_assert (meta_monitor_config_manager_get_previous (config_manager) ==
old_current);
child_config = meta_monitor_config_manager_create_linear (config_manager);
old_current = meta_monitor_config_manager_get_current (config_manager);
meta_monitors_config_set_parent_config (child_config, old_current);
g_assert_nonnull (child_config);
g_assert_nonnull (old_current);
g_assert (old_current == fallback_config);
g_assert_null (old_current->parent_config);
meta_monitor_config_manager_set_current (config_manager, child_config);
g_assert (meta_monitor_config_manager_get_current (config_manager) ==
child_config);
g_assert (meta_monitor_config_manager_get_current (config_manager) !=
old_current);
g_assert (meta_monitor_config_manager_get_previous (config_manager) ==
linear_config);
other_child = meta_monitor_config_manager_create_linear (config_manager);
meta_monitors_config_set_parent_config (other_child, old_current);
old_current = meta_monitor_config_manager_get_current (config_manager);
g_assert_nonnull (old_current->parent_config);
g_assert (old_current == child_config);
meta_monitor_config_manager_set_current (config_manager, other_child);
g_assert (meta_monitor_config_manager_get_current (config_manager) ==
other_child);
g_assert (meta_monitor_config_manager_get_current (config_manager) !=
old_current);
g_assert (meta_monitor_config_manager_get_previous (config_manager) ==
linear_config);
g_assert (meta_monitor_config_manager_pop_previous (config_manager) ==
linear_config);
g_assert_null (meta_monitor_config_manager_get_previous (config_manager));
g_assert_null (meta_monitor_config_manager_pop_previous (config_manager));
}
monitor-unit-tests: Add tests to verify config manager history Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2021-07-27 12:01:47 -04:00
static void
meta_test_monitor_config_store_set_current_max_size (void)
{
/* Keep this in sync with CONFIG_HISTORY_MAX_SIZE */
const unsigned int config_history_max_size = 3;
g_autolist (MetaMonitorsConfig) added = NULL;
MetaBackend *backend = meta_get_backend ();
MetaMonitorManager *monitor_manager =
meta_backend_get_monitor_manager (backend);
MetaMonitorConfigManager *config_manager = monitor_manager->config_manager;
MetaMonitorsConfig *previous = NULL;
MetaMonitorsConfig *config;
unsigned int i;
for (i = 0; i < config_history_max_size; i++)
{
g_autoptr (MetaMonitorsConfig) linear_config = NULL;
linear_config = meta_monitor_config_manager_create_linear (config_manager);
g_assert_nonnull (linear_config);
g_assert (!g_list_find (added, linear_config));
if (i > 0)
{
g_assert (previous !=
meta_monitor_config_manager_get_current (config_manager));
}
previous = meta_monitor_config_manager_get_current (config_manager);
meta_monitor_config_manager_set_current (config_manager, linear_config);
added = g_list_prepend (added, g_object_ref (linear_config));
g_assert (meta_monitor_config_manager_get_current (config_manager)
== linear_config);
g_assert (meta_monitor_config_manager_get_previous (config_manager)
== previous);
}
for (i = 0; i < config_history_max_size - 1; i++)
{
g_autoptr (MetaMonitorsConfig) fallback = NULL;
fallback = meta_monitor_config_manager_create_fallback (config_manager);
g_assert_nonnull (fallback);
meta_monitor_config_manager_set_current (config_manager, fallback);
added = g_list_prepend (added, g_steal_pointer (&fallback));
}
g_assert_cmpuint (g_list_length (added), >, config_history_max_size);
config = meta_monitor_config_manager_get_current (config_manager);
g_assert (config == g_list_nth_data (added, 0));
for (i = 0; i < config_history_max_size; i++)
{
config = meta_monitor_config_manager_get_previous (config_manager);
g_assert_nonnull (config);
g_assert (meta_monitor_config_manager_pop_previous (config_manager)
== config);
g_assert (config == g_list_nth_data (added, i + 1));
}
config = meta_monitor_config_manager_get_previous (config_manager);
g_assert_null (config);
g_assert_null (meta_monitor_config_manager_pop_previous (config_manager));
g_assert (config != g_list_nth_data (added, config_history_max_size));
g_assert_nonnull (g_list_nth_data (added, config_history_max_size + 1));
}
static void
meta_test_monitor_config_store_set_current_null (void)
{
MetaBackend *backend = meta_get_backend ();
MetaMonitorManager *monitor_manager =
meta_backend_get_monitor_manager (backend);
MetaMonitorConfigManager *config_manager = monitor_manager->config_manager;
MetaMonitorsConfig *previous;
previous = meta_monitor_config_manager_get_current (config_manager);
g_assert_null (previous);
meta_monitor_config_manager_set_current (config_manager, NULL);
g_assert_null (meta_monitor_config_manager_get_current (config_manager));
g_assert_null (meta_monitor_config_manager_get_previous (config_manager));
g_assert_null (meta_monitor_config_manager_pop_previous (config_manager));
}
tests/monitor: Test two crtcs, one output https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 02:15:25 -05:00
static void
meta_test_monitor_one_disconnected_linear_config (void)
{
MonitorTestCase test_case = initial_test_case;
MetaMonitorTestSetup *test_setup;
test_case.setup.n_outputs = 1;
test_case.expect = (MonitorTestCaseExpect) {
tests: Check that the monitors are properly generated https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-12 21:58:41 -05:00
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
monitor-unit-tests: Check monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-14 04:23:44 -05:00
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.0,
monitor-unit-tests: Check monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-14 04:23:44 -05:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
tests/monitor-unit-tests: Check current monitor mode Check both that current mode is up to date, and that deriving it again won't change it. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-05 23:43:22 -05:00
.current_mode = 0,
tests: Check that the monitors are properly generated https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-12 21:58:41 -05:00
.width_mm = 222,
.height_mm = 125
}
},
.n_monitors = 1,
tests/monitor: Test two crtcs, one output https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 02:15:25 -05:00
.logical_monitors = {
{
monitor-unit-tests: Check monitor <-> logical monitor relationships Make sure that each logical monitor owns the expected actual monitors. This currently needs special care when dealing with laptop lid the configuration, as the MetaMonitorConfigManager path still deosn't handle restoring the previous configuration, meaning the logical monitor with the external monitor will continue being primary. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 01:09:55 -05:00
.monitors = { 0 },
.n_monitors = 1,
tests/monitor: Test two crtcs, one output https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 02:15:25 -05:00
.layout = { .x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
},
},
.n_logical_monitors = 1,
monitor-unit-tests: Check handling of the primary presentation flags The main output of the main (first) monitor of a primary logical monitor should have the MetaOutput::is_primary field set; all other outputs should have it not set. All outputs associated with a logical monitor with presentation set should have MetaOutput::is_presentation set. No other outputs should have it set. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 00:09:21 -05:00
.primary_logical_monitor = 0,
tests/monitor: Test two crtcs, one output https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 02:15:25 -05:00
.n_outputs = 1,
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
.crtcs = {
{
.current_mode = 0,
},
{
.current_mode = -1,
}
},
tests/monitor: Test two crtcs, one output https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 02:15:25 -05:00
.n_crtcs = 2,
.screen_width = 1024,
.screen_height = 768
};
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Make hotplug_mode_update optional Add a flag to the test setup creation function enabling the caller to specify whether a stored config should be used. This is done by changing the value of the hotplug_mode_update MetaOutput field, normally used by VMs to do the same. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 23:32:12 -05:00
MONITOR_TEST_FLAG_NO_STORED);
tests/monitor: Test two crtcs, one output https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 02:15:25 -05:00
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
tests/monitor: Test two crtcs, one output https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 02:15:25 -05:00
}
tests/monitor: Test one out of two outputs being off https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 02:16:12 -05:00
static void
meta_test_monitor_one_off_linear_config (void)
{
MonitorTestCase test_case;
MetaMonitorTestSetup *test_setup;
MonitorTestCaseOutput outputs[] = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125
},
{
.crtc = -1,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 1 },
.n_possible_crtcs = 1,
tests: Check that the monitors are properly generated https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-12 21:58:41 -05:00
.width_mm = 224,
.height_mm = 126
tests/monitor: Test one out of two outputs being off https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 02:16:12 -05:00
}
};
test_case = initial_test_case;
memcpy (&test_case.setup.outputs, &outputs, sizeof (outputs));
test_case.setup.n_outputs = G_N_ELEMENTS (outputs);
test_case.setup.crtcs[1].current_mode = -1;
test_case.expect = (MonitorTestCaseExpect) {
tests: Check that the monitors are properly generated https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-12 21:58:41 -05:00
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
monitor-unit-tests: Check monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-14 04:23:44 -05:00
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.0,
monitor-unit-tests: Check monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-14 04:23:44 -05:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
tests/monitor-unit-tests: Check current monitor mode Check both that current mode is up to date, and that deriving it again won't change it. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-05 23:43:22 -05:00
.current_mode = 0,
tests: Check that the monitors are properly generated https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-12 21:58:41 -05:00
.width_mm = 222,
.height_mm = 125
},
{
.outputs = { 1 },
.n_outputs = 1,
monitor-unit-tests: Check monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-14 04:23:44 -05:00
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.0,
monitor-unit-tests: Check monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-14 04:23:44 -05:00
.crtc_modes = {
{
.output = 1,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
tests/monitor-unit-tests: Check current monitor mode Check both that current mode is up to date, and that deriving it again won't change it. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-05 23:43:22 -05:00
.current_mode = 0,
tests: Check that the monitors are properly generated https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-12 21:58:41 -05:00
.width_mm = 224,
.height_mm = 126
}
},
.n_monitors = 2,
tests/monitor: Test one out of two outputs being off https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 02:16:12 -05:00
.logical_monitors = {
{
monitor-unit-tests: Check monitor <-> logical monitor relationships Make sure that each logical monitor owns the expected actual monitors. This currently needs special care when dealing with laptop lid the configuration, as the MetaMonitorConfigManager path still deosn't handle restoring the previous configuration, meaning the logical monitor with the external monitor will continue being primary. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 01:09:55 -05:00
.monitors = { 0 },
.n_monitors = 1,
tests/monitor: Test one out of two outputs being off https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 02:16:12 -05:00
.layout = { .x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
},
{
monitor-unit-tests: Check monitor <-> logical monitor relationships Make sure that each logical monitor owns the expected actual monitors. This currently needs special care when dealing with laptop lid the configuration, as the MetaMonitorConfigManager path still deosn't handle restoring the previous configuration, meaning the logical monitor with the external monitor will continue being primary. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 01:09:55 -05:00
.monitors = { 1 },
.n_monitors = 1,
tests/monitor: Test one out of two outputs being off https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 02:16:12 -05:00
.layout = { .x = 1024, .y = 0, .width = 1024, .height = 768 },
.scale = 1
},
},
.n_logical_monitors = 2,
monitor-unit-tests: Check handling of the primary presentation flags The main output of the main (first) monitor of a primary logical monitor should have the MetaOutput::is_primary field set; all other outputs should have it not set. All outputs associated with a logical monitor with presentation set should have MetaOutput::is_presentation set. No other outputs should have it set. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 00:09:21 -05:00
.primary_logical_monitor = 0,
tests/monitor: Test one out of two outputs being off https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 02:16:12 -05:00
.n_outputs = 2,
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
.crtcs = {
{
.current_mode = 0,
},
{
.current_mode = 0,
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
.x = 1024,
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
}
},
tests/monitor: Test one out of two outputs being off https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 02:16:12 -05:00
.n_crtcs = 2,
.screen_width = 1024 * 2,
.screen_height = 768
};
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Make hotplug_mode_update optional Add a flag to the test setup creation function enabling the caller to specify whether a stored config should be used. This is done by changing the value of the hotplug_mode_update MetaOutput field, normally used by VMs to do the same. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 23:32:12 -05:00
MONITOR_TEST_FLAG_NO_STORED);
tests/monitor: Test one out of two outputs being off https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 02:16:12 -05:00
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
tests/monitor: Test one out of two outputs being off https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 02:16:12 -05:00
}
tests/monitor: Test preferred mode https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 02:33:45 -05:00
static void
meta_test_monitor_preferred_linear_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 800,
.height = 600,
.refresh_rate = 60.0
},
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0
},
{
.width = 1280,
.height = 720,
.refresh_rate = 60.0
}
},
.n_modes = 3,
.outputs = {
{
.crtc = -1,
.modes = { 0, 1, 2 },
.n_modes = 3,
.preferred_mode = 1,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125
}
},
.n_outputs = 1,
.crtcs = {
{
.current_mode = -1
}
},
.n_crtcs = 1
},
.expect = {
tests: Check that the monitors are properly generated https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-12 21:58:41 -05:00
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
monitor-unit-tests: Check monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-14 04:23:44 -05:00
.modes = {
{
.width = 800,
.height = 600,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.0,
monitor-unit-tests: Check monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-14 04:23:44 -05:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
},
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.0,
monitor-unit-tests: Check monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-14 04:23:44 -05:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 1
}
}
},
{
.width = 1280,
.height = 720,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.0,
monitor-unit-tests: Check monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-14 04:23:44 -05:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 2
}
}
}
},
.n_modes = 3,
tests/monitor-unit-tests: Check current monitor mode Check both that current mode is up to date, and that deriving it again won't change it. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-05 23:43:22 -05:00
.current_mode = 1,
tests: Check that the monitors are properly generated https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-12 21:58:41 -05:00
.width_mm = 222,
.height_mm = 125
}
},
.n_monitors = 1,
tests/monitor: Test preferred mode https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 02:33:45 -05:00
.logical_monitors = {
{
monitor-unit-tests: Check monitor <-> logical monitor relationships Make sure that each logical monitor owns the expected actual monitors. This currently needs special care when dealing with laptop lid the configuration, as the MetaMonitorConfigManager path still deosn't handle restoring the previous configuration, meaning the logical monitor with the external monitor will continue being primary. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 01:09:55 -05:00
.monitors = { 0 },
.n_monitors = 1,
tests/monitor: Test preferred mode https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 02:33:45 -05:00
.layout = { .x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
},
},
.n_logical_monitors = 1,
monitor-unit-tests: Check handling of the primary presentation flags The main output of the main (first) monitor of a primary logical monitor should have the MetaOutput::is_primary field set; all other outputs should have it not set. All outputs associated with a logical monitor with presentation set should have MetaOutput::is_presentation set. No other outputs should have it set. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 00:09:21 -05:00
.primary_logical_monitor = 0,
tests/monitor: Test preferred mode https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 02:33:45 -05:00
.n_outputs = 1,
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
.crtcs = {
{
.current_mode = 1,
}
},
tests/monitor: Test preferred mode https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 02:33:45 -05:00
.n_crtcs = 1,
.screen_width = 1024,
.screen_height = 768,
}
};
MetaMonitorTestSetup *test_setup;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Make hotplug_mode_update optional Add a flag to the test setup creation function enabling the caller to specify whether a stored config should be used. This is done by changing the value of the hotplug_mode_update MetaOutput field, normally used by VMs to do the same. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 23:32:12 -05:00
MONITOR_TEST_FLAG_NO_STORED);
tests/monitor: Test preferred mode https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 02:33:45 -05:00
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
tests/monitor: Test preferred mode https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 02:33:45 -05:00
}
tests/monitor: Add tiled monitor test https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 04:42:06 -05:00
static void
meta_test_monitor_tiled_linear_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 400,
.height = 600,
.refresh_rate = 60.0
},
},
.n_modes = 1,
.outputs = {
{
.crtc = -1,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.tile_info = {
.group_id = 1,
.max_h_tiles = 2,
.max_v_tiles = 1,
.loc_h_tile = 0,
.loc_v_tile = 0,
.tile_w = 400,
.tile_h = 600
}
},
{
.crtc = -1,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 1 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.tile_info = {
.group_id = 1,
.max_h_tiles = 2,
.max_v_tiles = 1,
.loc_h_tile = 1,
.loc_v_tile = 0,
.tile_w = 400,
.tile_h = 600
}
}
},
.n_outputs = 2,
.crtcs = {
{
.current_mode = -1
},
{
.current_mode = -1
}
},
.n_crtcs = 2
},
.expect = {
tests: Check that the monitors are properly generated https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-12 21:58:41 -05:00
.monitors = {
{
.outputs = { 0, 1 },
.n_outputs = 2,
monitor-unit-tests: Check monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-14 04:23:44 -05:00
.modes = {
{
.width = 800,
.height = 600,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.0,
monitor-unit-tests: Check monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-14 04:23:44 -05:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
},
{
.output = 1,
monitor-unit-tests: Check monitor mode CRTC mode positions Check that the crtc mode has the correct intra-monitor position. In effect, this tests that the CRTCs in a tiled monitor are configured with the correct mode on the correct position. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 04:35:01 -05:00
.crtc_mode = 0,
monitor-unit-tests: Check monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-14 04:23:44 -05:00
}
}
},
},
.n_modes = 1,
tests/monitor-unit-tests: Check current monitor mode Check both that current mode is up to date, and that deriving it again won't change it. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-05 23:43:22 -05:00
.current_mode = 0,
tests: Check that the monitors are properly generated https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-12 21:58:41 -05:00
.width_mm = 222,
.height_mm = 125,
}
},
.n_monitors = 1,
tests/monitor: Add tiled monitor test https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 04:42:06 -05:00
.logical_monitors = {
{
monitor-unit-tests: Check monitor <-> logical monitor relationships Make sure that each logical monitor owns the expected actual monitors. This currently needs special care when dealing with laptop lid the configuration, as the MetaMonitorConfigManager path still deosn't handle restoring the previous configuration, meaning the logical monitor with the external monitor will continue being primary. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 01:09:55 -05:00
.monitors = { 0 },
.n_monitors = 1,
tests/monitor: Add tiled monitor test https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 04:42:06 -05:00
.layout = { .x = 0, .y = 0, .width = 800, .height = 600 },
.scale = 1
},
},
.n_logical_monitors = 1,
monitor-unit-tests: Check handling of the primary presentation flags The main output of the main (first) monitor of a primary logical monitor should have the MetaOutput::is_primary field set; all other outputs should have it not set. All outputs associated with a logical monitor with presentation set should have MetaOutput::is_presentation set. No other outputs should have it set. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 00:09:21 -05:00
.primary_logical_monitor = 0,
tests/monitor: Add tiled monitor test https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 04:42:06 -05:00
.n_outputs = 2,
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
.crtcs = {
{
.current_mode = 0,
},
{
.current_mode = 0,
monitor: Don't keep CRTC position in MetaMonitorCrtcMode The CRTC position depends on the transform and how the transform is implemented. The function calculating the positions still doesn't support anything but the non-transformed case; this commit is in preparation of adding support for transforms. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-17 05:21:10 -04:00
.x = 400,
.y = 0
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
}
},
tests/monitor: Add tiled monitor test https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 04:42:06 -05:00
.n_crtcs = 2,
monitor-unit-tests: Check tiled monitor adding/removing notification Check that the moniter manager backends get the tiled monitor added/removed notification. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-13 07:11:48 -05:00
.n_tiled_monitors = 1,
tests/monitor: Add tiled monitor test https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 04:42:06 -05:00
.screen_width = 800,
.screen_height = 600,
}
};
MetaMonitorTestSetup *test_setup;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Make hotplug_mode_update optional Add a flag to the test setup creation function enabling the caller to specify whether a stored config should be used. This is done by changing the value of the hotplug_mode_update MetaOutput field, normally used by VMs to do the same. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 23:32:12 -05:00
MONITOR_TEST_FLAG_NO_STORED);
tests/monitor: Add tiled monitor test https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 04:42:06 -05:00
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
tests/monitor: Add tiled monitor test https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 04:42:06 -05:00
}
tests/monitor-unit-tests: Check handling of odd tiled monitors Add tests for handling tiled monitors where the origin tile output is not the main output. https://bugzilla.gnome.org/show_bug.cgi?id=781723
2017-05-01 00:12:42 -04:00
static void
meta_test_monitor_tiled_non_preferred_linear_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 640,
.height = 480,
.refresh_rate = 60.0
},
{
.width = 800,
.height = 600,
.refresh_rate = 60.0
},
{
.width = 512,
.height = 768,
.refresh_rate = 120.0
},
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0
},
},
.n_modes = 4,
.outputs = {
{
.crtc = -1,
.modes = { 0, 2 },
.n_modes = 2,
.preferred_mode = 1,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.tile_info = {
.group_id = 1,
.max_h_tiles = 2,
.max_v_tiles = 1,
.loc_h_tile = 0,
.loc_v_tile = 0,
.tile_w = 512,
.tile_h = 768
}
},
{
.crtc = -1,
.modes = { 1, 2, 3 },
.n_modes = 3,
.preferred_mode = 0,
.possible_crtcs = { 1 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.tile_info = {
.group_id = 1,
.max_h_tiles = 2,
.max_v_tiles = 1,
.loc_h_tile = 1,
.loc_v_tile = 0,
.tile_w = 512,
.tile_h = 768
}
}
},
.n_outputs = 2,
.crtcs = {
{
.current_mode = -1
},
{
.current_mode = -1
}
},
.n_crtcs = 2
},
.expect = {
.monitors = {
{
.outputs = { 0, 1 },
.n_outputs = 2,
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 120.0,
tests/monitor-unit-tests: Check handling of odd tiled monitors Add tests for handling tiled monitors where the origin tile output is not the main output. https://bugzilla.gnome.org/show_bug.cgi?id=781723
2017-05-01 00:12:42 -04:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 2
},
{
.output = 1,
.crtc_mode = 2,
}
}
},
{
.width = 800,
.height = 600,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.0,
tests/monitor-unit-tests: Check handling of odd tiled monitors Add tests for handling tiled monitors where the origin tile output is not the main output. https://bugzilla.gnome.org/show_bug.cgi?id=781723
2017-05-01 00:12:42 -04:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = -1
},
{
.output = 1,
.crtc_mode = 1,
}
}
},
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.0,
tests/monitor-unit-tests: Check handling of odd tiled monitors Add tests for handling tiled monitors where the origin tile output is not the main output. https://bugzilla.gnome.org/show_bug.cgi?id=781723
2017-05-01 00:12:42 -04:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = -1
},
{
.output = 1,
.crtc_mode = 3,
}
}
},
},
.n_modes = 3,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
}
},
.n_monitors = 1,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
},
},
.n_logical_monitors = 1,
.primary_logical_monitor = 0,
.n_outputs = 2,
.crtcs = {
{
.current_mode = 2,
},
{
.current_mode = 2,
.x = 512
}
},
.n_crtcs = 2,
.n_tiled_monitors = 1,
.screen_width = 1024,
.screen_height = 768,
}
};
MetaMonitorTestSetup *test_setup;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
tests/monitor-unit-tests: Check handling of odd tiled monitors Add tests for handling tiled monitors where the origin tile output is not the main output. https://bugzilla.gnome.org/show_bug.cgi?id=781723
2017-05-01 00:12:42 -04:00
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
tests/monitor-unit-tests: Check handling of odd tiled monitors Add tests for handling tiled monitors where the origin tile output is not the main output. https://bugzilla.gnome.org/show_bug.cgi?id=781723
2017-05-01 00:12:42 -04:00
}
monitor-unit-tests: Check tiled monitors with non-origin main output Test that a tiled monitor with tile (0, 0) as the non-main output, where main output is defined as the output that is active as long as the monitor is active. https://bugzilla.gnome.org/show_bug.cgi?id=781723
2017-07-12 03:44:51 -04:00
static void
meta_test_monitor_tiled_non_main_origin_linear_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 400,
.height = 600,
.refresh_rate = 60.0
},
{
.width = 800,
.height = 600,
.refresh_rate = 30.0
},
},
.n_modes = 2,
.outputs = {
{
.crtc = -1,
.modes = { 0, 1 },
.n_modes = 2,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.tile_info = {
.group_id = 1,
.max_h_tiles = 2,
.max_v_tiles = 1,
.loc_h_tile = 1,
.loc_v_tile = 0,
.tile_w = 400,
.tile_h = 600
}
},
{
.crtc = -1,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 1 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.tile_info = {
.group_id = 1,
.max_h_tiles = 2,
.max_v_tiles = 1,
.loc_h_tile = 0,
.loc_v_tile = 0,
.tile_w = 400,
.tile_h = 600
}
}
},
.n_outputs = 2,
.crtcs = {
{
.current_mode = -1
},
{
.current_mode = -1
}
},
.n_crtcs = 2
},
.expect = {
.monitors = {
{
.outputs = { 0, 1 },
.n_outputs = 2,
.modes = {
{
.width = 800,
.height = 600,
.refresh_rate = 60.0,
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0,
},
{
.output = 1,
.crtc_mode = 0,
}
}
},
{
.width = 800,
.height = 600,
.refresh_rate = 30.0,
.crtc_modes = {
{
.output = 0,
.crtc_mode = 1
},
{
.output = 1,
.crtc_mode = -1,
}
}
},
},
.n_modes = 2,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
}
},
.n_monitors = 1,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 800, .height = 600 },
.scale = 1
},
},
.n_logical_monitors = 1,
.primary_logical_monitor = 0,
.n_outputs = 2,
.crtcs = {
{
.current_mode = 0,
.x = 400,
.y = 0
},
{
.current_mode = 0,
}
},
.n_crtcs = 2,
.n_tiled_monitors = 1,
.screen_width = 800,
.screen_height = 600,
}
};
MetaMonitorTestSetup *test_setup;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Check tiled monitors with non-origin main output Test that a tiled monitor with tile (0, 0) as the non-main output, where main output is defined as the output that is active as long as the monitor is active. https://bugzilla.gnome.org/show_bug.cgi?id=781723
2017-07-12 03:44:51 -04:00
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Check tiled monitors with non-origin main output Test that a tiled monitor with tile (0, 0) as the non-main output, where main output is defined as the output that is active as long as the monitor is active. https://bugzilla.gnome.org/show_bug.cgi?id=781723
2017-07-12 03:44:51 -04:00
}
tests/monitor: Add HiDPI test This doesn't test the actual calculation, since that is done in the backend, it only tests the configuration. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 04:42:30 -05:00
static void
meta_test_monitor_hidpi_linear_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1280,
.height = 720,
.refresh_rate = 60.0
},
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0
}
},
.n_modes = 2,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
/* These will result in DPI of about 216" */
.width_mm = 150,
.height_mm = 85,
.scale = 2,
},
{
.crtc = 1,
.modes = { 1 },
.n_modes = 1,
.preferred_mode = 1,
.possible_crtcs = { 1 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.scale = 1,
}
},
.n_outputs = 2,
.crtcs = {
{
.current_mode = -1
},
{
.current_mode = -1
}
},
.n_crtcs = 2
},
.expect = {
tests: Check that the monitors are properly generated https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-12 21:58:41 -05:00
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
monitor-unit-tests: Check monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-14 04:23:44 -05:00
.modes = {
{
.width = 1280,
.height = 720,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.0,
monitor-unit-tests: Check monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-14 04:23:44 -05:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
},
},
.n_modes = 1,
tests/monitor-unit-tests: Check current monitor mode Check both that current mode is up to date, and that deriving it again won't change it. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-05 23:43:22 -05:00
.current_mode = 0,
tests: Check that the monitors are properly generated https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-12 21:58:41 -05:00
.width_mm = 150,
.height_mm = 85
},
{
.outputs = { 1 },
.n_outputs = 1,
monitor-unit-tests: Check monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-14 04:23:44 -05:00
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.0,
monitor-unit-tests: Check monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-14 04:23:44 -05:00
.crtc_modes = {
{
.output = 1,
.crtc_mode = 1
}
}
},
},
.n_modes = 1,
tests/monitor-unit-tests: Check current monitor mode Check both that current mode is up to date, and that deriving it again won't change it. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-05 23:43:22 -05:00
.current_mode = 0,
tests: Check that the monitors are properly generated https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-12 21:58:41 -05:00
.width_mm = 222,
.height_mm = 125
}
},
.n_monitors = 2,
tests/monitor: Add HiDPI test This doesn't test the actual calculation, since that is done in the backend, it only tests the configuration. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 04:42:30 -05:00
.logical_monitors = {
{
monitor-unit-tests: Check monitor <-> logical monitor relationships Make sure that each logical monitor owns the expected actual monitors. This currently needs special care when dealing with laptop lid the configuration, as the MetaMonitorConfigManager path still deosn't handle restoring the previous configuration, meaning the logical monitor with the external monitor will continue being primary. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 01:09:55 -05:00
.monitors = { 0 },
.n_monitors = 1,
Add support for scaled logical monitor framebuffers This commit adds support for rendering onto enlarged per logical monitor framebuffers, using the scaled clutter stage views, for HiDPI enabled logical monitors. This works by scaling the mode of the monitors in a logical monitors by the scale, no longer relying on scaling the window actors and window geometry for making windows have the correct size on HiDPI monitors. It is disabled by default, as in automatically created configurations will still use the old mode. This is partly because Xwayland clients will not yet work good enough to make it feasible. To enable, add the 'scale-monitor-framebuffer' keyword to the org.gnome.mutter.experimental-features gsettings array. It is still possible to specify the mode via the new D-Bus API, which has been adapted. The adaptations to the D-Bus API means the caller need to be aware of how to position logical monitors on the stage grid. This depends on the 'layout-mode' property that is used (see the DisplayConfig D-Bus documentation). https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-02-24 05:10:52 -05:00
.layout = { .x = 0, .y = 0, .width = 640, .height = 360 },
tests/monitor: Add HiDPI test This doesn't test the actual calculation, since that is done in the backend, it only tests the configuration. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 04:42:30 -05:00
.scale = 2
},
{
monitor-unit-tests: Check monitor <-> logical monitor relationships Make sure that each logical monitor owns the expected actual monitors. This currently needs special care when dealing with laptop lid the configuration, as the MetaMonitorConfigManager path still deosn't handle restoring the previous configuration, meaning the logical monitor with the external monitor will continue being primary. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 01:09:55 -05:00
.monitors = { 1 },
.n_monitors = 1,
Add support for scaled logical monitor framebuffers This commit adds support for rendering onto enlarged per logical monitor framebuffers, using the scaled clutter stage views, for HiDPI enabled logical monitors. This works by scaling the mode of the monitors in a logical monitors by the scale, no longer relying on scaling the window actors and window geometry for making windows have the correct size on HiDPI monitors. It is disabled by default, as in automatically created configurations will still use the old mode. This is partly because Xwayland clients will not yet work good enough to make it feasible. To enable, add the 'scale-monitor-framebuffer' keyword to the org.gnome.mutter.experimental-features gsettings array. It is still possible to specify the mode via the new D-Bus API, which has been adapted. The adaptations to the D-Bus API means the caller need to be aware of how to position logical monitors on the stage grid. This depends on the 'layout-mode' property that is used (see the DisplayConfig D-Bus documentation). https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-02-24 05:10:52 -05:00
.layout = { .x = 640, .y = 0, .width = 1024, .height = 768 },
tests/monitor: Add HiDPI test This doesn't test the actual calculation, since that is done in the backend, it only tests the configuration. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 04:42:30 -05:00
.scale = 1
}
},
.n_logical_monitors = 2,
monitor-unit-tests: Check handling of the primary presentation flags The main output of the main (first) monitor of a primary logical monitor should have the MetaOutput::is_primary field set; all other outputs should have it not set. All outputs associated with a logical monitor with presentation set should have MetaOutput::is_presentation set. No other outputs should have it set. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 00:09:21 -05:00
.primary_logical_monitor = 0,
tests/monitor: Add HiDPI test This doesn't test the actual calculation, since that is done in the backend, it only tests the configuration. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 04:42:30 -05:00
.n_outputs = 2,
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
.crtcs = {
{
.current_mode = 0,
},
{
.current_mode = 1,
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
.x = 640,
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
}
},
tests/monitor: Add HiDPI test This doesn't test the actual calculation, since that is done in the backend, it only tests the configuration. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 04:42:30 -05:00
.n_crtcs = 2,
Add support for scaled logical monitor framebuffers This commit adds support for rendering onto enlarged per logical monitor framebuffers, using the scaled clutter stage views, for HiDPI enabled logical monitors. This works by scaling the mode of the monitors in a logical monitors by the scale, no longer relying on scaling the window actors and window geometry for making windows have the correct size on HiDPI monitors. It is disabled by default, as in automatically created configurations will still use the old mode. This is partly because Xwayland clients will not yet work good enough to make it feasible. To enable, add the 'scale-monitor-framebuffer' keyword to the org.gnome.mutter.experimental-features gsettings array. It is still possible to specify the mode via the new D-Bus API, which has been adapted. The adaptations to the D-Bus API means the caller need to be aware of how to position logical monitors on the stage grid. This depends on the 'layout-mode' property that is used (see the DisplayConfig D-Bus documentation). https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-02-24 05:10:52 -05:00
.screen_width = 640 + 1024,
tests/monitor: Add HiDPI test This doesn't test the actual calculation, since that is done in the backend, it only tests the configuration. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 04:42:30 -05:00
.screen_height = 768
}
};
MetaMonitorTestSetup *test_setup;
tests: Derive configuration when stage views is disabled In order to test deriving the logical state from the underlying configuration, as is always done on X11, make the test backend derive the state when stage views are disabled. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 05:16:04 -04:00
if (!meta_is_stage_views_enabled ())
{
g_test_skip ("Not using stage views");
return;
}
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Make hotplug_mode_update optional Add a flag to the test setup creation function enabling the caller to specify whether a stored config should be used. This is done by changing the value of the hotplug_mode_update MetaOutput field, normally used by VMs to do the same. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 23:32:12 -05:00
MONITOR_TEST_FLAG_NO_STORED);
tests/monitor: Add HiDPI test This doesn't test the actual calculation, since that is done in the backend, it only tests the configuration. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 04:42:30 -05:00
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
tests/monitor: Add HiDPI test This doesn't test the actual calculation, since that is done in the backend, it only tests the configuration. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-07 04:42:30 -05:00
}
monitor-unit-tests: Test suggested-x/y configuration Test the suggested-x/y output state often set by virtual machines. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-20 10:15:45 -05:00
static void
meta_test_monitor_suggested_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 800,
.height = 600,
.refresh_rate = 60.0
},
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0
}
},
.n_modes = 2,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
tests/monitor-unit-tests: Make hotplug mode part of test setup https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1287
2020-02-26 03:35:14 -05:00
.height_mm = 125,
.hotplug_mode = TRUE,
.suggested_x = 1024,
.suggested_y = 758,
monitor-unit-tests: Test suggested-x/y configuration Test the suggested-x/y output state often set by virtual machines. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-20 10:15:45 -05:00
},
{
.crtc = 1,
.modes = { 1 },
.n_modes = 1,
.preferred_mode = 1,
.possible_crtcs = { 1 },
.n_possible_crtcs = 1,
.width_mm = 220,
tests/monitor-unit-tests: Make hotplug mode part of test setup https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1287
2020-02-26 03:35:14 -05:00
.height_mm = 124,
.hotplug_mode = TRUE,
.suggested_x = 0,
.suggested_y = 0,
monitor-unit-tests: Test suggested-x/y configuration Test the suggested-x/y output state often set by virtual machines. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-20 10:15:45 -05:00
}
},
.n_outputs = 2,
.crtcs = {
{
.current_mode = -1
},
{
.current_mode = -1
}
},
.n_crtcs = 2
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 800,
.height = 600,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.0,
monitor-unit-tests: Test suggested-x/y configuration Test the suggested-x/y output state often set by virtual machines. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-20 10:15:45 -05:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
tests/monitor-unit-tests: Check current monitor mode Check both that current mode is up to date, and that deriving it again won't change it. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-05 23:43:22 -05:00
.current_mode = 0,
monitor-unit-tests: Test suggested-x/y configuration Test the suggested-x/y output state often set by virtual machines. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-20 10:15:45 -05:00
.width_mm = 222,
.height_mm = 125
},
{
.outputs = { 1 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.0,
monitor-unit-tests: Test suggested-x/y configuration Test the suggested-x/y output state often set by virtual machines. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-20 10:15:45 -05:00
.crtc_modes = {
{
.output = 1,
.crtc_mode = 1
}
}
}
},
.n_modes = 1,
tests/monitor-unit-tests: Check current monitor mode Check both that current mode is up to date, and that deriving it again won't change it. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-05 23:43:22 -05:00
.current_mode = 0,
monitor-unit-tests: Test suggested-x/y configuration Test the suggested-x/y output state often set by virtual machines. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-20 10:15:45 -05:00
.width_mm = 220,
.height_mm = 124
}
},
.n_monitors = 2,
/*
* Logical monitors expectations altered to correspond to the
* "suggested_x/y" changed further below.
*/
.logical_monitors = {
{
monitor-unit-tests: Check monitor <-> logical monitor relationships Make sure that each logical monitor owns the expected actual monitors. This currently needs special care when dealing with laptop lid the configuration, as the MetaMonitorConfigManager path still deosn't handle restoring the previous configuration, meaning the logical monitor with the external monitor will continue being primary. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 01:09:55 -05:00
.monitors = { 0 },
.n_monitors = 1,
monitor-unit-tests: Test suggested-x/y configuration Test the suggested-x/y output state often set by virtual machines. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-20 10:15:45 -05:00
.layout = { .x = 1024, .y = 758, .width = 800, .height = 600 },
.scale = 1
},
{
monitor-unit-tests: Check monitor <-> logical monitor relationships Make sure that each logical monitor owns the expected actual monitors. This currently needs special care when dealing with laptop lid the configuration, as the MetaMonitorConfigManager path still deosn't handle restoring the previous configuration, meaning the logical monitor with the external monitor will continue being primary. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 01:09:55 -05:00
.monitors = { 1 },
.n_monitors = 1,
monitor-unit-tests: Test suggested-x/y configuration Test the suggested-x/y output state often set by virtual machines. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-20 10:15:45 -05:00
.layout = { .x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
}
},
.n_logical_monitors = 2,
monitor-unit-tests: Check handling of the primary presentation flags The main output of the main (first) monitor of a primary logical monitor should have the MetaOutput::is_primary field set; all other outputs should have it not set. All outputs associated with a logical monitor with presentation set should have MetaOutput::is_presentation set. No other outputs should have it set. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 00:09:21 -05:00
.primary_logical_monitor = 1,
monitor-unit-tests: Test suggested-x/y configuration Test the suggested-x/y output state often set by virtual machines. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-20 10:15:45 -05:00
.n_outputs = 2,
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
.crtcs = {
{
.current_mode = 0,
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
.x = 1024,
.y = 758,
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
},
{
.current_mode = 1,
}
},
monitor-unit-tests: Test suggested-x/y configuration Test the suggested-x/y output state often set by virtual machines. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-20 10:15:45 -05:00
.n_crtcs = 2,
.n_tiled_monitors = 0,
.screen_width = 1024 + 800,
.screen_height = 1358
}
};
MetaMonitorTestSetup *test_setup;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Make hotplug_mode_update optional Add a flag to the test setup creation function enabling the caller to specify whether a stored config should be used. This is done by changing the value of the hotplug_mode_update MetaOutput field, normally used by VMs to do the same. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 23:32:12 -05:00
MONITOR_TEST_FLAG_NO_STORED);
monitor-unit-tests: Test suggested-x/y configuration Test the suggested-x/y output state often set by virtual machines. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-20 10:15:45 -05:00
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Test suggested-x/y configuration Test the suggested-x/y output state often set by virtual machines. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-20 10:15:45 -05:00
}
monitor-unit-tests: Add test for overlapping monitor config Verify that when we've monitors with overlapping preferred configuration, we fallback to the default linear configuration. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2019-04-03 12:56:45 -04:00
static void
meta_test_monitor_suggested_config_overlapping (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 800,
.height = 600,
.refresh_rate = 60.0
},
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0
}
},
.n_modes = 2,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.hotplug_mode = TRUE,
.suggested_x = 800,
.suggested_y = 600,
},
{
.crtc = 1,
.modes = { 1 },
.n_modes = 1,
.preferred_mode = 1,
.possible_crtcs = { 1 },
.n_possible_crtcs = 1,
.width_mm = 220,
.height_mm = 124,
.hotplug_mode = TRUE,
.suggested_x = 0,
.suggested_y = 0,
}
},
.n_outputs = 2,
.crtcs = {
{
.current_mode = -1
},
{
.current_mode = -1
}
},
.n_crtcs = 2
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 800,
.height = 600,
.refresh_rate = 60.0,
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125
},
{
.outputs = { 1 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0,
.crtc_modes = {
{
.output = 1,
.crtc_mode = 1
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 220,
.height_mm = 124
}
},
.n_monitors = 2,
/*
* Logical monitors expectations altered to correspond to the
* "suggested_x/y" defined above.
*/
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 1024, .y = 0, .width = 800, .height = 600 },
.scale = 1
},
{
.monitors = { 1 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
}
},
.n_logical_monitors = 2,
.primary_logical_monitor = 1,
.n_outputs = 2,
.crtcs = {
{
.x = 1024,
.y = 0,
.current_mode = 0,
},
{
.x = 0,
.y = 0,
.current_mode = 1,
}
},
.n_crtcs = 2,
.n_tiled_monitors = 0,
.screen_width = 1024 + 800,
.screen_height = MAX (768, 600)
}
};
MetaMonitorTestSetup *test_setup;
test_setup = create_monitor_test_setup (&test_case.setup,
MONITOR_TEST_FLAG_NO_STORED);
g_test_expect_message (G_LOG_DOMAIN, G_LOG_LEVEL_WARNING,
"Suggested monitor config has overlapping region, "
"rejecting");
emulate_hotplug (test_setup);
g_test_assert_expected_messages ();
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
monitor-unit-tests: Add test for overlapping monitor config Verify that when we've monitors with overlapping preferred configuration, we fallback to the default linear configuration. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2019-04-03 12:56:45 -04:00
}
monitor-unit-tests: Check suggested configuration has adjacent outputs Verify that the suggested monitor configuration contains only adjacent monitors, and that if this is not the case we fallback to the linear configuration. This can happen in case of multi-DPI setup, so add a test checking this too. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2019-04-03 13:02:42 -04:00
static void
meta_test_monitor_suggested_config_not_adjacent (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 800,
.height = 600,
.refresh_rate = 60.0
},
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0
}
},
.n_modes = 2,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.hotplug_mode = TRUE,
.suggested_x = 1920,
.suggested_y = 1080,
},
{
.crtc = 1,
.modes = { 1 },
.n_modes = 1,
.preferred_mode = 1,
.possible_crtcs = { 1 },
.n_possible_crtcs = 1,
.width_mm = 220,
.height_mm = 124,
.hotplug_mode = TRUE,
.suggested_x = 0,
.suggested_y = 0,
}
},
.n_outputs = 2,
.crtcs = {
{
.current_mode = -1
},
{
.current_mode = -1
}
},
.n_crtcs = 2
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 800,
.height = 600,
.refresh_rate = 60.0,
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125
},
{
.outputs = { 1 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0,
.crtc_modes = {
{
.output = 1,
.crtc_mode = 1
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 220,
.height_mm = 124
}
},
.n_monitors = 2,
/*
* Logical monitors expectations follow fallback linear configuration
*/
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 1024, .y = 0, .width = 800, .height = 600 },
.scale = 1
},
{
.monitors = { 1 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
}
},
.n_logical_monitors = 2,
.primary_logical_monitor = 1,
.n_outputs = 2,
.crtcs = {
{
.current_mode = 0,
.x = 1024,
.y = 0,
},
{
.current_mode = 1,
.x = 0,
.y = 0,
}
},
.n_crtcs = 2,
.n_tiled_monitors = 0,
.screen_width = 1024 + 800,
.screen_height = MAX (768, 600)
}
};
MetaMonitorTestSetup *test_setup;
test_setup = create_monitor_test_setup (&test_case.setup,
MONITOR_TEST_FLAG_NO_STORED);
g_test_expect_message (G_LOG_DOMAIN, G_LOG_LEVEL_WARNING,
"Suggested monitor config has monitors with no "
"neighbors, rejecting");
emulate_hotplug (test_setup);
g_test_assert_expected_messages ();
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
monitor-unit-tests: Check suggested configuration has adjacent outputs Verify that the suggested monitor configuration contains only adjacent monitors, and that if this is not the case we fallback to the linear configuration. This can happen in case of multi-DPI setup, so add a test checking this too. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2019-04-03 13:02:42 -04:00
}
static void
meta_test_monitor_suggested_config_multi_dpi (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 800,
.height = 600,
.refresh_rate = 60.0
},
{
.width = 4096,
.height = 2160,
.refresh_rate = 60.0
}
},
.n_modes = 2,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.hotplug_mode = TRUE,
.suggested_x = 4096,
.suggested_y = 2160,
},
{
.crtc = 1,
.modes = { 1 },
.n_modes = 1,
.preferred_mode = 1,
.possible_crtcs = { 1 },
.n_possible_crtcs = 1,
.width_mm = 350,
.height_mm = 180,
.scale = 2,
.hotplug_mode = TRUE,
.suggested_x = 0,
.suggested_y = 0,
}
},
.n_outputs = 2,
.crtcs = {
{
.current_mode = -1
},
{
.current_mode = -1
}
},
.n_crtcs = 2
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 800,
.height = 600,
.refresh_rate = 60.0,
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125
},
{
.outputs = { 1 },
.n_outputs = 1,
.modes = {
{
.width = 4096,
.height = 2160,
.refresh_rate = 60.0,
.crtc_modes = {
{
.output = 1,
.crtc_mode = 1
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 350,
.height_mm = 180,
}
},
.n_monitors = 2,
/*
* Logical monitors expectations altered to correspond to the
* "suggested_x/y" changed further below.
*/
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 4096/2, .y = 0, .width = 800, .height = 600 },
.scale = 1
},
{
.monitors = { 1 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 4096/2, .height = 2160/2 },
.scale = 2
}
},
.n_logical_monitors = 2,
.primary_logical_monitor = 1,
.n_outputs = 2,
.crtcs = {
{
.current_mode = 0,
.x = 2048,
},
{
.current_mode = 1,
}
},
.n_crtcs = 2,
.n_tiled_monitors = 0,
.screen_width = 4096/2 + 800,
.screen_height = 2160/2
}
};
MetaMonitorTestSetup *test_setup;
test_setup = create_monitor_test_setup (&test_case.setup,
MONITOR_TEST_FLAG_NO_STORED);
g_test_expect_message (G_LOG_DOMAIN, G_LOG_LEVEL_WARNING,
"Suggested monitor config has monitors with no "
"neighbors, rejecting");
emulate_hotplug (test_setup);
g_test_assert_expected_messages();
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
monitor-unit-tests: Check suggested configuration has adjacent outputs Verify that the suggested monitor configuration contains only adjacent monitors, and that if this is not the case we fallback to the linear configuration. This can happen in case of multi-DPI setup, so add a test checking this too. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2019-04-03 13:02:42 -04:00
}
monitor-unit-tests: Add test for handling too few CRTCs Check that configuration when there are more outputs than CRTCs does something sane. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 04:10:58 -05:00
static void
meta_test_monitor_limited_crtcs (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0
}
},
.n_modes = 1,
.outputs = {
{
.crtc = -1,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125
},
{
.crtc = -1,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 220,
.height_mm = 124
}
},
.n_outputs = 2,
.crtcs = {
{
.current_mode = 0
}
},
.n_crtcs = 1
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.0,
monitor-unit-tests: Add test for handling too few CRTCs Check that configuration when there are more outputs than CRTCs does something sane. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 04:10:58 -05:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125
},
{
.outputs = { 1 },
.n_outputs = 1,
.modes = {
Fix a couple of wrong indentations https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 00:23:53 -04:00
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.0,
Fix a couple of wrong indentations https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 00:23:53 -04:00
.crtc_modes = {
monitor-unit-tests: Add test for handling too few CRTCs Check that configuration when there are more outputs than CRTCs does something sane. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 04:10:58 -05:00
{
Fix a couple of wrong indentations https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 00:23:53 -04:00
.output = 1,
.crtc_mode = 0
monitor-unit-tests: Add test for handling too few CRTCs Check that configuration when there are more outputs than CRTCs does something sane. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 04:10:58 -05:00
}
Fix a couple of wrong indentations https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 00:23:53 -04:00
}
}
monitor-unit-tests: Add test for handling too few CRTCs Check that configuration when there are more outputs than CRTCs does something sane. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 04:10:58 -05:00
},
.n_modes = 1,
.current_mode = -1,
.width_mm = 220,
.height_mm = 124
}
},
.n_monitors = 2,
.logical_monitors = {
{
monitor-unit-tests: Check monitor <-> logical monitor relationships Make sure that each logical monitor owns the expected actual monitors. This currently needs special care when dealing with laptop lid the configuration, as the MetaMonitorConfigManager path still deosn't handle restoring the previous configuration, meaning the logical monitor with the external monitor will continue being primary. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 01:09:55 -05:00
.monitors = { 0 },
.n_monitors = 1,
monitor-unit-tests: Add test for handling too few CRTCs Check that configuration when there are more outputs than CRTCs does something sane. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 04:10:58 -05:00
.layout = { .x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
},
},
.n_logical_monitors = 1,
monitor-unit-tests: Check handling of the primary presentation flags The main output of the main (first) monitor of a primary logical monitor should have the MetaOutput::is_primary field set; all other outputs should have it not set. All outputs associated with a logical monitor with presentation set should have MetaOutput::is_presentation set. No other outputs should have it set. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 00:09:21 -05:00
.primary_logical_monitor = 0,
monitor-unit-tests: Add test for handling too few CRTCs Check that configuration when there are more outputs than CRTCs does something sane. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 04:10:58 -05:00
.n_outputs = 2,
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
.crtcs = {
{
.current_mode = 0,
}
},
monitor-unit-tests: Add test for handling too few CRTCs Check that configuration when there are more outputs than CRTCs does something sane. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 04:10:58 -05:00
.n_crtcs = 1,
.n_tiled_monitors = 0,
.screen_width = 1024,
.screen_height = 768
}
};
MetaMonitorTestSetup *test_setup;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Make hotplug_mode_update optional Add a flag to the test setup creation function enabling the caller to specify whether a stored config should be used. This is done by changing the value of the hotplug_mode_update MetaOutput field, normally used by VMs to do the same. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 23:32:12 -05:00
MONITOR_TEST_FLAG_NO_STORED);
monitor-unit-tests: Add test for handling too few CRTCs Check that configuration when there are more outputs than CRTCs does something sane. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 04:10:58 -05:00
Remove old monitor configuration system Remove the old MetaMonitorConfig system and mark the new one as non-experimental. This also removes the D-Bus property. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-24 03:36:12 -04:00
g_test_expect_message (G_LOG_DOMAIN, G_LOG_LEVEL_WARNING,
"Failed to use linear *");
monitor-unit-tests: Add test for handling too few CRTCs Check that configuration when there are more outputs than CRTCs does something sane. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 04:10:58 -05:00
emulate_hotplug (test_setup);
g_test_assert_expected_messages ();
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Add test for handling too few CRTCs Check that configuration when there are more outputs than CRTCs does something sane. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 04:10:58 -05:00
}
monitor-unit-tests: Add laptop lid switch test case Test that the laptop panel is disabled if the lid is closed. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 22:50:44 -05:00
static void
meta_test_monitor_lid_switch_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0
}
},
.n_modes = 1,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.is_laptop_panel = TRUE
},
{
.crtc = 1,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 1 },
.n_possible_crtcs = 1,
.width_mm = 220,
.height_mm = 124
}
},
.n_outputs = 2,
.crtcs = {
{
.current_mode = 0
},
{
.current_mode = 0
}
},
.n_crtcs = 2
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.0,
monitor-unit-tests: Add laptop lid switch test case Test that the laptop panel is disabled if the lid is closed. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 22:50:44 -05:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125
},
{
.outputs = { 1 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.0,
monitor-unit-tests: Add laptop lid switch test case Test that the laptop panel is disabled if the lid is closed. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 22:50:44 -05:00
.crtc_modes = {
{
.output = 1,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 220,
.height_mm = 124
}
},
.n_monitors = 2,
.logical_monitors = {
{
monitor-unit-tests: Check monitor <-> logical monitor relationships Make sure that each logical monitor owns the expected actual monitors. This currently needs special care when dealing with laptop lid the configuration, as the MetaMonitorConfigManager path still deosn't handle restoring the previous configuration, meaning the logical monitor with the external monitor will continue being primary. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 01:09:55 -05:00
.monitors = { 0 },
.n_monitors = 1,
monitor-unit-tests: Add laptop lid switch test case Test that the laptop panel is disabled if the lid is closed. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 22:50:44 -05:00
.layout = { .x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
},
{
monitor-unit-tests: Check monitor <-> logical monitor relationships Make sure that each logical monitor owns the expected actual monitors. This currently needs special care when dealing with laptop lid the configuration, as the MetaMonitorConfigManager path still deosn't handle restoring the previous configuration, meaning the logical monitor with the external monitor will continue being primary. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 01:09:55 -05:00
.monitors = { 1 },
.n_monitors = 1,
monitor-unit-tests: Add laptop lid switch test case Test that the laptop panel is disabled if the lid is closed. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 22:50:44 -05:00
.layout = { .x = 1024, .y = 0, .width = 1024, .height = 768 },
.scale = 1
}
},
.n_logical_monitors = 2,
monitor-unit-tests: Check handling of the primary presentation flags The main output of the main (first) monitor of a primary logical monitor should have the MetaOutput::is_primary field set; all other outputs should have it not set. All outputs associated with a logical monitor with presentation set should have MetaOutput::is_presentation set. No other outputs should have it set. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 00:09:21 -05:00
.primary_logical_monitor = 0,
monitor-unit-tests: Add laptop lid switch test case Test that the laptop panel is disabled if the lid is closed. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 22:50:44 -05:00
.n_outputs = 2,
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
.crtcs = {
{
.current_mode = 0,
},
{
.current_mode = 0,
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
.x = 1024,
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
}
},
monitor-unit-tests: Add laptop lid switch test case Test that the laptop panel is disabled if the lid is closed. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 22:50:44 -05:00
.n_crtcs = 2,
.n_tiled_monitors = 0,
.screen_width = 1024 * 2,
.screen_height = 768
}
};
MetaMonitorTestSetup *test_setup;
MetaBackend *backend = meta_get_backend ();
MetaMonitorManager *monitor_manager =
meta_backend_get_monitor_manager (backend);
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Make hotplug_mode_update optional Add a flag to the test setup creation function enabling the caller to specify whether a stored config should be used. This is done by changing the value of the hotplug_mode_update MetaOutput field, normally used by VMs to do the same. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 23:32:12 -05:00
MONITOR_TEST_FLAG_NO_STORED);
monitor-unit-tests: Add laptop lid switch test case Test that the laptop panel is disabled if the lid is closed. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 22:50:44 -05:00
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Add laptop lid switch test case Test that the laptop panel is disabled if the lid is closed. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 22:50:44 -05:00
backend: Move lid-is-closed handling to MetaBackend Rather than handle UpClient in both MetaBackend (to reset the idletime when the lid is opened), and in MetaMonitorManager and MetaMonitorConfigManager (to turn the screen under the lid on/off depending on its status), move the ability to get the lid status from UPower or mock it in one place, in MetaBackend.
2018-04-16 14:07:45 -04:00
meta_backend_test_set_is_lid_closed (META_BACKEND_TEST (backend), TRUE);
monitor-unit-tests: Add laptop lid switch test case Test that the laptop panel is disabled if the lid is closed. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 22:50:44 -05:00
meta_monitor_manager_lid_is_closed_changed (monitor_manager);
monitor-unit-tests: Check monitor <-> logical monitor relationships Make sure that each logical monitor owns the expected actual monitors. This currently needs special care when dealing with laptop lid the configuration, as the MetaMonitorConfigManager path still deosn't handle restoring the previous configuration, meaning the logical monitor with the external monitor will continue being primary. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 01:09:55 -05:00
test_case.expect.logical_monitors[0] = (MonitorTestCaseLogicalMonitor) {
.monitors = { 1 },
.n_monitors = 1,
.layout = {.x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
};
monitor-unit-tests: Add laptop lid switch test case Test that the laptop panel is disabled if the lid is closed. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 22:50:44 -05:00
test_case.expect.n_logical_monitors = 1;
test_case.expect.screen_width = 1024;
test_case.expect.monitors[0].current_mode = -1;
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
test_case.expect.crtcs[0].current_mode = -1;
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
test_case.expect.crtcs[1].x = 0;
monitor-unit-tests: Add laptop lid switch test case Test that the laptop panel is disabled if the lid is closed. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 22:50:44 -05:00
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Add laptop lid switch test case Test that the laptop panel is disabled if the lid is closed. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 22:50:44 -05:00
backend: Move lid-is-closed handling to MetaBackend Rather than handle UpClient in both MetaBackend (to reset the idletime when the lid is opened), and in MetaMonitorManager and MetaMonitorConfigManager (to turn the screen under the lid on/off depending on its status), move the ability to get the lid status from UPower or mock it in one place, in MetaBackend.
2018-04-16 14:07:45 -04:00
meta_backend_test_set_is_lid_closed (META_BACKEND_TEST (backend), FALSE);
monitor-unit-tests: Add laptop lid switch test case Test that the laptop panel is disabled if the lid is closed. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 22:50:44 -05:00
meta_monitor_manager_lid_is_closed_changed (monitor_manager);
Remove old monitor configuration system Remove the old MetaMonitorConfig system and mark the new one as non-experimental. This also removes the D-Bus property. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-24 03:36:12 -04:00
test_case.expect.logical_monitors[0] = (MonitorTestCaseLogicalMonitor) {
.monitors = { 0 },
.n_monitors = 1,
monitor-manager: Try to restore previous config before regenerating When opening a laptop lid, one will likely want to restore the configuration one had prior to closing it, so when ensuring monitor configuration, first try to see if the previously set configuration is both complete (all connected monitors are configured) and applicable (it is a valid configuration) and only try to generate a new from scratch if that failed. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-08-11 03:21:36 -04:00
.layout = {.x = 0, .y = 0, .width = 1024, .height = 768 },
Remove old monitor configuration system Remove the old MetaMonitorConfig system and mark the new one as non-experimental. This also removes the D-Bus property. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-24 03:36:12 -04:00
.scale = 1
};
test_case.expect.n_logical_monitors = 2;
monitor-manager: Try to restore previous config before regenerating When opening a laptop lid, one will likely want to restore the configuration one had prior to closing it, so when ensuring monitor configuration, first try to see if the previously set configuration is both complete (all connected monitors are configured) and applicable (it is a valid configuration) and only try to generate a new from scratch if that failed. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-08-11 03:21:36 -04:00
test_case.expect.screen_width = 1024 * 2;
test_case.expect.monitors[0].current_mode = 0;
Remove old monitor configuration system Remove the old MetaMonitorConfig system and mark the new one as non-experimental. This also removes the D-Bus property. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-24 03:36:12 -04:00
test_case.expect.primary_logical_monitor = 0;
monitor-unit-tests: Check monitor <-> logical monitor relationships Make sure that each logical monitor owns the expected actual monitors. This currently needs special care when dealing with laptop lid the configuration, as the MetaMonitorConfigManager path still deosn't handle restoring the previous configuration, meaning the logical monitor with the external monitor will continue being primary. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 01:09:55 -05:00
monitor-manager: Try to restore previous config before regenerating When opening a laptop lid, one will likely want to restore the configuration one had prior to closing it, so when ensuring monitor configuration, first try to see if the previously set configuration is both complete (all connected monitors are configured) and applicable (it is a valid configuration) and only try to generate a new from scratch if that failed. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-08-11 03:21:36 -04:00
test_case.expect.crtcs[0].current_mode = 0;
test_case.expect.crtcs[1].current_mode = 0;
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
test_case.expect.crtcs[1].x = 1024;
monitor-manager: Try to restore previous config before regenerating When opening a laptop lid, one will likely want to restore the configuration one had prior to closing it, so when ensuring monitor configuration, first try to see if the previously set configuration is both complete (all connected monitors are configured) and applicable (it is a valid configuration) and only try to generate a new from scratch if that failed. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-08-11 03:21:36 -04:00
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Add laptop lid switch test case Test that the laptop panel is disabled if the lid is closed. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 22:50:44 -05:00
}
monitor-unit-tests: Test starting with lid closed Add a test case that checks that configuration works when the lid is initialy closed then later opened. This test case is disabled when the legacy configuration is used as it does not handle that situation. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-10 00:18:46 -05:00
static void
meta_test_monitor_lid_opened_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0
}
},
.n_modes = 1,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.is_laptop_panel = TRUE
},
{
.crtc = 1,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 1 },
.n_possible_crtcs = 1,
.width_mm = 220,
.height_mm = 124
}
},
.n_outputs = 2,
.crtcs = {
{
.current_mode = 0
},
{
.current_mode = 0
}
},
.n_crtcs = 2
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.0,
monitor-unit-tests: Test starting with lid closed Add a test case that checks that configuration works when the lid is initialy closed then later opened. This test case is disabled when the legacy configuration is used as it does not handle that situation. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-10 00:18:46 -05:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = -1,
.width_mm = 222,
.height_mm = 125
},
{
.outputs = { 1 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.0,
monitor-unit-tests: Test starting with lid closed Add a test case that checks that configuration works when the lid is initialy closed then later opened. This test case is disabled when the legacy configuration is used as it does not handle that situation. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-10 00:18:46 -05:00
.crtc_modes = {
{
.output = 1,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 220,
.height_mm = 124
}
},
.n_monitors = 2,
.logical_monitors = {
{
monitor-unit-tests: Check monitor <-> logical monitor relationships Make sure that each logical monitor owns the expected actual monitors. This currently needs special care when dealing with laptop lid the configuration, as the MetaMonitorConfigManager path still deosn't handle restoring the previous configuration, meaning the logical monitor with the external monitor will continue being primary. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 01:09:55 -05:00
.monitors = { 1 },
.n_monitors = 1,
monitor-unit-tests: Test starting with lid closed Add a test case that checks that configuration works when the lid is initialy closed then later opened. This test case is disabled when the legacy configuration is used as it does not handle that situation. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-10 00:18:46 -05:00
.layout = { .x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
},
{
monitor-unit-tests: Check monitor <-> logical monitor relationships Make sure that each logical monitor owns the expected actual monitors. This currently needs special care when dealing with laptop lid the configuration, as the MetaMonitorConfigManager path still deosn't handle restoring the previous configuration, meaning the logical monitor with the external monitor will continue being primary. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 01:09:55 -05:00
.monitors = { 0 },
.n_monitors = 1,
monitor-unit-tests: Test starting with lid closed Add a test case that checks that configuration works when the lid is initialy closed then later opened. This test case is disabled when the legacy configuration is used as it does not handle that situation. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-10 00:18:46 -05:00
.layout = { .x = 1024, .y = 0, .width = 1024, .height = 768 },
.scale = 1
}
},
.n_logical_monitors = 1, /* Second one checked after lid opened. */
monitor-unit-tests: Check handling of the primary presentation flags The main output of the main (first) monitor of a primary logical monitor should have the MetaOutput::is_primary field set; all other outputs should have it not set. All outputs associated with a logical monitor with presentation set should have MetaOutput::is_presentation set. No other outputs should have it set. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 00:09:21 -05:00
.primary_logical_monitor = 0,
monitor-unit-tests: Test starting with lid closed Add a test case that checks that configuration works when the lid is initialy closed then later opened. This test case is disabled when the legacy configuration is used as it does not handle that situation. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-10 00:18:46 -05:00
.n_outputs = 2,
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
.crtcs = {
{
.current_mode = -1,
},
{
.current_mode = 0,
}
},
monitor-unit-tests: Test starting with lid closed Add a test case that checks that configuration works when the lid is initialy closed then later opened. This test case is disabled when the legacy configuration is used as it does not handle that situation. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-10 00:18:46 -05:00
.n_crtcs = 2,
.n_tiled_monitors = 0,
.screen_width = 1024,
.screen_height = 768
}
};
MetaMonitorTestSetup *test_setup;
MetaBackend *backend = meta_get_backend ();
MetaMonitorManager *monitor_manager =
meta_backend_get_monitor_manager (backend);
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Make hotplug_mode_update optional Add a flag to the test setup creation function enabling the caller to specify whether a stored config should be used. This is done by changing the value of the hotplug_mode_update MetaOutput field, normally used by VMs to do the same. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 23:32:12 -05:00
MONITOR_TEST_FLAG_NO_STORED);
backend: Move lid-is-closed handling to MetaBackend Rather than handle UpClient in both MetaBackend (to reset the idletime when the lid is opened), and in MetaMonitorManager and MetaMonitorConfigManager (to turn the screen under the lid on/off depending on its status), move the ability to get the lid status from UPower or mock it in one place, in MetaBackend.
2018-04-16 14:07:45 -04:00
meta_backend_test_set_is_lid_closed (META_BACKEND_TEST (backend), TRUE);
monitor-unit-tests: Test starting with lid closed Add a test case that checks that configuration works when the lid is initialy closed then later opened. This test case is disabled when the legacy configuration is used as it does not handle that situation. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-10 00:18:46 -05:00
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Test starting with lid closed Add a test case that checks that configuration works when the lid is initialy closed then later opened. This test case is disabled when the legacy configuration is used as it does not handle that situation. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-10 00:18:46 -05:00
backend: Move lid-is-closed handling to MetaBackend Rather than handle UpClient in both MetaBackend (to reset the idletime when the lid is opened), and in MetaMonitorManager and MetaMonitorConfigManager (to turn the screen under the lid on/off depending on its status), move the ability to get the lid status from UPower or mock it in one place, in MetaBackend.
2018-04-16 14:07:45 -04:00
meta_backend_test_set_is_lid_closed (META_BACKEND_TEST (backend), FALSE);
monitor-unit-tests: Test starting with lid closed Add a test case that checks that configuration works when the lid is initialy closed then later opened. This test case is disabled when the legacy configuration is used as it does not handle that situation. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-10 00:18:46 -05:00
meta_monitor_manager_lid_is_closed_changed (monitor_manager);
test_case.expect.n_logical_monitors = 2;
test_case.expect.screen_width = 1024 * 2;
test_case.expect.monitors[0].current_mode = 0;
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
test_case.expect.crtcs[0].current_mode = 0;
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
test_case.expect.crtcs[0].x = 1024;
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
test_case.expect.crtcs[1].current_mode = 0;
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
test_case.expect.crtcs[1].x = 0;
monitor-unit-tests: Test starting with lid closed Add a test case that checks that configuration works when the lid is initialy closed then later opened. This test case is disabled when the legacy configuration is used as it does not handle that situation. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-10 00:18:46 -05:00
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Test starting with lid closed Add a test case that checks that configuration works when the lid is initialy closed then later opened. This test case is disabled when the legacy configuration is used as it does not handle that situation. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-10 00:18:46 -05:00
}
monitor-unit-tests: Add lid-closed with no external monitor test case Test that when the laptop lid is closed, but no external monitors are connected, that we still have a mode set on the laptop panel. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 00:42:42 -05:00
static void
meta_test_monitor_lid_closed_no_external (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0
}
},
.n_modes = 1,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.is_laptop_panel = TRUE
}
},
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0
}
},
.n_crtcs = 1
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.0,
monitor-unit-tests: Add lid-closed with no external monitor test case Test that when the laptop lid is closed, but no external monitors are connected, that we still have a mode set on the laptop panel. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 00:42:42 -05:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125
}
},
.n_monitors = 1,
.logical_monitors = {
{
monitor-unit-tests: Check monitor <-> logical monitor relationships Make sure that each logical monitor owns the expected actual monitors. This currently needs special care when dealing with laptop lid the configuration, as the MetaMonitorConfigManager path still deosn't handle restoring the previous configuration, meaning the logical monitor with the external monitor will continue being primary. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 01:09:55 -05:00
.monitors = { 0 },
.n_monitors = 1,
monitor-unit-tests: Add lid-closed with no external monitor test case Test that when the laptop lid is closed, but no external monitors are connected, that we still have a mode set on the laptop panel. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 00:42:42 -05:00
.layout = { .x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
}
},
.n_logical_monitors = 1,
monitor-unit-tests: Check handling of the primary presentation flags The main output of the main (first) monitor of a primary logical monitor should have the MetaOutput::is_primary field set; all other outputs should have it not set. All outputs associated with a logical monitor with presentation set should have MetaOutput::is_presentation set. No other outputs should have it set. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 00:09:21 -05:00
.primary_logical_monitor = 0,
monitor-unit-tests: Add lid-closed with no external monitor test case Test that when the laptop lid is closed, but no external monitors are connected, that we still have a mode set on the laptop panel. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 00:42:42 -05:00
.n_outputs = 1,
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
.crtcs = {
{
.current_mode = 0,
},
},
monitor-unit-tests: Add lid-closed with no external monitor test case Test that when the laptop lid is closed, but no external monitors are connected, that we still have a mode set on the laptop panel. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 00:42:42 -05:00
.n_crtcs = 1,
.n_tiled_monitors = 0,
.screen_width = 1024,
.screen_height = 768
}
};
MetaMonitorTestSetup *test_setup;
MetaBackend *backend = meta_get_backend ();
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Make hotplug_mode_update optional Add a flag to the test setup creation function enabling the caller to specify whether a stored config should be used. This is done by changing the value of the hotplug_mode_update MetaOutput field, normally used by VMs to do the same. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 23:32:12 -05:00
MONITOR_TEST_FLAG_NO_STORED);
backend: Move lid-is-closed handling to MetaBackend Rather than handle UpClient in both MetaBackend (to reset the idletime when the lid is opened), and in MetaMonitorManager and MetaMonitorConfigManager (to turn the screen under the lid on/off depending on its status), move the ability to get the lid status from UPower or mock it in one place, in MetaBackend.
2018-04-16 14:07:45 -04:00
meta_backend_test_set_is_lid_closed (META_BACKEND_TEST (backend), TRUE);
monitor-unit-tests: Add lid-closed with no external monitor test case Test that when the laptop lid is closed, but no external monitors are connected, that we still have a mode set on the laptop panel. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 00:42:42 -05:00
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Add lid-closed with no external monitor test case Test that when the laptop lid is closed, but no external monitors are connected, that we still have a mode set on the laptop panel. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 00:42:42 -05:00
}
monitor-unit-tests: Add test for lid closed after hot plug Add a test case that checks that we don't try to revert to a laptop-panel-only configuration after closing the lid after an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-03 04:11:27 -04:00
static void
meta_test_monitor_lid_closed_with_hotplugged_external (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0
}
},
.n_modes = 1,
.outputs = {
{
.crtc = -1,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.is_laptop_panel = TRUE
},
{
.crtc = -1,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 1 },
.n_possible_crtcs = 1,
.width_mm = 220,
.height_mm = 124
}
},
.n_outputs = 1, /* Second is hotplugged later */
.crtcs = {
{
.current_mode = -1
},
{
.current_mode = -1
}
},
.n_crtcs = 2
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0,
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125
},
{
.outputs = { 1 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0,
.crtc_modes = {
{
.output = 1,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 220,
.height_mm = 124
}
},
.n_monitors = 1, /* Second is hotplugged later */
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
},
{
.monitors = { 1 },
.n_monitors = 1,
.layout = { .x = 1024, .y = 0, .width = 1024, .height = 768 },
.scale = 1
}
},
.n_logical_monitors = 1, /* Second is hotplugged later */
.primary_logical_monitor = 0,
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0,
},
{
.current_mode = -1,
}
},
.n_crtcs = 2,
.n_tiled_monitors = 0,
.screen_width = 1024,
.screen_height = 768
}
};
MetaMonitorTestSetup *test_setup;
MetaBackend *backend = meta_get_backend ();
monitor-unit-tests: Add test for lid toggle after hot unplug https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 00:33:38 -05:00
/*
* The first part of this test emulate the following:
* 1) Start with the lid open
* 2) Connect external monitor
* 3) Close lid
*/
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Add test for lid closed after hot plug Add a test case that checks that we don't try to revert to a laptop-panel-only configuration after closing the lid after an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-03 04:11:27 -04:00
MONITOR_TEST_FLAG_NO_STORED);
backend: Move lid-is-closed handling to MetaBackend Rather than handle UpClient in both MetaBackend (to reset the idletime when the lid is opened), and in MetaMonitorManager and MetaMonitorConfigManager (to turn the screen under the lid on/off depending on its status), move the ability to get the lid status from UPower or mock it in one place, in MetaBackend.
2018-04-16 14:07:45 -04:00
meta_backend_test_set_is_lid_closed (META_BACKEND_TEST (backend), FALSE);
monitor-unit-tests: Add test for lid closed after hot plug Add a test case that checks that we don't try to revert to a laptop-panel-only configuration after closing the lid after an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-03 04:11:27 -04:00
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Add test for lid closed after hot plug Add a test case that checks that we don't try to revert to a laptop-panel-only configuration after closing the lid after an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-03 04:11:27 -04:00
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("External monitor connected");
monitor-unit-tests: Add test for lid closed after hot plug Add a test case that checks that we don't try to revert to a laptop-panel-only configuration after closing the lid after an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-03 04:11:27 -04:00
test_case.setup.n_outputs = 2;
test_case.expect.n_outputs = 2;
test_case.expect.n_monitors = 2;
test_case.expect.n_logical_monitors = 2;
test_case.expect.crtcs[1].current_mode = 0;
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
test_case.expect.crtcs[1].x = 1024;
monitor-unit-tests: Add test for lid closed after hot plug Add a test case that checks that we don't try to revert to a laptop-panel-only configuration after closing the lid after an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-03 04:11:27 -04:00
test_case.expect.screen_width = 1024 * 2;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Add test for lid closed after hot plug Add a test case that checks that we don't try to revert to a laptop-panel-only configuration after closing the lid after an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-03 04:11:27 -04:00
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Add test for lid closed after hot plug Add a test case that checks that we don't try to revert to a laptop-panel-only configuration after closing the lid after an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-03 04:11:27 -04:00
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("Lid closed");
monitor-unit-tests: Add test for lid closed after hot plug Add a test case that checks that we don't try to revert to a laptop-panel-only configuration after closing the lid after an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-03 04:11:27 -04:00
test_case.expect.monitors[0].current_mode = -1;
test_case.expect.logical_monitors[0].monitors[0] = 1,
test_case.expect.n_logical_monitors = 1;
test_case.expect.crtcs[0].current_mode = -1;
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
test_case.expect.crtcs[1].x = 0;
monitor-unit-tests: Add test for lid closed after hot plug Add a test case that checks that we don't try to revert to a laptop-panel-only configuration after closing the lid after an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-03 04:11:27 -04:00
test_case.expect.screen_width = 1024;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Add test for lid closed after hot plug Add a test case that checks that we don't try to revert to a laptop-panel-only configuration after closing the lid after an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-03 04:11:27 -04:00
MONITOR_TEST_FLAG_NO_STORED);
backend: Move lid-is-closed handling to MetaBackend Rather than handle UpClient in both MetaBackend (to reset the idletime when the lid is opened), and in MetaMonitorManager and MetaMonitorConfigManager (to turn the screen under the lid on/off depending on its status), move the ability to get the lid status from UPower or mock it in one place, in MetaBackend.
2018-04-16 14:07:45 -04:00
meta_backend_test_set_is_lid_closed (META_BACKEND_TEST (backend), TRUE);
monitor-unit-tests: Add test for lid closed after hot plug Add a test case that checks that we don't try to revert to a laptop-panel-only configuration after closing the lid after an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-03 04:11:27 -04:00
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Add test for lid toggle after hot unplug https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 00:33:38 -05:00
/*
* The second part of this test emulate the following:
* 1) Open lid
* 2) Disconnect external monitor
* 3) Close lid
* 4) Open lid
*/
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("Lid opened");
monitor-unit-tests: Add test for lid toggle after hot unplug https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 00:33:38 -05:00
test_case.expect.monitors[0].current_mode = 0;
test_case.expect.logical_monitors[0].monitors[0] = 0,
test_case.expect.logical_monitors[1].monitors[0] = 1,
test_case.expect.n_logical_monitors = 2;
test_case.expect.crtcs[0].current_mode = 0;
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
test_case.expect.crtcs[1].x = 1024;
monitor-unit-tests: Add test for lid toggle after hot unplug https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 00:33:38 -05:00
test_case.expect.screen_width = 1024 * 2;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Add test for lid toggle after hot unplug https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 00:33:38 -05:00
MONITOR_TEST_FLAG_NO_STORED);
backend: Move lid-is-closed handling to MetaBackend Rather than handle UpClient in both MetaBackend (to reset the idletime when the lid is opened), and in MetaMonitorManager and MetaMonitorConfigManager (to turn the screen under the lid on/off depending on its status), move the ability to get the lid status from UPower or mock it in one place, in MetaBackend.
2018-04-16 14:07:45 -04:00
meta_backend_test_set_is_lid_closed (META_BACKEND_TEST (backend), FALSE);
monitor-unit-tests: Add test for lid toggle after hot unplug https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 00:33:38 -05:00
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Add test for lid toggle after hot unplug https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 00:33:38 -05:00
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("External monitor disconnected");
monitor-unit-tests: Add test for lid toggle after hot unplug https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 00:33:38 -05:00
test_case.setup.n_outputs = 1;
test_case.expect.n_outputs = 1;
test_case.expect.n_monitors = 1;
test_case.expect.n_logical_monitors = 1;
test_case.expect.crtcs[1].current_mode = -1;
test_case.expect.screen_width = 1024;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Add test for lid toggle after hot unplug https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 00:33:38 -05:00
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Add test for lid toggle after hot unplug https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 00:33:38 -05:00
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("Lid closed");
monitor-unit-tests: Add test for lid toggle after hot unplug https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 00:33:38 -05:00
test_case.expect.logical_monitors[0].monitors[0] = 0,
test_case.expect.n_logical_monitors = 1;
test_case.expect.screen_width = 1024;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Add test for lid toggle after hot unplug https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 00:33:38 -05:00
MONITOR_TEST_FLAG_NO_STORED);
backend: Move lid-is-closed handling to MetaBackend Rather than handle UpClient in both MetaBackend (to reset the idletime when the lid is opened), and in MetaMonitorManager and MetaMonitorConfigManager (to turn the screen under the lid on/off depending on its status), move the ability to get the lid status from UPower or mock it in one place, in MetaBackend.
2018-04-16 14:07:45 -04:00
meta_backend_test_set_is_lid_closed (META_BACKEND_TEST (backend), TRUE);
monitor-unit-tests: Add test for lid toggle after hot unplug https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 00:33:38 -05:00
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Add test for lid toggle after hot unplug https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 00:33:38 -05:00
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("Lid opened");
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Add test for lid toggle after hot unplug https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 00:33:38 -05:00
MONITOR_TEST_FLAG_NO_STORED);
backend: Move lid-is-closed handling to MetaBackend Rather than handle UpClient in both MetaBackend (to reset the idletime when the lid is opened), and in MetaMonitorManager and MetaMonitorConfigManager (to turn the screen under the lid on/off depending on its status), move the ability to get the lid status from UPower or mock it in one place, in MetaBackend.
2018-04-16 14:07:45 -04:00
meta_backend_test_set_is_lid_closed (META_BACKEND_TEST (backend), FALSE);
monitor-unit-tests: Add test for lid toggle after hot unplug https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 00:33:38 -05:00
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Add test for lid closed after hot plug Add a test case that checks that we don't try to revert to a laptop-panel-only configuration after closing the lid after an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-03 04:11:27 -04:00
}
monitor-unit-tests: Ensure configuration is preserved in laptop with closed lid https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1200
2020-04-16 04:58:43 -04:00
static void
meta_test_monitor_lid_scaled_closed_opened (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1920,
.height = 1080,
.refresh_rate = 60.000495910644531
}
},
.n_modes = 1,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.is_laptop_panel = TRUE
},
},
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0
},
},
.n_crtcs = 1
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1920,
.height = 1080,
.refresh_rate = 60.000495910644531,
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
}
},
.n_monitors = 1,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 960, .height = 540 },
.scale = 2
}
},
.n_logical_monitors = 1,
.primary_logical_monitor = 0,
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0,
}
},
.n_crtcs = 1,
.n_tiled_monitors = 0,
.screen_width = 960,
.screen_height = 540
}
};
MetaMonitorTestSetup *test_setup;
MetaBackend *backend = meta_get_backend ();
MetaMonitorManager *monitor_manager =
meta_backend_get_monitor_manager (backend);
if (!meta_is_stage_views_enabled ())
{
g_test_skip ("Not using stage views");
return;
}
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Ensure configuration is preserved in laptop with closed lid https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1200
2020-04-16 04:58:43 -04:00
MONITOR_TEST_FLAG_NONE);
set_custom_monitor_config ("lid-scale.xml");
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Ensure configuration is preserved in laptop with closed lid https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1200
2020-04-16 04:58:43 -04:00
meta_backend_test_set_is_lid_closed (META_BACKEND_TEST (backend), TRUE);
meta_monitor_manager_lid_is_closed_changed (monitor_manager);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Ensure configuration is preserved in laptop with closed lid https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1200
2020-04-16 04:58:43 -04:00
meta_backend_test_set_is_lid_closed (META_BACKEND_TEST (backend), FALSE);
meta_monitor_manager_lid_is_closed_changed (monitor_manager);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Ensure configuration is preserved in laptop with closed lid https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1200
2020-04-16 04:58:43 -04:00
}
monitor-unit-tests: Test headless mode This tests only the monitor configuration and basic functionality. It does not test anything related to window management and Wayland client interaction. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 00:51:43 -05:00
static void
meta_test_monitor_no_outputs (void)
{
MonitorTestCase test_case = {
.setup = {
.n_modes = 0,
.n_outputs = 0,
.n_crtcs = 0
},
.expect = {
.n_monitors = 0,
.n_logical_monitors = 0,
monitor-unit-tests: Check handling of the primary presentation flags The main output of the main (first) monitor of a primary logical monitor should have the MetaOutput::is_primary field set; all other outputs should have it not set. All outputs associated with a logical monitor with presentation set should have MetaOutput::is_presentation set. No other outputs should have it set. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 00:09:21 -05:00
.primary_logical_monitor = -1,
monitor-unit-tests: Test headless mode This tests only the monitor configuration and basic functionality. It does not test anything related to window management and Wayland client interaction. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 00:51:43 -05:00
.n_outputs = 0,
.n_crtcs = 0,
.n_tiled_monitors = 0,
monitor-manager: Fall back to minimum screen size of 640 x 480 When headless, we don't have any logical monitors to derive a screen size from, but we can't set it to empty as that will cause issues with the clutter stage, UI widget layout and other things. To avoid such issues, just fall back to a 640 x 480 screen size when headless. https://bugzilla.gnome.org/show_bug.cgi?id=730551
2017-04-12 02:15:33 -04:00
.screen_width = META_MONITOR_MANAGER_MIN_SCREEN_WIDTH,
.screen_height = META_MONITOR_MANAGER_MIN_SCREEN_HEIGHT
monitor-unit-tests: Test headless mode This tests only the monitor configuration and basic functionality. It does not test anything related to window management and Wayland client interaction. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 00:51:43 -05:00
}
};
MetaMonitorTestSetup *test_setup;
monitor-unit-tests: Try resizing clients while headless Prior to 6dcce19932 this test would crash. https://bugzilla.gnome.org/show_bug.cgi?id=790207
2018-02-06 02:40:44 -05:00
GError *error = NULL;
monitor-unit-tests: Test headless mode This tests only the monitor configuration and basic functionality. It does not test anything related to window management and Wayland client interaction. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 00:51:43 -05:00
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Make hotplug_mode_update optional Add a flag to the test setup creation function enabling the caller to specify whether a stored config should be used. This is done by changing the value of the hotplug_mode_update MetaOutput field, normally used by VMs to do the same. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 23:32:12 -05:00
MONITOR_TEST_FLAG_NO_STORED);
monitor-unit-tests: Test headless mode This tests only the monitor configuration and basic functionality. It does not test anything related to window management and Wayland client interaction. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 00:51:43 -05:00
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Check going headless -> headless https://bugzilla.gnome.org/show_bug.cgi?id=788607
2017-10-07 00:35:23 -04:00
tests/utils: Prefix TestClient with Meta Soon we'll expose it via a libmutter-test library. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-06 17:34:36 -04:00
if (!meta_test_client_do (x11_monitor_test_client, &error,
"resize", X11_TEST_CLIENT_WINDOW,
"123", "210",
NULL))
monitor-unit-tests: Try resizing clients while headless Prior to 6dcce19932 this test would crash. https://bugzilla.gnome.org/show_bug.cgi?id=790207
2018-02-06 02:40:44 -05:00
g_error ("Failed to resize X11 window: %s", error->message);
tests/utils: Prefix TestClient with Meta Soon we'll expose it via a libmutter-test library. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-06 17:34:36 -04:00
if (!meta_test_client_do (wayland_monitor_test_client, &error,
"resize", WAYLAND_TEST_CLIENT_WINDOW,
"123", "210",
NULL))
monitor-unit-tests: Try resizing clients while headless Prior to 6dcce19932 this test would crash. https://bugzilla.gnome.org/show_bug.cgi?id=790207
2018-02-06 02:40:44 -05:00
g_error ("Failed to resize Wayland window: %s", error->message);
check_monitor_test_clients_state ();
monitor-unit-tests: Check going headless -> headless https://bugzilla.gnome.org/show_bug.cgi?id=788607
2017-10-07 00:35:23 -04:00
/* Also check that we handle going headless -> headless */
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Check going headless -> headless https://bugzilla.gnome.org/show_bug.cgi?id=788607
2017-10-07 00:35:23 -04:00
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Test headless mode This tests only the monitor configuration and basic functionality. It does not test anything related to window management and Wayland client interaction. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 00:51:43 -05:00
}
tests: Add monitor store and config test for output underscanning https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 22:34:23 -05:00
static void
meta_test_monitor_underscanning_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0
}
},
.n_modes = 1,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.is_underscanning = TRUE,
}
},
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0
}
},
.n_crtcs = 1
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.0,
tests: Add monitor store and config test for output underscanning https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 22:34:23 -05:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
.is_underscanning = TRUE,
}
},
.n_monitors = 1,
.logical_monitors = {
{
monitor-unit-tests: Check monitor <-> logical monitor relationships Make sure that each logical monitor owns the expected actual monitors. This currently needs special care when dealing with laptop lid the configuration, as the MetaMonitorConfigManager path still deosn't handle restoring the previous configuration, meaning the logical monitor with the external monitor will continue being primary. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 01:09:55 -05:00
.monitors = { 0 },
.n_monitors = 1,
tests: Add monitor store and config test for output underscanning https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 22:34:23 -05:00
.layout = { .x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
}
},
.n_logical_monitors = 1,
.primary_logical_monitor = 0,
.n_outputs = 1,
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
.crtcs = {
{
.current_mode = 0,
}
},
tests: Add monitor store and config test for output underscanning https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 22:34:23 -05:00
.n_crtcs = 1,
.screen_width = 1024,
.screen_height = 768
}
};
MetaMonitorTestSetup *test_setup;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
tests: Add monitor store and config test for output underscanning https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 22:34:23 -05:00
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
tests: Add monitor store and config test for output underscanning https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 22:34:23 -05:00
}
monitor-unit-tests: Check non-first preferred modes Check that if there are multiple modes with the same ID (resolution, refresh rate and handled flags) we correctly add the preferred mode to the list of monitor modes. https://bugzilla.gnome.org/show_bug.cgi?id=789153
2017-10-18 11:24:36 -04:00
static void
meta_test_monitor_preferred_non_first_mode (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 800,
.height = 600,
.refresh_rate = 60.0,
.flags = META_CRTC_MODE_FLAG_NHSYNC,
},
{
.width = 800,
.height = 600,
.refresh_rate = 60.0,
.flags = META_CRTC_MODE_FLAG_PHSYNC,
},
},
.n_modes = 2,
.outputs = {
{
.crtc = -1,
.modes = { 0, 1 },
.n_modes = 2,
.preferred_mode = 1,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125
}
},
.n_outputs = 1,
.crtcs = {
{
.current_mode = -1
}
},
.n_crtcs = 1
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 800,
.height = 600,
.refresh_rate = 60.0,
.crtc_modes = {
{
.output = 0,
.crtc_mode = 1
}
}
},
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125
}
},
.n_monitors = 1,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 800, .height = 600 },
.scale = 1
},
},
.n_logical_monitors = 1,
.primary_logical_monitor = 0,
.n_outputs = 1,
.crtcs = {
{
.current_mode = 1,
}
},
.n_crtcs = 1,
.screen_width = 800,
.screen_height = 600,
}
};
MetaMonitorTestSetup *test_setup;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Check non-first preferred modes Check that if there are multiple modes with the same ID (resolution, refresh rate and handled flags) we correctly add the preferred mode to the list of monitor modes. https://bugzilla.gnome.org/show_bug.cgi?id=789153
2017-10-18 11:24:36 -04:00
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Check non-first preferred modes Check that if there are multiple modes with the same ID (resolution, refresh rate and handled flags) we correctly add the preferred mode to the list of monitor modes. https://bugzilla.gnome.org/show_bug.cgi?id=789153
2017-10-18 11:24:36 -04:00
}
monitor-unit-tests: Add non upright panel test https://bugzilla.gnome.org/show_bug.cgi?id=782294
2017-10-26 05:50:10 -04:00
static void
meta_test_monitor_non_upright_panel (void)
{
MonitorTestCase test_case = initial_test_case;
MetaMonitorTestSetup *test_setup;
test_case.setup.modes[1] = (MonitorTestCaseMode) {
.width = 768,
.height = 1024,
.refresh_rate = 60.0,
};
test_case.setup.n_modes = 2;
test_case.setup.outputs[0].modes[0] = 1;
test_case.setup.outputs[0].preferred_mode = 1;
test_case.setup.outputs[0].panel_orientation_transform =
META_MONITOR_TRANSFORM_90;
/*
* Note we do not swap outputs[0].width_mm and height_mm, because these get
* swapped for rotated panels inside the xrandr / kms code and we directly
* create a dummy output here, skipping this code.
*/
test_case.setup.crtcs[0].current_mode = 1;
test_case.expect.monitors[0].modes[0].crtc_modes[0].crtc_mode = 1;
test_case.expect.crtcs[0].current_mode = 1;
test_case.expect.crtcs[0].transform = META_MONITOR_TRANSFORM_90;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Add non upright panel test https://bugzilla.gnome.org/show_bug.cgi?id=782294
2017-10-26 05:50:10 -04:00
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Add non upright panel test https://bugzilla.gnome.org/show_bug.cgi?id=782294
2017-10-26 05:50:10 -04:00
}
monitor-config-manager: Handle multiple builtin panels gracefully While multiple built-in panels isn't actually supported in any meaningful manner, if we would ever end up with such a situation, e.g. due to kernel bugs[0], we shouldn't crash when trying to set an 'external only' without any external monitors. While we could handle this with more degraded functionality (e.g. don't support the 'switch' method of monitor configuration at all), handle it by simply not trying to switch to external-only when there are no, according to the kernel, external monitors available. This would e.g. still allow betwene 'mirror-all', and 'linear' switches. The crash itself was disguised as an arbitrary X11 BadValue error, due to mutter trying to resize the root window to 0x0, as the monitor configuration that was applied consisted of zero logical monitors, thus was effectively empty. [0] https://bugzilla.redhat.com/show_bug.cgi?id=1896904 Related: https://bugzilla.redhat.com/show_bug.cgi?id=1899260 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1607>
2020-11-27 03:03:38 -05:00
static void
meta_test_monitor_switch_external_without_external (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0
}
},
.n_modes = 1,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.is_laptop_panel = TRUE
},
{
.crtc = 1,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 1 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.is_laptop_panel = TRUE
}
},
.n_outputs = 2,
.crtcs = {
{
.current_mode = 0
},
{
.current_mode = 0
}
},
.n_crtcs = 2
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0,
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125
},
{
.outputs = { 1 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0,
.crtc_modes = {
{
.output = 1,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125
}
},
.n_monitors = 2,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
},
{
.monitors = { 1 },
.n_monitors = 1,
.layout = { .x = 1024, .y = 0, .width = 1024, .height = 768 },
.scale = 1
}
},
.n_logical_monitors = 2,
.primary_logical_monitor = 0,
.n_outputs = 2,
.crtcs = {
{
.current_mode = 0,
},
{
.current_mode = 0,
.x = 1024,
},
},
.n_crtcs = 2,
.n_tiled_monitors = 0,
.screen_width = 2048,
.screen_height = 768
}
};
MetaMonitorTestSetup *test_setup;
MetaBackend *backend = meta_get_backend ();
MetaMonitorManager *monitor_manager =
meta_backend_get_monitor_manager (backend);
test_setup = create_monitor_test_setup (&test_case.setup,
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
monitor-config-manager: Handle multiple builtin panels gracefully While multiple built-in panels isn't actually supported in any meaningful manner, if we would ever end up with such a situation, e.g. due to kernel bugs[0], we shouldn't crash when trying to set an 'external only' without any external monitors. While we could handle this with more degraded functionality (e.g. don't support the 'switch' method of monitor configuration at all), handle it by simply not trying to switch to external-only when there are no, according to the kernel, external monitors available. This would e.g. still allow betwene 'mirror-all', and 'linear' switches. The crash itself was disguised as an arbitrary X11 BadValue error, due to mutter trying to resize the root window to 0x0, as the monitor configuration that was applied consisted of zero logical monitors, thus was effectively empty. [0] https://bugzilla.redhat.com/show_bug.cgi?id=1896904 Related: https://bugzilla.redhat.com/show_bug.cgi?id=1899260 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1607>
2020-11-27 03:03:38 -05:00
meta_monitor_manager_switch_config (monitor_manager,
META_MONITOR_SWITCH_CONFIG_EXTERNAL);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
monitor-config-manager: Handle multiple builtin panels gracefully While multiple built-in panels isn't actually supported in any meaningful manner, if we would ever end up with such a situation, e.g. due to kernel bugs[0], we shouldn't crash when trying to set an 'external only' without any external monitors. While we could handle this with more degraded functionality (e.g. don't support the 'switch' method of monitor configuration at all), handle it by simply not trying to switch to external-only when there are no, according to the kernel, external monitors available. This would e.g. still allow betwene 'mirror-all', and 'linear' switches. The crash itself was disguised as an arbitrary X11 BadValue error, due to mutter trying to resize the root window to 0x0, as the monitor configuration that was applied consisted of zero logical monitors, thus was effectively empty. [0] https://bugzilla.redhat.com/show_bug.cgi?id=1896904 Related: https://bugzilla.redhat.com/show_bug.cgi?id=1899260 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1607>
2020-11-27 03:03:38 -05:00
check_monitor_test_clients_state ();
}
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
static void
monitor-unit-tests: Take panel orientation transform in account When checking panel orientation on logical monitors we should take panel orientation transform to check it's properly applied, so ensure that we're checking the right one. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 04:09:12 -05:00
check_monitor_configuration_per_orientation (MonitorTestCase *test_case,
unsigned int monitor_index,
MetaOrientation orientation,
int width,
int height)
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
{
MetaMonitorTransform transform;
monitor-unit-tests: Take panel orientation transform in account When checking panel orientation on logical monitors we should take panel orientation transform to check it's properly applied, so ensure that we're checking the right one. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 04:09:12 -05:00
MetaMonitorTransform output_transform;
MonitorTestCaseExpect expect = test_case->expect;
MonitorTestCaseSetup *setup = &test_case->setup;
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
int i = 0;
transform = meta_monitor_transform_from_orientation (orientation);
monitor-unit-tests: Take panel orientation transform in account When checking panel orientation on logical monitors we should take panel orientation transform to check it's properly applied, so ensure that we're checking the right one. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 04:09:12 -05:00
output_transform = setup->outputs[monitor_index].panel_orientation_transform;
expect.logical_monitors[monitor_index].transform =
meta_monitor_transform_transform (transform,
meta_monitor_transform_invert (output_transform));
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
expect.crtcs[monitor_index].transform = transform;
if (meta_monitor_transform_is_rotated (transform))
{
expect.logical_monitors[monitor_index].layout.width = height;
expect.logical_monitors[monitor_index].layout.height = width;
}
else
{
expect.logical_monitors[monitor_index].layout.width = width;
expect.logical_monitors[monitor_index].layout.height = height;
}
expect.screen_width = 0;
expect.screen_height = 0;
for (i = 0; i < expect.n_logical_monitors; ++i)
{
MonitorTestCaseLogicalMonitor *monitor =
&expect.logical_monitors[i];
int right_edge;
int bottom_edge;
g_debug ("Got monitor %dx%d : %dx%d", monitor->layout.x,
monitor->layout.y, monitor->layout.width, monitor->layout.height);
right_edge = (monitor->layout.width + monitor->layout.x);
if (right_edge > expect.screen_width)
expect.screen_width = right_edge;
bottom_edge = (monitor->layout.height + monitor->layout.y);
if (bottom_edge > expect.screen_height)
expect.screen_height = bottom_edge;
}
check_monitor_configuration (&expect);
check_monitor_test_clients_state ();
}
typedef MetaSensorsProxyMock MetaSensorsProxyAutoResetMock;
static void
meta_sensors_proxy_reset (MetaSensorsProxyMock *proxy)
{
orientation-manager: Use an idle to apply monitor orientation changes In X11 when we switch to another tty all the the signals are blocked (as the display fd is not replying back to polling, causing the main loop to stop), and they are all handled once we switch back to the tty. This is not a problem for most of external events, but in case of accelerometer changes, once we reactivate a mutter session we'll get them all together, causing lots of monitor reconfigurations leading to black screen for some seconds and most of the times to a wrong configuration being applied. To avoid this, batch all these events using an idle to only apply the last one we got in a loop. Fixes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1217 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-01 10:32:46 -04:00
MetaBackend *backend = meta_get_backend ();
MetaOrientationManager *orientation_manager =
meta_backend_get_orientation_manager (backend);
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("Resetting proxy");
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
meta_sensors_proxy_mock_set_orientation (proxy,
META_ORIENTATION_NORMAL);
tests: Move orientation helper to monitor test utils It was used by both the orientation tests, and the monitor configuration tests. Lets move the helper to common ground. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2021-09-30 08:47:11 -04:00
meta_wait_for_orientation (orientation_manager, META_ORIENTATION_NORMAL, NULL);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
g_object_unref (proxy);
}
G_DEFINE_AUTOPTR_CLEANUP_FUNC (MetaSensorsProxyAutoResetMock,
meta_sensors_proxy_reset)
static ClutterInputDevice *
meta_test_add_touch_device (MetaBackend * backend)
{
MetaBackendTest *backend_test = META_BACKEND_TEST (backend);
ClutterInputDevice *device;
device = meta_backend_test_add_test_device (backend_test, "test-touchscreen",
CLUTTER_TOUCHSCREEN_DEVICE, 1);
g_assert_true (CLUTTER_IS_INPUT_DEVICE (device));
g_assert_cmpuint (clutter_input_device_get_device_type (device),
==,
CLUTTER_TOUCHSCREEN_DEVICE);
return device;
}
typedef ClutterInputDevice ClutterAutoRemoveInputDevice;
static void
input_device_test_remove (ClutterAutoRemoveInputDevice *device)
{
MetaBackend *backend = meta_get_backend ();
meta_backend_test_remove_device (META_BACKEND_TEST (backend), device);
g_object_unref (device);
}
G_DEFINE_AUTOPTR_CLEANUP_FUNC (ClutterAutoRemoveInputDevice,
input_device_test_remove)
static void
meta_test_monitor_orientation_is_managed (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0
}
},
.n_modes = 1,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.is_laptop_panel = FALSE,
}
},
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0
}
},
.n_crtcs = 1
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0,
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125
}
},
.n_monitors = 1,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
}
},
.n_logical_monitors = 1,
.primary_logical_monitor = 0,
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0,
},
},
.n_crtcs = 1,
.n_tiled_monitors = 0,
.screen_width = 1024,
.screen_height = 768
}
};
MetaMonitorTestSetup *test_setup;
MetaBackend *backend = meta_get_backend ();
MetaOrientationManager *orientation_manager =
meta_backend_get_orientation_manager (backend);
MetaMonitorManager *monitor_manager =
meta_backend_get_monitor_manager (backend);
ClutterBackend *clutter_backend = meta_backend_get_clutter_backend (backend);
ClutterSeat *seat = clutter_backend_get_default_seat (clutter_backend);
g_autoptr (ClutterAutoRemoveInputDevice) touch_device = NULL;
g_autoptr (MetaSensorsProxyAutoResetMock) orientation_mock = NULL;
test_setup = create_monitor_test_setup (&test_case.setup,
MONITOR_TEST_FLAG_NO_STORED);
g_assert_false (
meta_monitor_manager_get_panel_orientation_managed (monitor_manager));
emulate_hotplug (test_setup);
check_monitor_configuration (&test_case.expect);
check_monitor_test_clients_state ();
g_assert_false (
meta_monitor_manager_get_panel_orientation_managed (monitor_manager));
g_assert_null (meta_monitor_manager_get_laptop_panel (monitor_manager));
test_case.setup.outputs[0].is_laptop_panel = TRUE;
test_setup = create_monitor_test_setup (&test_case.setup,
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
g_assert_nonnull (meta_monitor_manager_get_laptop_panel (monitor_manager));
g_assert_false (clutter_seat_get_touch_mode (seat));
touch_device = meta_test_add_touch_device (backend);
while (!clutter_seat_get_touch_mode (seat))
g_main_context_iteration (NULL, FALSE);
g_assert_true (clutter_seat_get_touch_mode (seat));
g_assert_false (
meta_monitor_manager_get_panel_orientation_managed (monitor_manager));
orientation_mock = meta_sensors_proxy_mock_get ();
g_assert_false (
meta_orientation_manager_has_accelerometer (orientation_manager));
g_assert_false (
meta_monitor_manager_get_panel_orientation_managed (monitor_manager));
meta_sensors_proxy_mock_set_property (orientation_mock, "HasAccelerometer",
g_variant_new_boolean (TRUE));
while (!meta_orientation_manager_has_accelerometer (orientation_manager))
g_main_context_iteration (NULL, FALSE);
g_assert_true (
meta_orientation_manager_has_accelerometer (orientation_manager));
g_assert_true (
meta_monitor_manager_get_panel_orientation_managed (monitor_manager));
test_case.setup.outputs[0].is_laptop_panel = FALSE;
test_setup = create_monitor_test_setup (&test_case.setup,
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
g_assert_null (meta_monitor_manager_get_laptop_panel (monitor_manager));
g_assert_false (
meta_monitor_manager_get_panel_orientation_managed (monitor_manager));
test_case.setup.outputs[0].is_laptop_panel = TRUE;
test_setup = create_monitor_test_setup (&test_case.setup,
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
g_assert_nonnull (meta_monitor_manager_get_laptop_panel (monitor_manager));
g_assert_true (
meta_monitor_manager_get_panel_orientation_managed (monitor_manager));
meta_sensors_proxy_mock_set_property (orientation_mock, "HasAccelerometer",
g_variant_new_boolean (FALSE));
while (meta_orientation_manager_has_accelerometer (orientation_manager))
g_main_context_iteration (NULL, FALSE);
g_assert_false (
meta_monitor_manager_get_panel_orientation_managed (monitor_manager));
meta_sensors_proxy_mock_set_property (orientation_mock, "HasAccelerometer",
g_variant_new_boolean (TRUE));
while (!meta_orientation_manager_has_accelerometer (orientation_manager))
g_main_context_iteration (NULL, FALSE);
g_assert_true (
meta_monitor_manager_get_panel_orientation_managed (monitor_manager));
meta_backend_test_remove_device (META_BACKEND_TEST (backend), touch_device);
g_clear_object (&touch_device);
while (clutter_seat_get_touch_mode (seat))
g_main_context_iteration (NULL, FALSE);
g_assert_false (clutter_seat_get_touch_mode (seat));
g_assert_false (
meta_monitor_manager_get_panel_orientation_managed (monitor_manager));
touch_device = meta_test_add_touch_device (backend);
while (!clutter_seat_get_touch_mode (seat))
g_main_context_iteration (NULL, FALSE);
g_assert_true (clutter_seat_get_touch_mode (seat));
g_assert_true (
meta_monitor_manager_get_panel_orientation_managed (monitor_manager));
}
static void
meta_test_monitor_orientation_initial_rotated (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.000495910644531
}
},
.n_modes = 1,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.is_laptop_panel = TRUE
},
},
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0
},
},
.n_crtcs = 1
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.000495910644531,
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
}
},
.n_monitors = 1,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
}
},
.n_logical_monitors = 1,
.primary_logical_monitor = 0,
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0,
}
},
.n_crtcs = 1,
.n_tiled_monitors = 0,
.screen_width = 1024,
.screen_height = 768
}
};
MetaMonitorTestSetup *test_setup;
MetaBackend *backend = meta_get_backend ();
MetaOrientationManager *orientation_manager =
meta_backend_get_orientation_manager (backend);
g_autoptr (MetaSensorsProxyAutoResetMock) orientation_mock = NULL;
g_autoptr (ClutterAutoRemoveInputDevice) touch_device = NULL;
MetaOrientation orientation;
tests: Change how we wait for an orientation change Previously, we were waiting up to 300ms for the signal, then proceeding anyway. However, 300ms is not necessarily long enough to wait on an autobuilder that might be heavily loaded, particularly if it's a non-x86 with different performance characteristics. Conversely, if mutter responds to the D-Bus signal from the mock sensor before we have connected to the signal, then we cannot expect to receive the signal - it was already emitted, but we missed it. In this case, we need to avoid waiting. One remaining use of wait_for_orientation_changes() that would previously always have timed out was in meta_test_orientation_manager_has_accelerometer(), which does not actually expect to see an orientation-changed signal. Make this wait for the accelerometer to be detected instead. Resolves: https://gitlab.gnome.org/GNOME/mutter/-/issues/1967 Bug-Debian: https://bugs.debian.org/995929 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-10 07:31:47 -04:00
unsigned int times_signalled = 0;
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("%s", G_STRFUNC);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
orientation_mock = meta_sensors_proxy_mock_get ();
touch_device = meta_test_add_touch_device (backend);
orientation = META_ORIENTATION_LEFT_UP;
meta_sensors_proxy_mock_set_orientation (orientation_mock, orientation);
tests: Move orientation helper to monitor test utils It was used by both the orientation tests, and the monitor configuration tests. Lets move the helper to common ground. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2021-09-30 08:47:11 -04:00
meta_wait_for_orientation (orientation_manager, orientation,
&times_signalled);
tests: Change how we wait for an orientation change Previously, we were waiting up to 300ms for the signal, then proceeding anyway. However, 300ms is not necessarily long enough to wait on an autobuilder that might be heavily loaded, particularly if it's a non-x86 with different performance characteristics. Conversely, if mutter responds to the D-Bus signal from the mock sensor before we have connected to the signal, then we cannot expect to receive the signal - it was already emitted, but we missed it. In this case, we need to avoid waiting. One remaining use of wait_for_orientation_changes() that would previously always have timed out was in meta_test_orientation_manager_has_accelerometer(), which does not actually expect to see an orientation-changed signal. Make this wait for the accelerometer to be detected instead. Resolves: https://gitlab.gnome.org/GNOME/mutter/-/issues/1967 Bug-Debian: https://bugs.debian.org/995929 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-10 07:31:47 -04:00
g_assert_cmpuint (times_signalled, <=, 1);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
META_TEST_LOG_CALL ("Checking configuration per orientation",
check_monitor_configuration_per_orientation (
monitor-unit-tests: Take panel orientation transform in account When checking panel orientation on logical monitors we should take panel orientation transform to check it's properly applied, so ensure that we're checking the right one. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 04:09:12 -05:00
&test_case, 0, orientation, 1024, 768));
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
}
static void
meta_test_monitor_orientation_initial_rotated_no_touch_mode (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.000495910644531
}
},
.n_modes = 1,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.is_laptop_panel = TRUE
},
},
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0
},
},
.n_crtcs = 1
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.000495910644531,
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
}
},
.n_monitors = 1,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
}
},
.n_logical_monitors = 1,
.primary_logical_monitor = 0,
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0,
}
},
.n_crtcs = 1,
.n_tiled_monitors = 0,
.screen_width = 1024,
.screen_height = 768
}
};
MetaMonitorTestSetup *test_setup;
MetaBackend *backend = meta_get_backend ();
MetaOrientationManager *orientation_manager =
meta_backend_get_orientation_manager (backend);
g_autoptr (MetaSensorsProxyAutoResetMock) orientation_mock = NULL;
MetaOrientation orientation;
tests: Change how we wait for an orientation change Previously, we were waiting up to 300ms for the signal, then proceeding anyway. However, 300ms is not necessarily long enough to wait on an autobuilder that might be heavily loaded, particularly if it's a non-x86 with different performance characteristics. Conversely, if mutter responds to the D-Bus signal from the mock sensor before we have connected to the signal, then we cannot expect to receive the signal - it was already emitted, but we missed it. In this case, we need to avoid waiting. One remaining use of wait_for_orientation_changes() that would previously always have timed out was in meta_test_orientation_manager_has_accelerometer(), which does not actually expect to see an orientation-changed signal. Make this wait for the accelerometer to be detected instead. Resolves: https://gitlab.gnome.org/GNOME/mutter/-/issues/1967 Bug-Debian: https://bugs.debian.org/995929 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-10 07:31:47 -04:00
unsigned int times_signalled = 0;
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("%s", G_STRFUNC);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
orientation_mock = meta_sensors_proxy_mock_get ();
orientation = META_ORIENTATION_LEFT_UP;
meta_sensors_proxy_mock_set_orientation (orientation_mock, orientation);
tests: Move orientation helper to monitor test utils It was used by both the orientation tests, and the monitor configuration tests. Lets move the helper to common ground. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2021-09-30 08:47:11 -04:00
meta_wait_for_orientation (orientation_manager, orientation,
&times_signalled);
tests: Change how we wait for an orientation change Previously, we were waiting up to 300ms for the signal, then proceeding anyway. However, 300ms is not necessarily long enough to wait on an autobuilder that might be heavily loaded, particularly if it's a non-x86 with different performance characteristics. Conversely, if mutter responds to the D-Bus signal from the mock sensor before we have connected to the signal, then we cannot expect to receive the signal - it was already emitted, but we missed it. In this case, we need to avoid waiting. One remaining use of wait_for_orientation_changes() that would previously always have timed out was in meta_test_orientation_manager_has_accelerometer(), which does not actually expect to see an orientation-changed signal. Make this wait for the accelerometer to be detected instead. Resolves: https://gitlab.gnome.org/GNOME/mutter/-/issues/1967 Bug-Debian: https://bugs.debian.org/995929 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-10 07:31:47 -04:00
g_assert_cmpuint (times_signalled, <=, 1);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
META_TEST_LOG_CALL ("Checking configuration per orientation",
check_monitor_configuration_per_orientation (
monitor-unit-tests: Take panel orientation transform in account When checking panel orientation on logical monitors we should take panel orientation transform to check it's properly applied, so ensure that we're checking the right one. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 04:09:12 -05:00
&test_case, 0, META_ORIENTATION_NORMAL, 1024, 768));
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
}
static void
meta_test_monitor_orientation_initial_stored_rotated (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1920,
.height = 1080,
.refresh_rate = 60.000495910644531
}
},
.n_modes = 1,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.is_laptop_panel = TRUE
},
},
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0
},
},
.n_crtcs = 1
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1920,
.height = 1080,
.refresh_rate = 60.000495910644531,
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
}
},
.n_monitors = 1,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 960, .height = 540 },
.scale = 2
}
},
.n_logical_monitors = 1,
.primary_logical_monitor = 0,
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0,
}
},
.n_crtcs = 1,
.n_tiled_monitors = 0,
.screen_width = 960,
.screen_height = 540
}
};
MetaMonitorTestSetup *test_setup;
MetaBackend *backend = meta_get_backend ();
MetaMonitorManager *monitor_manager =
meta_backend_get_monitor_manager (backend);
MetaOrientationManager *orientation_manager =
meta_backend_get_orientation_manager (backend);
g_autoptr (MetaSensorsProxyAutoResetMock) orientation_mock = NULL;
g_autoptr (ClutterAutoRemoveInputDevice) touch_device = NULL;
MetaOrientation orientation;
tests: Change how we wait for an orientation change Previously, we were waiting up to 300ms for the signal, then proceeding anyway. However, 300ms is not necessarily long enough to wait on an autobuilder that might be heavily loaded, particularly if it's a non-x86 with different performance characteristics. Conversely, if mutter responds to the D-Bus signal from the mock sensor before we have connected to the signal, then we cannot expect to receive the signal - it was already emitted, but we missed it. In this case, we need to avoid waiting. One remaining use of wait_for_orientation_changes() that would previously always have timed out was in meta_test_orientation_manager_has_accelerometer(), which does not actually expect to see an orientation-changed signal. Make this wait for the accelerometer to be detected instead. Resolves: https://gitlab.gnome.org/GNOME/mutter/-/issues/1967 Bug-Debian: https://bugs.debian.org/995929 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-10 07:31:47 -04:00
unsigned int times_signalled = 0;
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
if (!meta_is_stage_views_enabled ())
{
g_test_skip ("Not using stage views");
return;
}
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("%s", G_STRFUNC);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
orientation_mock = meta_sensors_proxy_mock_get ();
touch_device = meta_test_add_touch_device (backend);
orientation = META_ORIENTATION_RIGHT_UP;
meta_sensors_proxy_mock_set_orientation (orientation_mock, orientation);
tests: Move orientation helper to monitor test utils It was used by both the orientation tests, and the monitor configuration tests. Lets move the helper to common ground. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2021-09-30 08:47:11 -04:00
meta_wait_for_orientation (orientation_manager, orientation,
&times_signalled);
tests: Change how we wait for an orientation change Previously, we were waiting up to 300ms for the signal, then proceeding anyway. However, 300ms is not necessarily long enough to wait on an autobuilder that might be heavily loaded, particularly if it's a non-x86 with different performance characteristics. Conversely, if mutter responds to the D-Bus signal from the mock sensor before we have connected to the signal, then we cannot expect to receive the signal - it was already emitted, but we missed it. In this case, we need to avoid waiting. One remaining use of wait_for_orientation_changes() that would previously always have timed out was in meta_test_orientation_manager_has_accelerometer(), which does not actually expect to see an orientation-changed signal. Make this wait for the accelerometer to be detected instead. Resolves: https://gitlab.gnome.org/GNOME/mutter/-/issues/1967 Bug-Debian: https://bugs.debian.org/995929 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-10 07:31:47 -04:00
g_assert_cmpuint (times_signalled, <=, 1);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
MONITOR_TEST_FLAG_NONE);
set_custom_monitor_config ("lid-scale.xml");
emulate_hotplug (test_setup);
META_TEST_LOG_CALL ("Checking configuration per orientation",
check_monitor_configuration_per_orientation (
monitor-unit-tests: Take panel orientation transform in account When checking panel orientation on logical monitors we should take panel orientation transform to check it's properly applied, so ensure that we're checking the right one. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 04:09:12 -05:00
&test_case, 0, orientation, 960, 540));
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("Closing lid");
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
meta_backend_test_set_is_lid_closed (META_BACKEND_TEST (backend), TRUE);
meta_monitor_manager_lid_is_closed_changed (monitor_manager);
META_TEST_LOG_CALL ("Checking configuration per orientation",
check_monitor_configuration_per_orientation (
monitor-unit-tests: Take panel orientation transform in account When checking panel orientation on logical monitors we should take panel orientation transform to check it's properly applied, so ensure that we're checking the right one. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 04:09:12 -05:00
&test_case, 0, orientation, 960, 540));
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("Rotating to left-up");
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
orientation = META_ORIENTATION_LEFT_UP;
meta_sensors_proxy_mock_set_orientation (orientation_mock, orientation);
tests: Move orientation helper to monitor test utils It was used by both the orientation tests, and the monitor configuration tests. Lets move the helper to common ground. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2021-09-30 08:47:11 -04:00
meta_wait_for_orientation (orientation_manager, orientation,
&times_signalled);
tests: Change how we wait for an orientation change Previously, we were waiting up to 300ms for the signal, then proceeding anyway. However, 300ms is not necessarily long enough to wait on an autobuilder that might be heavily loaded, particularly if it's a non-x86 with different performance characteristics. Conversely, if mutter responds to the D-Bus signal from the mock sensor before we have connected to the signal, then we cannot expect to receive the signal - it was already emitted, but we missed it. In this case, we need to avoid waiting. One remaining use of wait_for_orientation_changes() that would previously always have timed out was in meta_test_orientation_manager_has_accelerometer(), which does not actually expect to see an orientation-changed signal. Make this wait for the accelerometer to be detected instead. Resolves: https://gitlab.gnome.org/GNOME/mutter/-/issues/1967 Bug-Debian: https://bugs.debian.org/995929 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-10 07:31:47 -04:00
g_assert_cmpuint (times_signalled, <=, 1);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
meta_backend_test_set_is_lid_closed (META_BACKEND_TEST (backend), FALSE);
meta_monitor_manager_lid_is_closed_changed (monitor_manager);
META_TEST_LOG_CALL ("Checking configuration per orientation",
check_monitor_configuration_per_orientation (
monitor-unit-tests: Take panel orientation transform in account When checking panel orientation on logical monitors we should take panel orientation transform to check it's properly applied, so ensure that we're checking the right one. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 04:09:12 -05:00
&test_case, 0, orientation, 960, 540));
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
/* When no touch device is available, the orientation change is ignored */
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("Removing touch device");
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
meta_backend_test_remove_device (META_BACKEND_TEST (backend), touch_device);
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("Rotating to right-up");
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
orientation = META_ORIENTATION_RIGHT_UP;
meta_sensors_proxy_mock_set_orientation (orientation_mock, orientation);
tests: Move orientation helper to monitor test utils It was used by both the orientation tests, and the monitor configuration tests. Lets move the helper to common ground. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2021-09-30 08:47:11 -04:00
meta_wait_for_orientation (orientation_manager, orientation,
&times_signalled);
tests: Change how we wait for an orientation change Previously, we were waiting up to 300ms for the signal, then proceeding anyway. However, 300ms is not necessarily long enough to wait on an autobuilder that might be heavily loaded, particularly if it's a non-x86 with different performance characteristics. Conversely, if mutter responds to the D-Bus signal from the mock sensor before we have connected to the signal, then we cannot expect to receive the signal - it was already emitted, but we missed it. In this case, we need to avoid waiting. One remaining use of wait_for_orientation_changes() that would previously always have timed out was in meta_test_orientation_manager_has_accelerometer(), which does not actually expect to see an orientation-changed signal. Make this wait for the accelerometer to be detected instead. Resolves: https://gitlab.gnome.org/GNOME/mutter/-/issues/1967 Bug-Debian: https://bugs.debian.org/995929 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-10 07:31:47 -04:00
g_assert_cmpuint (times_signalled, <=, 1);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
META_TEST_LOG_CALL ("Checking configuration per orientation",
check_monitor_configuration_per_orientation (
monitor-unit-tests: Take panel orientation transform in account When checking panel orientation on logical monitors we should take panel orientation transform to check it's properly applied, so ensure that we're checking the right one. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 04:09:12 -05:00
&test_case, 0, META_ORIENTATION_LEFT_UP,
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
960, 540));
}
static void
meta_test_monitor_orientation_initial_stored_rotated_no_touch (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1920,
.height = 1080,
.refresh_rate = 60.000495910644531
}
},
.n_modes = 1,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.is_laptop_panel = TRUE
},
},
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0
},
},
.n_crtcs = 1
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1920,
.height = 1080,
.refresh_rate = 60.000495910644531,
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
}
},
.n_monitors = 1,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 960, .height = 540 },
.scale = 2
}
},
.n_logical_monitors = 1,
.primary_logical_monitor = 0,
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0,
}
},
.n_crtcs = 1,
.n_tiled_monitors = 0,
.screen_width = 960,
.screen_height = 540
}
};
MetaMonitorTestSetup *test_setup;
MetaBackend *backend = meta_get_backend ();
MetaMonitorManager *monitor_manager =
meta_backend_get_monitor_manager (backend);
MetaOrientationManager *orientation_manager =
meta_backend_get_orientation_manager (backend);
g_autoptr (MetaSensorsProxyAutoResetMock) orientation_mock = NULL;
MetaOrientation orientation;
tests: Change how we wait for an orientation change Previously, we were waiting up to 300ms for the signal, then proceeding anyway. However, 300ms is not necessarily long enough to wait on an autobuilder that might be heavily loaded, particularly if it's a non-x86 with different performance characteristics. Conversely, if mutter responds to the D-Bus signal from the mock sensor before we have connected to the signal, then we cannot expect to receive the signal - it was already emitted, but we missed it. In this case, we need to avoid waiting. One remaining use of wait_for_orientation_changes() that would previously always have timed out was in meta_test_orientation_manager_has_accelerometer(), which does not actually expect to see an orientation-changed signal. Make this wait for the accelerometer to be detected instead. Resolves: https://gitlab.gnome.org/GNOME/mutter/-/issues/1967 Bug-Debian: https://bugs.debian.org/995929 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-10 07:31:47 -04:00
unsigned int times_signalled = 0;
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
if (!meta_is_stage_views_enabled ())
{
g_test_skip ("Not using stage views");
return;
}
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("%s", G_STRFUNC);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
orientation_mock = meta_sensors_proxy_mock_get ();
orientation = META_ORIENTATION_RIGHT_UP;
meta_sensors_proxy_mock_set_orientation (orientation_mock, orientation);
tests: Move orientation helper to monitor test utils It was used by both the orientation tests, and the monitor configuration tests. Lets move the helper to common ground. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2021-09-30 08:47:11 -04:00
meta_wait_for_orientation (orientation_manager, orientation,
&times_signalled);
tests: Change how we wait for an orientation change Previously, we were waiting up to 300ms for the signal, then proceeding anyway. However, 300ms is not necessarily long enough to wait on an autobuilder that might be heavily loaded, particularly if it's a non-x86 with different performance characteristics. Conversely, if mutter responds to the D-Bus signal from the mock sensor before we have connected to the signal, then we cannot expect to receive the signal - it was already emitted, but we missed it. In this case, we need to avoid waiting. One remaining use of wait_for_orientation_changes() that would previously always have timed out was in meta_test_orientation_manager_has_accelerometer(), which does not actually expect to see an orientation-changed signal. Make this wait for the accelerometer to be detected instead. Resolves: https://gitlab.gnome.org/GNOME/mutter/-/issues/1967 Bug-Debian: https://bugs.debian.org/995929 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-10 07:31:47 -04:00
g_assert_cmpuint (times_signalled, <=, 1);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
MONITOR_TEST_FLAG_NONE);
set_custom_monitor_config ("lid-scale.xml");
emulate_hotplug (test_setup);
META_TEST_LOG_CALL ("Checking configuration per orientation",
check_monitor_configuration_per_orientation (
monitor-unit-tests: Take panel orientation transform in account When checking panel orientation on logical monitors we should take panel orientation transform to check it's properly applied, so ensure that we're checking the right one. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 04:09:12 -05:00
&test_case, 0, META_ORIENTATION_NORMAL,
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
960, 540));
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("Closing lid");
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
meta_backend_test_set_is_lid_closed (META_BACKEND_TEST (backend), TRUE);
meta_monitor_manager_lid_is_closed_changed (monitor_manager);
META_TEST_LOG_CALL ("Checking configuration per orientation",
check_monitor_configuration_per_orientation (
monitor-unit-tests: Take panel orientation transform in account When checking panel orientation on logical monitors we should take panel orientation transform to check it's properly applied, so ensure that we're checking the right one. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 04:09:12 -05:00
&test_case, 0, META_ORIENTATION_NORMAL,
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
960, 540));
}
static void
meta_test_monitor_orientation_changes (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.000495910644531
}
},
.n_modes = 1,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.is_laptop_panel = TRUE
},
},
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0
},
},
.n_crtcs = 1
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.000495910644531,
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
}
},
.n_monitors = 1,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
}
},
.n_logical_monitors = 1,
.primary_logical_monitor = 0,
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0,
}
},
.n_crtcs = 1,
.n_tiled_monitors = 0,
.screen_width = 1024,
.screen_height = 768
}
};
MetaMonitorTestSetup *test_setup;
MetaBackend *backend = meta_get_backend ();
MetaMonitorManager *monitor_manager =
meta_backend_get_monitor_manager (backend);
MetaMonitorConfigManager *config_manager = monitor_manager->config_manager;
MetaOrientationManager *orientation_manager =
meta_backend_get_orientation_manager (backend);
g_autoptr (ClutterAutoRemoveInputDevice) touch_device = NULL;
g_autoptr (MetaSensorsProxyAutoResetMock) orientation_mock = NULL;
g_autoptr (MetaMonitorsConfig) initial_config = NULL;
g_autoptr (MetaMonitorsConfig) previous_config = NULL;
monitor-unit-tests: Check orientation changes with transformed panels Ensure that orientation changes still work as expected when using a panel that has some native transformation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 06:14:44 -05:00
gboolean got_monitors_changed = FALSE;
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
MetaOrientation i;
tests: Change how we wait for an orientation change Previously, we were waiting up to 300ms for the signal, then proceeding anyway. However, 300ms is not necessarily long enough to wait on an autobuilder that might be heavily loaded, particularly if it's a non-x86 with different performance characteristics. Conversely, if mutter responds to the D-Bus signal from the mock sensor before we have connected to the signal, then we cannot expect to receive the signal - it was already emitted, but we missed it. In this case, we need to avoid waiting. One remaining use of wait_for_orientation_changes() that would previously always have timed out was in meta_test_orientation_manager_has_accelerometer(), which does not actually expect to see an orientation-changed signal. Make this wait for the accelerometer to be detected instead. Resolves: https://gitlab.gnome.org/GNOME/mutter/-/issues/1967 Bug-Debian: https://bugs.debian.org/995929 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-10 07:31:47 -04:00
unsigned int times_signalled = 0;
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("%s", G_STRFUNC);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
orientation_mock = meta_sensors_proxy_mock_get ();
touch_device = meta_test_add_touch_device (backend);
test_setup = create_monitor_test_setup (&test_case.setup,
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
g_set_object (&previous_config,
meta_monitor_config_manager_get_previous (config_manager));
g_set_object (&initial_config,
meta_monitor_config_manager_get_current (config_manager));
monitor-unit-tests: Check orientation changes with transformed panels Ensure that orientation changes still work as expected when using a panel that has some native transformation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 06:14:44 -05:00
g_signal_connect_swapped (monitor_manager, "monitors-changed",
G_CALLBACK (on_monitors_changed),
&got_monitors_changed);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
g_assert_cmpuint (
meta_orientation_manager_get_orientation (orientation_manager),
==,
META_ORIENTATION_UNDEFINED);
for (i = META_N_ORIENTATIONS - 1; i > META_ORIENTATION_UNDEFINED; i--)
{
MetaMonitorsConfig *current;
MetaMonitorsConfig *previous;
monitor-unit-tests: Check orientation changes with transformed panels Ensure that orientation changes still work as expected when using a panel that has some native transformation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 06:14:44 -05:00
got_monitors_changed = FALSE;
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
meta_sensors_proxy_mock_set_orientation (orientation_mock, i);
tests: Move orientation helper to monitor test utils It was used by both the orientation tests, and the monitor configuration tests. Lets move the helper to common ground. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2021-09-30 08:47:11 -04:00
meta_wait_for_orientation (orientation_manager, i, &times_signalled);
tests: Change how we wait for an orientation change Previously, we were waiting up to 300ms for the signal, then proceeding anyway. However, 300ms is not necessarily long enough to wait on an autobuilder that might be heavily loaded, particularly if it's a non-x86 with different performance characteristics. Conversely, if mutter responds to the D-Bus signal from the mock sensor before we have connected to the signal, then we cannot expect to receive the signal - it was already emitted, but we missed it. In this case, we need to avoid waiting. One remaining use of wait_for_orientation_changes() that would previously always have timed out was in meta_test_orientation_manager_has_accelerometer(), which does not actually expect to see an orientation-changed signal. Make this wait for the accelerometer to be detected instead. Resolves: https://gitlab.gnome.org/GNOME/mutter/-/issues/1967 Bug-Debian: https://bugs.debian.org/995929 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-10 07:31:47 -04:00
g_assert_cmpuint (times_signalled, <=, 1);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
META_TEST_LOG_CALL ("Checking configuration per orientation",
check_monitor_configuration_per_orientation (
monitor-unit-tests: Take panel orientation transform in account When checking panel orientation on logical monitors we should take panel orientation transform to check it's properly applied, so ensure that we're checking the right one. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 04:09:12 -05:00
&test_case, 0, i, 1024, 768));
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
current = meta_monitor_config_manager_get_current (config_manager);
previous = meta_monitor_config_manager_get_previous (config_manager);
monitor-unit-tests: Check orientation changes with transformed panels Ensure that orientation changes still work as expected when using a panel that has some native transformation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 06:14:44 -05:00
g_assert_true (got_monitors_changed);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
g_assert (previous == previous_config);
g_assert (current != initial_config);
g_assert_true (meta_monitors_config_key_equal (current->key,
initial_config->key));
}
/* Ensure applying the current orientation doesn't change the config */
g_assert_cmpuint (
meta_orientation_manager_get_orientation (orientation_manager),
==,
META_ORIENTATION_NORMAL);
g_set_object (&initial_config,
meta_monitor_config_manager_get_current (config_manager));
monitor-unit-tests: Check orientation changes with transformed panels Ensure that orientation changes still work as expected when using a panel that has some native transformation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 06:14:44 -05:00
got_monitors_changed = FALSE;
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
meta_sensors_proxy_mock_set_orientation (orientation_mock,
META_ORIENTATION_NORMAL);
tests: Move orientation helper to monitor test utils It was used by both the orientation tests, and the monitor configuration tests. Lets move the helper to common ground. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2021-09-30 08:47:11 -04:00
meta_wait_for_orientation (orientation_manager, META_ORIENTATION_NORMAL,
&times_signalled);
tests: Change how we wait for an orientation change Previously, we were waiting up to 300ms for the signal, then proceeding anyway. However, 300ms is not necessarily long enough to wait on an autobuilder that might be heavily loaded, particularly if it's a non-x86 with different performance characteristics. Conversely, if mutter responds to the D-Bus signal from the mock sensor before we have connected to the signal, then we cannot expect to receive the signal - it was already emitted, but we missed it. In this case, we need to avoid waiting. One remaining use of wait_for_orientation_changes() that would previously always have timed out was in meta_test_orientation_manager_has_accelerometer(), which does not actually expect to see an orientation-changed signal. Make this wait for the accelerometer to be detected instead. Resolves: https://gitlab.gnome.org/GNOME/mutter/-/issues/1967 Bug-Debian: https://bugs.debian.org/995929 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-10 07:31:47 -04:00
g_assert_cmpuint (times_signalled, ==, 0);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
META_TEST_LOG_CALL ("Checking configuration per orientation",
check_monitor_configuration_per_orientation (
monitor-unit-tests: Take panel orientation transform in account When checking panel orientation on logical monitors we should take panel orientation transform to check it's properly applied, so ensure that we're checking the right one. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 04:09:12 -05:00
&test_case, 0, META_ORIENTATION_NORMAL,
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
1024, 768));
monitor-unit-tests: Check orientation changes with transformed panels Ensure that orientation changes still work as expected when using a panel that has some native transformation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 06:14:44 -05:00
g_assert_false (got_monitors_changed);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
g_assert (meta_monitor_config_manager_get_current (config_manager) ==
initial_config);
/* When no touch device is available, the orientation changes are ignored */
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("Removing touch device");
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
meta_backend_test_remove_device (META_BACKEND_TEST (backend), touch_device);
for (i = META_N_ORIENTATIONS - 1; i > META_ORIENTATION_UNDEFINED; i--)
{
MetaMonitorsConfig *current;
MetaMonitorsConfig *previous;
monitor-unit-tests: Check orientation changes with transformed panels Ensure that orientation changes still work as expected when using a panel that has some native transformation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 06:14:44 -05:00
got_monitors_changed = FALSE;
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
meta_sensors_proxy_mock_set_orientation (orientation_mock, i);
tests: Move orientation helper to monitor test utils It was used by both the orientation tests, and the monitor configuration tests. Lets move the helper to common ground. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2021-09-30 08:47:11 -04:00
meta_wait_for_orientation (orientation_manager, i, &times_signalled);
tests: Change how we wait for an orientation change Previously, we were waiting up to 300ms for the signal, then proceeding anyway. However, 300ms is not necessarily long enough to wait on an autobuilder that might be heavily loaded, particularly if it's a non-x86 with different performance characteristics. Conversely, if mutter responds to the D-Bus signal from the mock sensor before we have connected to the signal, then we cannot expect to receive the signal - it was already emitted, but we missed it. In this case, we need to avoid waiting. One remaining use of wait_for_orientation_changes() that would previously always have timed out was in meta_test_orientation_manager_has_accelerometer(), which does not actually expect to see an orientation-changed signal. Make this wait for the accelerometer to be detected instead. Resolves: https://gitlab.gnome.org/GNOME/mutter/-/issues/1967 Bug-Debian: https://bugs.debian.org/995929 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-10 07:31:47 -04:00
g_assert_cmpuint (times_signalled, <=, 1);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
META_TEST_LOG_CALL ("Checking configuration per orientation",
check_monitor_configuration_per_orientation (
monitor-unit-tests: Take panel orientation transform in account When checking panel orientation on logical monitors we should take panel orientation transform to check it's properly applied, so ensure that we're checking the right one. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 04:09:12 -05:00
&test_case, 0, META_ORIENTATION_NORMAL,
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
1024, 768));
current = meta_monitor_config_manager_get_current (config_manager);
previous = meta_monitor_config_manager_get_previous (config_manager);
g_assert (previous == previous_config);
g_assert (current == initial_config);
monitor-unit-tests: Check orientation changes with transformed panels Ensure that orientation changes still work as expected when using a panel that has some native transformation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 06:14:44 -05:00
g_assert_false (got_monitors_changed);
}
g_signal_handlers_disconnect_by_data (monitor_manager, &got_monitors_changed);
}
static void
meta_test_monitor_orientation_changes_for_transformed_panel (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.000495910644531
}
},
.n_modes = 1,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.is_laptop_panel = TRUE,
.panel_orientation_transform = META_MONITOR_TRANSFORM_90,
},
},
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0
},
},
.n_crtcs = 1
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 768,
.height = 1024,
.refresh_rate = 60.000495910644531,
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
}
},
.n_monitors = 1,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
}
},
.n_logical_monitors = 1,
.primary_logical_monitor = 0,
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0,
}
},
.n_crtcs = 1,
.n_tiled_monitors = 0,
.screen_width = 1024,
.screen_height = 768
}
};
MetaMonitorTestSetup *test_setup;
MetaBackend *backend = meta_get_backend ();
MetaMonitorManager *monitor_manager =
meta_backend_get_monitor_manager (backend);
MetaMonitorConfigManager *config_manager = monitor_manager->config_manager;
MetaOrientationManager *orientation_manager =
meta_backend_get_orientation_manager (backend);
g_autoptr (ClutterAutoRemoveInputDevice) touch_device = NULL;
g_autoptr (MetaSensorsProxyAutoResetMock) orientation_mock = NULL;
g_autoptr (MetaMonitorsConfig) initial_config = NULL;
g_autoptr (MetaMonitorsConfig) previous_config = NULL;
gboolean got_monitors_changed = FALSE;
MetaOrientation i;
unsigned int times_signalled = 0;
g_test_message ("%s", G_STRFUNC);
orientation_mock = meta_sensors_proxy_mock_get ();
touch_device = meta_test_add_touch_device (backend);
test_setup = create_monitor_test_setup (&test_case.setup,
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
g_set_object (&previous_config,
meta_monitor_config_manager_get_previous (config_manager));
g_set_object (&initial_config,
meta_monitor_config_manager_get_current (config_manager));
g_signal_connect_swapped (monitor_manager, "monitors-changed",
G_CALLBACK (on_monitors_changed),
&got_monitors_changed);
g_assert_cmpuint (
meta_orientation_manager_get_orientation (orientation_manager),
==,
META_ORIENTATION_UNDEFINED);
for (i = META_N_ORIENTATIONS - 1; i > META_ORIENTATION_UNDEFINED; i--)
{
MetaMonitorsConfig *current;
MetaMonitorsConfig *previous;
got_monitors_changed = FALSE;
meta_sensors_proxy_mock_set_orientation (orientation_mock, i);
tests: Move orientation helper to monitor test utils It was used by both the orientation tests, and the monitor configuration tests. Lets move the helper to common ground. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2021-09-30 08:47:11 -04:00
meta_wait_for_orientation (orientation_manager, i, &times_signalled);
monitor-unit-tests: Check orientation changes with transformed panels Ensure that orientation changes still work as expected when using a panel that has some native transformation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 06:14:44 -05:00
g_assert_cmpuint (times_signalled, <=, 1);
META_TEST_LOG_CALL ("Checking configuration per orientation",
check_monitor_configuration_per_orientation (
&test_case, 0, i, 1024, 768));
current = meta_monitor_config_manager_get_current (config_manager);
previous = meta_monitor_config_manager_get_previous (config_manager);
g_assert_true (got_monitors_changed);
g_assert (previous == previous_config);
g_assert (current != initial_config);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
g_assert_true (meta_monitors_config_key_equal (current->key,
initial_config->key));
}
monitor-unit-tests: Check orientation changes with transformed panels Ensure that orientation changes still work as expected when using a panel that has some native transformation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 06:14:44 -05:00
/* Ensure applying the current orientation doesn't change the config */
g_assert_cmpuint (
meta_orientation_manager_get_orientation (orientation_manager),
==,
META_ORIENTATION_NORMAL);
g_set_object (&initial_config,
meta_monitor_config_manager_get_current (config_manager));
got_monitors_changed = FALSE;
meta_sensors_proxy_mock_set_orientation (orientation_mock,
META_ORIENTATION_NORMAL);
tests: Move orientation helper to monitor test utils It was used by both the orientation tests, and the monitor configuration tests. Lets move the helper to common ground. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2021-09-30 08:47:11 -04:00
meta_wait_for_orientation (orientation_manager, META_ORIENTATION_NORMAL,
&times_signalled);
monitor-unit-tests: Check orientation changes with transformed panels Ensure that orientation changes still work as expected when using a panel that has some native transformation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 06:14:44 -05:00
g_assert_cmpuint (times_signalled, ==, 0);
META_TEST_LOG_CALL ("Checking configuration per orientation",
check_monitor_configuration_per_orientation (
&test_case, 0, META_ORIENTATION_NORMAL,
1024, 768));
g_assert_false (got_monitors_changed);
g_assert (meta_monitor_config_manager_get_current (config_manager) ==
initial_config);
/* When no touch device is available, the orientation changes are ignored */
g_test_message ("Removing touch device");
meta_backend_test_remove_device (META_BACKEND_TEST (backend), touch_device);
for (i = META_N_ORIENTATIONS - 1; i > META_ORIENTATION_UNDEFINED; i--)
{
MetaMonitorsConfig *current;
MetaMonitorsConfig *previous;
got_monitors_changed = FALSE;
meta_sensors_proxy_mock_set_orientation (orientation_mock, i);
tests: Move orientation helper to monitor test utils It was used by both the orientation tests, and the monitor configuration tests. Lets move the helper to common ground. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2021-09-30 08:47:11 -04:00
meta_wait_for_orientation (orientation_manager, i, &times_signalled);
monitor-unit-tests: Check orientation changes with transformed panels Ensure that orientation changes still work as expected when using a panel that has some native transformation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 06:14:44 -05:00
g_assert_cmpuint (times_signalled, <=, 1);
META_TEST_LOG_CALL ("Checking configuration per orientation",
check_monitor_configuration_per_orientation (
&test_case, 0, META_ORIENTATION_NORMAL,
1024, 768));
current = meta_monitor_config_manager_get_current (config_manager);
previous = meta_monitor_config_manager_get_previous (config_manager);
g_assert (previous == previous_config);
g_assert (current == initial_config);
g_assert_false (got_monitors_changed);
}
g_assert_cmpuint (
meta_orientation_manager_get_orientation (orientation_manager),
==,
META_ORIENTATION_NORMAL);
meta_test_add_touch_device (backend);
got_monitors_changed = FALSE;
meta_sensors_proxy_mock_set_orientation (orientation_mock,
META_ORIENTATION_RIGHT_UP);
tests: Move orientation helper to monitor test utils It was used by both the orientation tests, and the monitor configuration tests. Lets move the helper to common ground. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2021-09-30 08:47:11 -04:00
meta_wait_for_orientation (orientation_manager,
META_ORIENTATION_RIGHT_UP,
&times_signalled);
monitor-unit-tests: Check orientation changes with transformed panels Ensure that orientation changes still work as expected when using a panel that has some native transformation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 06:14:44 -05:00
g_assert_cmpuint (times_signalled, <=, 1);
META_TEST_LOG_CALL ("Checking configuration per orientation",
check_monitor_configuration_per_orientation (
&test_case, 0, META_ORIENTATION_RIGHT_UP,
1024, 768));
g_assert_true (got_monitors_changed);
g_signal_handlers_disconnect_by_data (monitor_manager, &got_monitors_changed);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
}
static void
meta_test_monitor_orientation_changes_with_hotplugging (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0
}
},
.n_modes = 1,
.outputs = {
{
.crtc = -1,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.is_laptop_panel = TRUE
},
{
.crtc = -1,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 1 },
.n_possible_crtcs = 1,
.width_mm = 220,
.height_mm = 124
}
},
.n_outputs = 1, /* Second is hotplugged later */
.crtcs = {
{
.current_mode = -1
},
{
.current_mode = -1
}
},
.n_crtcs = 2
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0,
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125
},
{
.outputs = { 1 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0,
.crtc_modes = {
{
.output = 1,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 220,
.height_mm = 124
}
},
.n_monitors = 1, /* Second is hotplugged later */
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
},
{
.monitors = { 1 },
.n_monitors = 1,
.layout = { .x = 1024, .y = 0, .width = 1024, .height = 768 },
.scale = 1,
.transform = META_MONITOR_TRANSFORM_NORMAL,
}
},
.n_logical_monitors = 1, /* Second is hotplugged later */
.primary_logical_monitor = 0,
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0,
},
{
.current_mode = -1,
.transform = META_MONITOR_TRANSFORM_NORMAL,
}
},
.n_crtcs = 2,
.n_tiled_monitors = 0,
.screen_width = 1024,
.screen_height = 768
}
};
MetaMonitorTestSetup *test_setup;
MetaBackend *backend = meta_get_backend ();
MetaOrientationManager *orientation_manager =
meta_backend_get_orientation_manager (backend);
g_autoptr (ClutterAutoRemoveInputDevice) touch_device = NULL;
g_autoptr (MetaSensorsProxyAutoResetMock) orientation_mock = NULL;
MetaOrientation i;
tests: Change how we wait for an orientation change Previously, we were waiting up to 300ms for the signal, then proceeding anyway. However, 300ms is not necessarily long enough to wait on an autobuilder that might be heavily loaded, particularly if it's a non-x86 with different performance characteristics. Conversely, if mutter responds to the D-Bus signal from the mock sensor before we have connected to the signal, then we cannot expect to receive the signal - it was already emitted, but we missed it. In this case, we need to avoid waiting. One remaining use of wait_for_orientation_changes() that would previously always have timed out was in meta_test_orientation_manager_has_accelerometer(), which does not actually expect to see an orientation-changed signal. Make this wait for the accelerometer to be detected instead. Resolves: https://gitlab.gnome.org/GNOME/mutter/-/issues/1967 Bug-Debian: https://bugs.debian.org/995929 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-10 07:31:47 -04:00
unsigned int times_signalled = 0;
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("%s", G_STRFUNC);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
orientation_mock = meta_sensors_proxy_mock_get ();
touch_device = meta_test_add_touch_device (backend);
/*
* The first part of this test emulate the following:
* 1) Start with the lid open
* 2) Rotate the device in all directions
* 3) Connect external monitor
* 4) Rotate the device in all directions
* 5) Close lid
*/
test_setup = create_monitor_test_setup (&test_case.setup,
MONITOR_TEST_FLAG_NO_STORED);
meta_backend_test_set_is_lid_closed (META_BACKEND_TEST (backend), FALSE);
emulate_hotplug (test_setup);
check_monitor_configuration (&test_case.expect);
for (i = META_N_ORIENTATIONS - 1; i > META_ORIENTATION_UNDEFINED; i--)
{
meta_sensors_proxy_mock_set_orientation (orientation_mock, i);
tests: Move orientation helper to monitor test utils It was used by both the orientation tests, and the monitor configuration tests. Lets move the helper to common ground. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2021-09-30 08:47:11 -04:00
meta_wait_for_orientation (orientation_manager, i, &times_signalled);
tests: Change how we wait for an orientation change Previously, we were waiting up to 300ms for the signal, then proceeding anyway. However, 300ms is not necessarily long enough to wait on an autobuilder that might be heavily loaded, particularly if it's a non-x86 with different performance characteristics. Conversely, if mutter responds to the D-Bus signal from the mock sensor before we have connected to the signal, then we cannot expect to receive the signal - it was already emitted, but we missed it. In this case, we need to avoid waiting. One remaining use of wait_for_orientation_changes() that would previously always have timed out was in meta_test_orientation_manager_has_accelerometer(), which does not actually expect to see an orientation-changed signal. Make this wait for the accelerometer to be detected instead. Resolves: https://gitlab.gnome.org/GNOME/mutter/-/issues/1967 Bug-Debian: https://bugs.debian.org/995929 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-10 07:31:47 -04:00
g_assert_cmpuint (times_signalled, <=, 1);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
META_TEST_LOG_CALL ("Checking configuration per orientation",
check_monitor_configuration_per_orientation (
monitor-unit-tests: Take panel orientation transform in account When checking panel orientation on logical monitors we should take panel orientation transform to check it's properly applied, so ensure that we're checking the right one. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 04:09:12 -05:00
&test_case, 0, i, 1024, 768));
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
}
meta_sensors_proxy_mock_set_orientation (orientation_mock,
META_ORIENTATION_NORMAL);
tests: Move orientation helper to monitor test utils It was used by both the orientation tests, and the monitor configuration tests. Lets move the helper to common ground. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2021-09-30 08:47:11 -04:00
meta_wait_for_orientation (orientation_manager, META_ORIENTATION_NORMAL,
&times_signalled);
tests: Change how we wait for an orientation change Previously, we were waiting up to 300ms for the signal, then proceeding anyway. However, 300ms is not necessarily long enough to wait on an autobuilder that might be heavily loaded, particularly if it's a non-x86 with different performance characteristics. Conversely, if mutter responds to the D-Bus signal from the mock sensor before we have connected to the signal, then we cannot expect to receive the signal - it was already emitted, but we missed it. In this case, we need to avoid waiting. One remaining use of wait_for_orientation_changes() that would previously always have timed out was in meta_test_orientation_manager_has_accelerometer(), which does not actually expect to see an orientation-changed signal. Make this wait for the accelerometer to be detected instead. Resolves: https://gitlab.gnome.org/GNOME/mutter/-/issues/1967 Bug-Debian: https://bugs.debian.org/995929 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-10 07:31:47 -04:00
g_assert_cmpuint (times_signalled, <=, 1);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
check_monitor_configuration (&test_case.expect);
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("External monitor connected");
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
test_case.setup.n_outputs = 2;
test_case.expect.n_outputs = 2;
test_case.expect.n_monitors = 2;
test_case.expect.n_logical_monitors = 2;
test_case.expect.crtcs[1].current_mode = 0;
test_case.expect.crtcs[1].x = 1024;
test_case.expect.screen_width = 1024 * 2;
test_setup = create_monitor_test_setup (&test_case.setup,
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
check_monitor_configuration (&test_case.expect);
/* Rotate the monitor in all the directions */
for (i = META_N_ORIENTATIONS - 1; i > META_ORIENTATION_UNDEFINED; i--)
{
meta_sensors_proxy_mock_set_orientation (orientation_mock, i);
tests: Move orientation helper to monitor test utils It was used by both the orientation tests, and the monitor configuration tests. Lets move the helper to common ground. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2021-09-30 08:47:11 -04:00
meta_wait_for_orientation (orientation_manager, i, &times_signalled);
tests: Change how we wait for an orientation change Previously, we were waiting up to 300ms for the signal, then proceeding anyway. However, 300ms is not necessarily long enough to wait on an autobuilder that might be heavily loaded, particularly if it's a non-x86 with different performance characteristics. Conversely, if mutter responds to the D-Bus signal from the mock sensor before we have connected to the signal, then we cannot expect to receive the signal - it was already emitted, but we missed it. In this case, we need to avoid waiting. One remaining use of wait_for_orientation_changes() that would previously always have timed out was in meta_test_orientation_manager_has_accelerometer(), which does not actually expect to see an orientation-changed signal. Make this wait for the accelerometer to be detected instead. Resolves: https://gitlab.gnome.org/GNOME/mutter/-/issues/1967 Bug-Debian: https://bugs.debian.org/995929 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-10 07:31:47 -04:00
g_assert_cmpuint (times_signalled, <=, 1);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
META_TEST_LOG_CALL ("Checking configuration per orientation",
check_monitor_configuration_per_orientation (
monitor-unit-tests: Take panel orientation transform in account When checking panel orientation on logical monitors we should take panel orientation transform to check it's properly applied, so ensure that we're checking the right one. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 04:09:12 -05:00
&test_case, 0, i, 1024, 768));
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
}
meta_sensors_proxy_mock_set_orientation (orientation_mock,
META_ORIENTATION_NORMAL);
tests: Move orientation helper to monitor test utils It was used by both the orientation tests, and the monitor configuration tests. Lets move the helper to common ground. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2021-09-30 08:47:11 -04:00
meta_wait_for_orientation (orientation_manager, META_ORIENTATION_NORMAL,
&times_signalled);
tests: Change how we wait for an orientation change Previously, we were waiting up to 300ms for the signal, then proceeding anyway. However, 300ms is not necessarily long enough to wait on an autobuilder that might be heavily loaded, particularly if it's a non-x86 with different performance characteristics. Conversely, if mutter responds to the D-Bus signal from the mock sensor before we have connected to the signal, then we cannot expect to receive the signal - it was already emitted, but we missed it. In this case, we need to avoid waiting. One remaining use of wait_for_orientation_changes() that would previously always have timed out was in meta_test_orientation_manager_has_accelerometer(), which does not actually expect to see an orientation-changed signal. Make this wait for the accelerometer to be detected instead. Resolves: https://gitlab.gnome.org/GNOME/mutter/-/issues/1967 Bug-Debian: https://bugs.debian.org/995929 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-10 07:31:47 -04:00
g_assert_cmpuint (times_signalled, <=, 1);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
check_monitor_configuration (&test_case.expect);
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("Lid closed");
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
test_case.expect.monitors[0].current_mode = -1;
test_case.expect.logical_monitors[0].monitors[0] = 1,
test_case.expect.n_logical_monitors = 1;
test_case.expect.crtcs[0].current_mode = -1;
test_case.expect.crtcs[1].x = 0;
test_case.expect.screen_width = 1024;
test_setup = create_monitor_test_setup (&test_case.setup,
MONITOR_TEST_FLAG_NO_STORED);
meta_backend_test_set_is_lid_closed (META_BACKEND_TEST (backend), TRUE);
emulate_hotplug (test_setup);
/* Rotate the monitor in all the directions */
for (i = META_N_ORIENTATIONS - 1; i > META_ORIENTATION_UNDEFINED; i--)
{
meta_sensors_proxy_mock_set_orientation (orientation_mock, i);
tests: Move orientation helper to monitor test utils It was used by both the orientation tests, and the monitor configuration tests. Lets move the helper to common ground. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2021-09-30 08:47:11 -04:00
meta_wait_for_orientation (orientation_manager, i, &times_signalled);
tests: Change how we wait for an orientation change Previously, we were waiting up to 300ms for the signal, then proceeding anyway. However, 300ms is not necessarily long enough to wait on an autobuilder that might be heavily loaded, particularly if it's a non-x86 with different performance characteristics. Conversely, if mutter responds to the D-Bus signal from the mock sensor before we have connected to the signal, then we cannot expect to receive the signal - it was already emitted, but we missed it. In this case, we need to avoid waiting. One remaining use of wait_for_orientation_changes() that would previously always have timed out was in meta_test_orientation_manager_has_accelerometer(), which does not actually expect to see an orientation-changed signal. Make this wait for the accelerometer to be detected instead. Resolves: https://gitlab.gnome.org/GNOME/mutter/-/issues/1967 Bug-Debian: https://bugs.debian.org/995929 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-10 07:31:47 -04:00
g_assert_cmpuint (times_signalled, <=, 1);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
check_monitor_configuration (&test_case.expect);
}
meta_sensors_proxy_mock_set_orientation (orientation_mock,
META_ORIENTATION_NORMAL);
tests: Move orientation helper to monitor test utils It was used by both the orientation tests, and the monitor configuration tests. Lets move the helper to common ground. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2021-09-30 08:47:11 -04:00
meta_wait_for_orientation (orientation_manager, META_ORIENTATION_NORMAL,
&times_signalled);
tests: Change how we wait for an orientation change Previously, we were waiting up to 300ms for the signal, then proceeding anyway. However, 300ms is not necessarily long enough to wait on an autobuilder that might be heavily loaded, particularly if it's a non-x86 with different performance characteristics. Conversely, if mutter responds to the D-Bus signal from the mock sensor before we have connected to the signal, then we cannot expect to receive the signal - it was already emitted, but we missed it. In this case, we need to avoid waiting. One remaining use of wait_for_orientation_changes() that would previously always have timed out was in meta_test_orientation_manager_has_accelerometer(), which does not actually expect to see an orientation-changed signal. Make this wait for the accelerometer to be detected instead. Resolves: https://gitlab.gnome.org/GNOME/mutter/-/issues/1967 Bug-Debian: https://bugs.debian.org/995929 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-10 07:31:47 -04:00
g_assert_cmpuint (times_signalled, <=, 1);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
/*
* The second part of this test emulate the following at each device rotation:
* 1) Open lid
* 2) Close lid
* 3) Change orientation
* 4) Reopen the lid
* 2) Disconnect external monitor
*/
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("Lid opened");
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
test_case.expect.monitors[0].current_mode = 0;
test_case.expect.logical_monitors[0].monitors[0] = 0,
test_case.expect.logical_monitors[1].monitors[0] = 1,
test_case.expect.n_logical_monitors = 2;
test_case.expect.crtcs[0].current_mode = 0;
test_case.expect.crtcs[1].x = 1024;
test_case.expect.screen_width = 1024 * 2;
test_setup = create_monitor_test_setup (&test_case.setup,
MONITOR_TEST_FLAG_NO_STORED);
meta_backend_test_set_is_lid_closed (META_BACKEND_TEST (backend), FALSE);
emulate_hotplug (test_setup);
check_monitor_configuration (&test_case.expect);
for (i = META_N_ORIENTATIONS - 1; i > META_ORIENTATION_UNDEFINED; i--)
{
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("Closing lid");
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
test_case.expect.monitors[0].current_mode = -1;
test_case.expect.logical_monitors[0].monitors[0] = 1,
test_case.expect.n_logical_monitors = 1;
test_case.expect.crtcs[0].current_mode = -1;
test_case.expect.crtcs[1].x = 0;
test_case.expect.screen_width = 1024;
test_setup = create_monitor_test_setup (&test_case.setup,
MONITOR_TEST_FLAG_NO_STORED);
meta_backend_test_set_is_lid_closed (META_BACKEND_TEST (backend), TRUE);
emulate_hotplug (test_setup);
/* Change orientation */
meta_sensors_proxy_mock_set_orientation (orientation_mock, i);
tests: Move orientation helper to monitor test utils It was used by both the orientation tests, and the monitor configuration tests. Lets move the helper to common ground. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2021-09-30 08:47:11 -04:00
meta_wait_for_orientation (orientation_manager, i, &times_signalled);
tests: Change how we wait for an orientation change Previously, we were waiting up to 300ms for the signal, then proceeding anyway. However, 300ms is not necessarily long enough to wait on an autobuilder that might be heavily loaded, particularly if it's a non-x86 with different performance characteristics. Conversely, if mutter responds to the D-Bus signal from the mock sensor before we have connected to the signal, then we cannot expect to receive the signal - it was already emitted, but we missed it. In this case, we need to avoid waiting. One remaining use of wait_for_orientation_changes() that would previously always have timed out was in meta_test_orientation_manager_has_accelerometer(), which does not actually expect to see an orientation-changed signal. Make this wait for the accelerometer to be detected instead. Resolves: https://gitlab.gnome.org/GNOME/mutter/-/issues/1967 Bug-Debian: https://bugs.debian.org/995929 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-10 07:31:47 -04:00
g_assert_cmpuint (times_signalled, <=, 1);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
check_monitor_configuration (&test_case.expect);
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("Opening lid");
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
test_case.expect.monitors[0].current_mode = 0;
test_case.expect.logical_monitors[0].monitors[0] = 0,
test_case.expect.logical_monitors[1].monitors[0] = 1,
test_case.expect.n_logical_monitors = 2;
test_case.expect.crtcs[0].current_mode = 0;
test_case.expect.crtcs[1].x = 1024;
test_setup = create_monitor_test_setup (&test_case.setup,
MONITOR_TEST_FLAG_NO_STORED);
meta_backend_test_set_is_lid_closed (META_BACKEND_TEST (backend), FALSE);
emulate_hotplug (test_setup);
tests: Change how we wait for an orientation change Previously, we were waiting up to 300ms for the signal, then proceeding anyway. However, 300ms is not necessarily long enough to wait on an autobuilder that might be heavily loaded, particularly if it's a non-x86 with different performance characteristics. Conversely, if mutter responds to the D-Bus signal from the mock sensor before we have connected to the signal, then we cannot expect to receive the signal - it was already emitted, but we missed it. In this case, we need to avoid waiting. One remaining use of wait_for_orientation_changes() that would previously always have timed out was in meta_test_orientation_manager_has_accelerometer(), which does not actually expect to see an orientation-changed signal. Make this wait for the accelerometer to be detected instead. Resolves: https://gitlab.gnome.org/GNOME/mutter/-/issues/1967 Bug-Debian: https://bugs.debian.org/995929 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-10 07:31:47 -04:00
/* We don't actually expect the orientation to change here, so we
* just wait for a moment (so that if the orientation *did* change,
* mutter has had a chance to process it), and then continue. */
tests: Move orientation helper to monitor test utils It was used by both the orientation tests, and the monitor configuration tests. Lets move the helper to common ground. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2021-09-30 08:47:11 -04:00
meta_wait_for_possible_orientation_change (orientation_manager,
&times_signalled);
tests: Change how we wait for an orientation change Previously, we were waiting up to 300ms for the signal, then proceeding anyway. However, 300ms is not necessarily long enough to wait on an autobuilder that might be heavily loaded, particularly if it's a non-x86 with different performance characteristics. Conversely, if mutter responds to the D-Bus signal from the mock sensor before we have connected to the signal, then we cannot expect to receive the signal - it was already emitted, but we missed it. In this case, we need to avoid waiting. One remaining use of wait_for_orientation_changes() that would previously always have timed out was in meta_test_orientation_manager_has_accelerometer(), which does not actually expect to see an orientation-changed signal. Make this wait for the accelerometer to be detected instead. Resolves: https://gitlab.gnome.org/GNOME/mutter/-/issues/1967 Bug-Debian: https://bugs.debian.org/995929 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-10 07:31:47 -04:00
g_assert_cmpuint (times_signalled, ==, 0);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
META_TEST_LOG_CALL ("Checking configuration per orientation",
check_monitor_configuration_per_orientation (
monitor-unit-tests: Take panel orientation transform in account When checking panel orientation on logical monitors we should take panel orientation transform to check it's properly applied, so ensure that we're checking the right one. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 04:09:12 -05:00
&test_case, 0, i, 1024, 768));
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("External monitor disconnected");
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
test_case.setup.n_outputs = 1;
test_case.expect.n_outputs = 1;
test_case.expect.n_monitors = 1;
test_case.expect.n_logical_monitors = 1;
test_case.expect.crtcs[1].current_mode = -1;
test_setup = create_monitor_test_setup (&test_case.setup,
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
META_TEST_LOG_CALL ("Checking configuration per orientation",
check_monitor_configuration_per_orientation (
monitor-unit-tests: Take panel orientation transform in account When checking panel orientation on logical monitors we should take panel orientation transform to check it's properly applied, so ensure that we're checking the right one. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 04:09:12 -05:00
&test_case, 0, i, 1024, 768));
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
tests: Make it easier to keep track of where we are The monitor orientation tests do a lot of things in sequence. Replace some of the comments with g_test_message() so that the log from a failed test gives us a better idea of how far we got. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-11 04:39:37 -04:00
g_test_message ("External monitor connected");
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
test_case.setup.n_outputs = 2;
test_case.expect.n_outputs = 2;
test_case.expect.n_monitors = 2;
test_case.expect.n_logical_monitors = 2;
test_case.expect.crtcs[1].current_mode = 0;
test_case.expect.crtcs[1].x = 1024;
test_setup = create_monitor_test_setup (&test_case.setup,
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
META_TEST_LOG_CALL ("Checking configuration per orientation",
check_monitor_configuration_per_orientation (
monitor-unit-tests: Take panel orientation transform in account When checking panel orientation on logical monitors we should take panel orientation transform to check it's properly applied, so ensure that we're checking the right one. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 04:09:12 -05:00
&test_case, 0, i, 1024, 768));
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
}
meta_sensors_proxy_mock_set_orientation (orientation_mock,
META_ORIENTATION_NORMAL);
tests: Move orientation helper to monitor test utils It was used by both the orientation tests, and the monitor configuration tests. Lets move the helper to common ground. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2021-09-30 08:47:11 -04:00
meta_wait_for_orientation (orientation_manager, META_ORIENTATION_NORMAL,
&times_signalled);
tests: Change how we wait for an orientation change Previously, we were waiting up to 300ms for the signal, then proceeding anyway. However, 300ms is not necessarily long enough to wait on an autobuilder that might be heavily loaded, particularly if it's a non-x86 with different performance characteristics. Conversely, if mutter responds to the D-Bus signal from the mock sensor before we have connected to the signal, then we cannot expect to receive the signal - it was already emitted, but we missed it. In this case, we need to avoid waiting. One remaining use of wait_for_orientation_changes() that would previously always have timed out was in meta_test_orientation_manager_has_accelerometer(), which does not actually expect to see an orientation-changed signal. Make this wait for the accelerometer to be detected instead. Resolves: https://gitlab.gnome.org/GNOME/mutter/-/issues/1967 Bug-Debian: https://bugs.debian.org/995929 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2049>
2021-10-10 07:31:47 -04:00
g_assert_cmpuint (times_signalled, <=, 1);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
}
monitor-unit-tests: Check that a stored config is preferred Check that the stored config (where the logical monitors are placed vertically) is preferred to the otherwise generated linear config. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-13 01:42:03 -05:00
static void
meta_test_monitor_custom_vertical_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.000495910644531
},
{
.width = 800,
.height = 600,
.refresh_rate = 60.000495910644531
}
},
.n_modes = 2,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125
},
{
.crtc = 1,
.modes = { 1 },
.n_modes = 1,
.preferred_mode = 1,
.possible_crtcs = { 1 },
.n_possible_crtcs = 1,
.width_mm = 220,
.height_mm = 124
}
},
.n_outputs = 2,
.crtcs = {
{
.current_mode = 0
},
{
.current_mode = 0
}
},
.n_crtcs = 2
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.000495910644531,
monitor-unit-tests: Check that a stored config is preferred Check that the stored config (where the logical monitors are placed vertically) is preferred to the otherwise generated linear config. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-13 01:42:03 -05:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125
},
{
.outputs = { 1 },
.n_outputs = 1,
.modes = {
{
.width = 800,
.height = 600,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.000495910644531,
monitor-unit-tests: Check that a stored config is preferred Check that the stored config (where the logical monitors are placed vertically) is preferred to the otherwise generated linear config. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-13 01:42:03 -05:00
.crtc_modes = {
{
.output = 1,
.crtc_mode = 1
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 220,
.height_mm = 124
}
},
.n_monitors = 2,
.logical_monitors = {
{
monitor-unit-tests: Check monitor <-> logical monitor relationships Make sure that each logical monitor owns the expected actual monitors. This currently needs special care when dealing with laptop lid the configuration, as the MetaMonitorConfigManager path still deosn't handle restoring the previous configuration, meaning the logical monitor with the external monitor will continue being primary. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 01:09:55 -05:00
.monitors = { 0 },
.n_monitors = 1,
monitor-unit-tests: Check that a stored config is preferred Check that the stored config (where the logical monitors are placed vertically) is preferred to the otherwise generated linear config. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-13 01:42:03 -05:00
.layout = { .x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
},
{
monitor-unit-tests: Check monitor <-> logical monitor relationships Make sure that each logical monitor owns the expected actual monitors. This currently needs special care when dealing with laptop lid the configuration, as the MetaMonitorConfigManager path still deosn't handle restoring the previous configuration, meaning the logical monitor with the external monitor will continue being primary. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 01:09:55 -05:00
.monitors = { 1 },
.n_monitors = 1,
monitor-unit-tests: Check that a stored config is preferred Check that the stored config (where the logical monitors are placed vertically) is preferred to the otherwise generated linear config. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-13 01:42:03 -05:00
.layout = { .x = 0, .y = 768, .width = 800, .height = 600 },
.scale = 1
}
},
.n_logical_monitors = 2,
monitor-unit-tests: Check handling of the primary presentation flags The main output of the main (first) monitor of a primary logical monitor should have the MetaOutput::is_primary field set; all other outputs should have it not set. All outputs associated with a logical monitor with presentation set should have MetaOutput::is_presentation set. No other outputs should have it set. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 00:09:21 -05:00
.primary_logical_monitor = 0,
monitor-unit-tests: Check that a stored config is preferred Check that the stored config (where the logical monitors are placed vertically) is preferred to the otherwise generated linear config. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-13 01:42:03 -05:00
.n_outputs = 2,
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
.crtcs = {
{
.current_mode = 0,
},
{
.current_mode = 1,
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
.y = 768,
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
}
},
monitor-unit-tests: Check that a stored config is preferred Check that the stored config (where the logical monitors are placed vertically) is preferred to the otherwise generated linear config. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-13 01:42:03 -05:00
.n_crtcs = 2,
.n_tiled_monitors = 0,
.screen_width = 1024,
.screen_height = 768 + 600
}
};
MetaMonitorTestSetup *test_setup;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Check that a stored config is preferred Check that the stored config (where the logical monitors are placed vertically) is preferred to the otherwise generated linear config. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-13 01:42:03 -05:00
MONITOR_TEST_FLAG_NONE);
set_custom_monitor_config ("vertical.xml");
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Check that a stored config is preferred Check that the stored config (where the logical monitors are placed vertically) is preferred to the otherwise generated linear config. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-13 01:42:03 -05:00
}
tests: Add monitor and monitor store test for custom primary Test that having a custom primary logical monitor is configured as expected. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 00:13:35 -05:00
static void
meta_test_monitor_custom_primary_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.000495910644531
},
{
.width = 800,
.height = 600,
.refresh_rate = 60.000495910644531
}
},
.n_modes = 2,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125
},
{
.crtc = 1,
.modes = { 1 },
.n_modes = 1,
.preferred_mode = 1,
.possible_crtcs = { 1 },
.n_possible_crtcs = 1,
.width_mm = 220,
.height_mm = 124
}
},
.n_outputs = 2,
.crtcs = {
{
.current_mode = 0
},
{
.current_mode = 0
}
},
.n_crtcs = 2
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.000495910644531,
tests: Add monitor and monitor store test for custom primary Test that having a custom primary logical monitor is configured as expected. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 00:13:35 -05:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125
},
{
.outputs = { 1 },
.n_outputs = 1,
.modes = {
{
.width = 800,
.height = 600,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.000495910644531,
tests: Add monitor and monitor store test for custom primary Test that having a custom primary logical monitor is configured as expected. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 00:13:35 -05:00
.crtc_modes = {
{
.output = 1,
.crtc_mode = 1
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 220,
.height_mm = 124
}
},
.n_monitors = 2,
.logical_monitors = {
{
monitor-unit-tests: Check monitor <-> logical monitor relationships Make sure that each logical monitor owns the expected actual monitors. This currently needs special care when dealing with laptop lid the configuration, as the MetaMonitorConfigManager path still deosn't handle restoring the previous configuration, meaning the logical monitor with the external monitor will continue being primary. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 01:09:55 -05:00
.monitors = { 0 },
.n_monitors = 1,
tests: Add monitor and monitor store test for custom primary Test that having a custom primary logical monitor is configured as expected. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 00:13:35 -05:00
.layout = { .x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
},
{
monitor-unit-tests: Check monitor <-> logical monitor relationships Make sure that each logical monitor owns the expected actual monitors. This currently needs special care when dealing with laptop lid the configuration, as the MetaMonitorConfigManager path still deosn't handle restoring the previous configuration, meaning the logical monitor with the external monitor will continue being primary. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 01:09:55 -05:00
.monitors = { 1 },
.n_monitors = 1,
tests: Add monitor and monitor store test for custom primary Test that having a custom primary logical monitor is configured as expected. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 00:13:35 -05:00
.layout = { .x = 1024, .y = 0, .width = 800, .height = 600 },
.scale = 1
}
},
.n_logical_monitors = 2,
.primary_logical_monitor = 1,
.n_outputs = 2,
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
.crtcs = {
{
.current_mode = 0,
},
{
.current_mode = 1,
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
.x = 1024,
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
}
},
tests: Add monitor and monitor store test for custom primary Test that having a custom primary logical monitor is configured as expected. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 00:13:35 -05:00
.n_crtcs = 2,
.n_tiled_monitors = 0,
.screen_width = 1024 + 800,
.screen_height = 768
}
};
MetaMonitorTestSetup *test_setup;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
tests: Add monitor and monitor store test for custom primary Test that having a custom primary logical monitor is configured as expected. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 00:13:35 -05:00
MONITOR_TEST_FLAG_NONE);
set_custom_monitor_config ("primary.xml");
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
tests: Add monitor and monitor store test for custom primary Test that having a custom primary logical monitor is configured as expected. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 00:13:35 -05:00
}
tests: Add monitor store and config test for output underscanning https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 22:34:23 -05:00
static void
meta_test_monitor_custom_underscanning_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.000495910644531
}
},
.n_modes = 1,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125
},
},
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0
},
},
.n_crtcs = 1
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.000495910644531,
tests: Add monitor store and config test for output underscanning https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 22:34:23 -05:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
.is_underscanning = TRUE,
}
},
.n_monitors = 1,
.logical_monitors = {
{
monitor-unit-tests: Check monitor <-> logical monitor relationships Make sure that each logical monitor owns the expected actual monitors. This currently needs special care when dealing with laptop lid the configuration, as the MetaMonitorConfigManager path still deosn't handle restoring the previous configuration, meaning the logical monitor with the external monitor will continue being primary. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 01:09:55 -05:00
.monitors = { 0 },
.n_monitors = 1,
tests: Add monitor store and config test for output underscanning https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 22:34:23 -05:00
.layout = { .x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
}
},
.n_logical_monitors = 1,
.primary_logical_monitor = 0,
.n_outputs = 1,
monitor-unit-tests: Check that each CRTC mode is correct This is partly redundant given that the current monitor mode is checked against the CRTC mode, but this also checks the disabled CRTCs. Later the configured mode position and transform will be checked. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-18 05:01:47 -05:00
.crtcs = {
{
.current_mode = 0,
}
},
tests: Add monitor store and config test for output underscanning https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 22:34:23 -05:00
.n_crtcs = 1,
.n_tiled_monitors = 0,
.screen_width = 1024,
.screen_height = 768
}
};
MetaMonitorTestSetup *test_setup;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
tests: Add monitor store and config test for output underscanning https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 22:34:23 -05:00
MONITOR_TEST_FLAG_NONE);
set_custom_monitor_config ("underscanning.xml");
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
tests: Add monitor store and config test for output underscanning https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-16 22:34:23 -05:00
}
tests: Test configured custom logical monitor scale Check that a configured logical monitor scale overrides any calculated one. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 09:46:33 -05:00
static void
meta_test_monitor_custom_scale_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1920,
.height = 1080,
.refresh_rate = 60.000495910644531
}
},
.n_modes = 1,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125
},
},
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0
},
},
.n_crtcs = 1
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1920,
.height = 1080,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.000495910644531,
tests: Test configured custom logical monitor scale Check that a configured logical monitor scale overrides any calculated one. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 09:46:33 -05:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
}
},
.n_monitors = 1,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
Add support for scaled logical monitor framebuffers This commit adds support for rendering onto enlarged per logical monitor framebuffers, using the scaled clutter stage views, for HiDPI enabled logical monitors. This works by scaling the mode of the monitors in a logical monitors by the scale, no longer relying on scaling the window actors and window geometry for making windows have the correct size on HiDPI monitors. It is disabled by default, as in automatically created configurations will still use the old mode. This is partly because Xwayland clients will not yet work good enough to make it feasible. To enable, add the 'scale-monitor-framebuffer' keyword to the org.gnome.mutter.experimental-features gsettings array. It is still possible to specify the mode via the new D-Bus API, which has been adapted. The adaptations to the D-Bus API means the caller need to be aware of how to position logical monitors on the stage grid. This depends on the 'layout-mode' property that is used (see the DisplayConfig D-Bus documentation). https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-02-24 05:10:52 -05:00
.layout = { .x = 0, .y = 0, .width = 960, .height = 540 },
tests: Test configured custom logical monitor scale Check that a configured logical monitor scale overrides any calculated one. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 09:46:33 -05:00
.scale = 2
}
},
.n_logical_monitors = 1,
.primary_logical_monitor = 0,
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0,
}
},
.n_crtcs = 1,
.n_tiled_monitors = 0,
Add support for scaled logical monitor framebuffers This commit adds support for rendering onto enlarged per logical monitor framebuffers, using the scaled clutter stage views, for HiDPI enabled logical monitors. This works by scaling the mode of the monitors in a logical monitors by the scale, no longer relying on scaling the window actors and window geometry for making windows have the correct size on HiDPI monitors. It is disabled by default, as in automatically created configurations will still use the old mode. This is partly because Xwayland clients will not yet work good enough to make it feasible. To enable, add the 'scale-monitor-framebuffer' keyword to the org.gnome.mutter.experimental-features gsettings array. It is still possible to specify the mode via the new D-Bus API, which has been adapted. The adaptations to the D-Bus API means the caller need to be aware of how to position logical monitors on the stage grid. This depends on the 'layout-mode' property that is used (see the DisplayConfig D-Bus documentation). https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-02-24 05:10:52 -05:00
.screen_width = 960,
.screen_height = 540
tests: Test configured custom logical monitor scale Check that a configured logical monitor scale overrides any calculated one. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 09:46:33 -05:00
}
};
MetaMonitorTestSetup *test_setup;
tests: Derive configuration when stage views is disabled In order to test deriving the logical state from the underlying configuration, as is always done on X11, make the test backend derive the state when stage views are disabled. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 05:16:04 -04:00
if (!meta_is_stage_views_enabled ())
{
g_test_skip ("Not using stage views");
return;
}
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
tests: Test configured custom logical monitor scale Check that a configured logical monitor scale overrides any calculated one. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 09:46:33 -05:00
MONITOR_TEST_FLAG_NONE);
set_custom_monitor_config ("scale.xml");
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
tests: Test configured custom logical monitor scale Check that a configured logical monitor scale overrides any calculated one. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 09:46:33 -05:00
}
tests: Add tests for fractional scaling https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-05-25 05:22:14 -04:00
static void
meta_test_monitor_custom_fractional_scale_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1200,
.height = 900,
.refresh_rate = 60.000495910644531
}
},
.n_modes = 1,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125
},
},
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0
},
},
.n_crtcs = 1
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1200,
.height = 900,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.000495910644531,
tests: Add tests for fractional scaling https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-05-25 05:22:14 -04:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
}
},
.n_monitors = 1,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 800, .height = 600 },
.scale = 1.5
}
},
.n_logical_monitors = 1,
.primary_logical_monitor = 0,
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0,
}
},
.n_crtcs = 1,
.n_tiled_monitors = 0,
.screen_width = 800,
.screen_height = 600
}
};
MetaMonitorTestSetup *test_setup;
if (!meta_is_stage_views_enabled ())
{
g_test_skip ("Not using stage views");
return;
}
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
tests: Add tests for fractional scaling https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-05-25 05:22:14 -04:00
MONITOR_TEST_FLAG_NONE);
set_custom_monitor_config ("fractional-scale.xml");
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
tests: Add tests for fractional scaling https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-05-25 05:22:14 -04:00
}
tests: Add non-precise fractional scaling test https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-09 04:05:27 -04:00
static void
meta_test_monitor_custom_high_precision_fractional_scale_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.000495910644531
}
},
.n_modes = 1,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125
},
},
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0
},
},
.n_crtcs = 1
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.000495910644531,
tests: Add non-precise fractional scaling test https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-09 04:05:27 -04:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
}
},
.n_monitors = 1,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 744, .height = 558 },
.scale = 1024.0/744.0 /* 1.3763440847396851 */
}
},
.n_logical_monitors = 1,
.primary_logical_monitor = 0,
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0,
}
},
.n_crtcs = 1,
.n_tiled_monitors = 0,
.screen_width = 744,
.screen_height = 558
}
};
MetaMonitorTestSetup *test_setup;
if (!meta_is_stage_views_enabled ())
{
g_test_skip ("Not using stage views");
return;
}
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
tests: Add non-precise fractional scaling test https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-09 04:05:27 -04:00
MONITOR_TEST_FLAG_NONE);
set_custom_monitor_config ("high-precision-fractional-scale.xml");
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
tests: Add non-precise fractional scaling test https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-09 04:05:27 -04:00
}
monitor-unit-tests: Check custom tiled monitor config https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 09:48:36 -05:00
static void
meta_test_monitor_custom_tiled_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 400,
.height = 600,
.refresh_rate = 60.000495910644531
}
},
.n_modes = 1,
.outputs = {
{
.crtc = -1,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0, 1 },
.n_possible_crtcs = 2,
.width_mm = 222,
.height_mm = 125,
.tile_info = {
.group_id = 1,
.max_h_tiles = 2,
.max_v_tiles = 1,
.loc_h_tile = 0,
.loc_v_tile = 0,
.tile_w = 400,
.tile_h = 600
}
},
{
.crtc = -1,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0, 1 },
.n_possible_crtcs = 2,
.width_mm = 222,
.height_mm = 125,
.tile_info = {
.group_id = 1,
.max_h_tiles = 2,
.max_v_tiles = 1,
.loc_h_tile = 1,
.loc_v_tile = 0,
.tile_w = 400,
.tile_h = 600
}
}
},
.n_outputs = 2,
.crtcs = {
{
.current_mode = 0
},
{
.current_mode = -1
}
},
.n_crtcs = 2
},
.expect = {
.monitors = {
{
.outputs = { 0, 1 },
.n_outputs = 2,
.modes = {
{
.width = 800,
.height = 600,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.000495910644531,
monitor-unit-tests: Check custom tiled monitor config https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 09:48:36 -05:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0,
},
{
.output = 1,
.crtc_mode = 0,
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
}
},
.n_monitors = 1,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
Add support for scaled logical monitor framebuffers This commit adds support for rendering onto enlarged per logical monitor framebuffers, using the scaled clutter stage views, for HiDPI enabled logical monitors. This works by scaling the mode of the monitors in a logical monitors by the scale, no longer relying on scaling the window actors and window geometry for making windows have the correct size on HiDPI monitors. It is disabled by default, as in automatically created configurations will still use the old mode. This is partly because Xwayland clients will not yet work good enough to make it feasible. To enable, add the 'scale-monitor-framebuffer' keyword to the org.gnome.mutter.experimental-features gsettings array. It is still possible to specify the mode via the new D-Bus API, which has been adapted. The adaptations to the D-Bus API means the caller need to be aware of how to position logical monitors on the stage grid. This depends on the 'layout-mode' property that is used (see the DisplayConfig D-Bus documentation). https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-02-24 05:10:52 -05:00
.layout = { .x = 0, .y = 0, .width = 400, .height = 300 },
monitor-unit-tests: Check custom tiled monitor config https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 09:48:36 -05:00
.scale = 2
}
},
.n_logical_monitors = 1,
.primary_logical_monitor = 0,
.n_outputs = 2,
.crtcs = {
{
.current_mode = 0,
},
{
.current_mode = 0,
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
.x = 200,
monitor: Don't keep CRTC position in MetaMonitorCrtcMode The CRTC position depends on the transform and how the transform is implemented. The function calculating the positions still doesn't support anything but the non-transformed case; this commit is in preparation of adding support for transforms. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-17 05:21:10 -04:00
.y = 0
monitor-unit-tests: Check custom tiled monitor config https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 09:48:36 -05:00
}
},
.n_crtcs = 2,
.n_tiled_monitors = 1,
Add support for scaled logical monitor framebuffers This commit adds support for rendering onto enlarged per logical monitor framebuffers, using the scaled clutter stage views, for HiDPI enabled logical monitors. This works by scaling the mode of the monitors in a logical monitors by the scale, no longer relying on scaling the window actors and window geometry for making windows have the correct size on HiDPI monitors. It is disabled by default, as in automatically created configurations will still use the old mode. This is partly because Xwayland clients will not yet work good enough to make it feasible. To enable, add the 'scale-monitor-framebuffer' keyword to the org.gnome.mutter.experimental-features gsettings array. It is still possible to specify the mode via the new D-Bus API, which has been adapted. The adaptations to the D-Bus API means the caller need to be aware of how to position logical monitors on the stage grid. This depends on the 'layout-mode' property that is used (see the DisplayConfig D-Bus documentation). https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-02-24 05:10:52 -05:00
.screen_width = 400,
.screen_height = 300
monitor-unit-tests: Check custom tiled monitor config https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 09:48:36 -05:00
}
};
MetaMonitorTestSetup *test_setup;
tests: Derive configuration when stage views is disabled In order to test deriving the logical state from the underlying configuration, as is always done on X11, make the test backend derive the state when stage views are disabled. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 05:16:04 -04:00
if (!meta_is_stage_views_enabled ())
{
g_test_skip ("Not using stage views");
return;
}
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Check custom tiled monitor config https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 09:48:36 -05:00
MONITOR_TEST_FLAG_NONE);
set_custom_monitor_config ("tiled.xml");
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Check custom tiled monitor config https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 09:48:36 -05:00
}
tests/monitor-unit-tests: Add tests for custom tiled monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-06 00:13:07 -05:00
static void
meta_test_monitor_custom_tiled_custom_resolution_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 400,
.height = 600,
.refresh_rate = 60.000495910644531
},
{
.width = 640,
.height = 480,
.refresh_rate = 60.000495910644531
}
},
.n_modes = 2,
.outputs = {
{
.crtc = -1,
.modes = { 0, 1 },
.n_modes = 2,
.preferred_mode = 0,
.possible_crtcs = { 0, 1 },
.n_possible_crtcs = 2,
.width_mm = 222,
.height_mm = 125,
.tile_info = {
.group_id = 1,
.max_h_tiles = 2,
.max_v_tiles = 1,
.loc_h_tile = 0,
.loc_v_tile = 0,
.tile_w = 400,
.tile_h = 600
}
},
{
.crtc = -1,
.modes = { 0, 1 },
.n_modes = 2,
.preferred_mode = 0,
.possible_crtcs = { 0, 1 },
.n_possible_crtcs = 2,
.width_mm = 222,
.height_mm = 125,
.tile_info = {
.group_id = 1,
.max_h_tiles = 2,
.max_v_tiles = 1,
.loc_h_tile = 1,
.loc_v_tile = 0,
.tile_w = 400,
.tile_h = 600
}
}
},
.n_outputs = 2,
.crtcs = {
{
.current_mode = -1
},
{
.current_mode = -1
}
},
.n_crtcs = 2
},
.expect = {
.monitors = {
{
.outputs = { 0, 1 },
.n_outputs = 2,
.modes = {
{
.width = 800,
.height = 600,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.000495910644531,
tests/monitor-unit-tests: Add tests for custom tiled monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-06 00:13:07 -05:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0,
},
{
.output = 1,
.crtc_mode = 0,
}
}
},
{
.width = 640,
.height = 480,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.000495910644531,
tests/monitor-unit-tests: Add tests for custom tiled monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-06 00:13:07 -05:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 1,
},
{
.output = 1,
.crtc_mode = -1,
}
}
}
},
.n_modes = 2,
.current_mode = 1,
.width_mm = 222,
.height_mm = 125,
}
},
.n_monitors = 1,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 320, .height = 240 },
.scale = 2
}
},
.n_logical_monitors = 1,
.primary_logical_monitor = 0,
.n_outputs = 2,
.crtcs = {
{
.current_mode = 1,
},
{
.current_mode = -1,
monitor: Don't keep CRTC position in MetaMonitorCrtcMode The CRTC position depends on the transform and how the transform is implemented. The function calculating the positions still doesn't support anything but the non-transformed case; this commit is in preparation of adding support for transforms. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-17 05:21:10 -04:00
.x = 400,
.y = 0,
tests/monitor-unit-tests: Add tests for custom tiled monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-06 00:13:07 -05:00
}
},
.n_crtcs = 2,
.n_tiled_monitors = 1,
.screen_width = 320,
.screen_height = 240
}
};
MetaMonitorTestSetup *test_setup;
tests: Derive configuration when stage views is disabled In order to test deriving the logical state from the underlying configuration, as is always done on X11, make the test backend derive the state when stage views are disabled. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 05:16:04 -04:00
if (!meta_is_stage_views_enabled ())
{
g_test_skip ("Not using stage views");
return;
}
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
tests/monitor-unit-tests: Add tests for custom tiled monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-06 00:13:07 -05:00
MONITOR_TEST_FLAG_NONE);
set_custom_monitor_config ("tiled-custom-resolution.xml");
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
tests/monitor-unit-tests: Add tests for custom tiled monitor modes https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-06 00:13:07 -05:00
}
tests/monitor-unit-tests: Check handling of odd tiled monitors Add tests for handling tiled monitors where the origin tile output is not the main output. https://bugzilla.gnome.org/show_bug.cgi?id=781723
2017-05-01 00:12:42 -04:00
static void
meta_test_monitor_custom_tiled_non_preferred_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 640,
.height = 480,
.refresh_rate = 60.0
},
{
.width = 800,
.height = 600,
.refresh_rate = 60.0
},
{
.width = 512,
.height = 768,
.refresh_rate = 120.0
},
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0
},
},
.n_modes = 4,
.outputs = {
{
.crtc = -1,
.modes = { 0, 2 },
.n_modes = 2,
.preferred_mode = 1,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.tile_info = {
.group_id = 1,
.max_h_tiles = 2,
.max_v_tiles = 1,
.loc_h_tile = 0,
.loc_v_tile = 0,
.tile_w = 512,
.tile_h = 768
}
},
{
.crtc = -1,
.modes = { 1, 2, 3 },
.n_modes = 3,
.preferred_mode = 0,
.possible_crtcs = { 1 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.tile_info = {
.group_id = 1,
.max_h_tiles = 2,
.max_v_tiles = 1,
.loc_h_tile = 1,
.loc_v_tile = 0,
.tile_w = 512,
.tile_h = 768
}
}
},
.n_outputs = 2,
.crtcs = {
{
.current_mode = -1
},
{
.current_mode = -1
}
},
.n_crtcs = 2
},
.expect = {
.monitors = {
{
.outputs = { 0, 1 },
.n_outputs = 2,
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 120.0,
tests/monitor-unit-tests: Check handling of odd tiled monitors Add tests for handling tiled monitors where the origin tile output is not the main output. https://bugzilla.gnome.org/show_bug.cgi?id=781723
2017-05-01 00:12:42 -04:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 2
},
{
.output = 1,
.crtc_mode = 2,
}
}
},
{
.width = 800,
.height = 600,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.0,
tests/monitor-unit-tests: Check handling of odd tiled monitors Add tests for handling tiled monitors where the origin tile output is not the main output. https://bugzilla.gnome.org/show_bug.cgi?id=781723
2017-05-01 00:12:42 -04:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = -1
},
{
.output = 1,
.crtc_mode = 1,
}
}
},
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.0,
tests/monitor-unit-tests: Check handling of odd tiled monitors Add tests for handling tiled monitors where the origin tile output is not the main output. https://bugzilla.gnome.org/show_bug.cgi?id=781723
2017-05-01 00:12:42 -04:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = -1
},
{
.output = 1,
.crtc_mode = 3,
}
}
},
},
.n_modes = 3,
.current_mode = 1,
.width_mm = 222,
.height_mm = 125,
}
},
.n_monitors = 1,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 800, .height = 600 },
.scale = 1
},
},
.n_logical_monitors = 1,
.primary_logical_monitor = 0,
.n_outputs = 2,
.crtcs = {
{
.current_mode = -1,
},
{
.current_mode = 1,
}
},
.n_crtcs = 2,
.n_tiled_monitors = 1,
.screen_width = 800,
.screen_height = 600,
}
};
MetaMonitorTestSetup *test_setup;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
tests/monitor-unit-tests: Check handling of odd tiled monitors Add tests for handling tiled monitors where the origin tile output is not the main output. https://bugzilla.gnome.org/show_bug.cgi?id=781723
2017-05-01 00:12:42 -04:00
MONITOR_TEST_FLAG_NONE);
set_custom_monitor_config ("non-preferred-tiled-custom-resolution.xml");
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
tests/monitor-unit-tests: Check handling of odd tiled monitors Add tests for handling tiled monitors where the origin tile output is not the main output. https://bugzilla.gnome.org/show_bug.cgi?id=781723
2017-05-01 00:12:42 -04:00
}
tests: Check that mirroring is configured properly This test checks that mirroring works when using separate CRTCs. It does not check cloning. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 09:55:10 -05:00
static void
meta_test_monitor_custom_mirrored_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 800,
.height = 600,
.refresh_rate = 60.000495910644531
}
},
.n_modes = 1,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125
},
{
.crtc = 1,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 1 },
.n_possible_crtcs = 1,
.width_mm = 220,
.height_mm = 124
}
},
.n_outputs = 2,
.crtcs = {
{
.current_mode = 0
},
{
.current_mode = 0
}
},
.n_crtcs = 2
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 800,
.height = 600,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.000495910644531,
tests: Check that mirroring is configured properly This test checks that mirroring works when using separate CRTCs. It does not check cloning. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 09:55:10 -05:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125
},
{
.outputs = { 1 },
.n_outputs = 1,
.modes = {
{
.width = 800,
.height = 600,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.000495910644531,
tests: Check that mirroring is configured properly This test checks that mirroring works when using separate CRTCs. It does not check cloning. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 09:55:10 -05:00
.crtc_modes = {
{
.output = 1,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 220,
.height_mm = 124
}
},
.n_monitors = 2,
.logical_monitors = {
{
.monitors = { 0, 1 },
.n_monitors = 2,
.layout = { .x = 0, .y = 0, .width = 800, .height = 600 },
.scale = 1
}
},
.n_logical_monitors = 1,
.primary_logical_monitor = 0,
.n_outputs = 2,
.crtcs = {
{
.current_mode = 0,
},
{
.current_mode = 0,
}
},
.n_crtcs = 2,
.n_tiled_monitors = 0,
.screen_width = 800,
.screen_height = 600
}
};
MetaMonitorTestSetup *test_setup;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
tests: Check that mirroring is configured properly This test checks that mirroring works when using separate CRTCs. It does not check cloning. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 09:55:10 -05:00
MONITOR_TEST_FLAG_NONE);
set_custom_monitor_config ("mirrored.xml");
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
tests: Check that mirroring is configured properly This test checks that mirroring works when using separate CRTCs. It does not check cloning. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-19 09:55:10 -05:00
}
tests: Test that transforms are properly configured https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 02:28:25 -04:00
static void
meta_test_monitor_custom_first_rotated_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.000495910644531
}
},
.n_modes = 1,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
},
{
.crtc = 1,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 1 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
}
},
.n_outputs = 2,
.crtcs = {
{
.current_mode = 0,
},
{
.current_mode = 0
}
},
.n_crtcs = 2
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.000495910644531,
tests: Test that transforms are properly configured https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 02:28:25 -04:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
},
{
.outputs = { 1 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.000495910644531,
tests: Test that transforms are properly configured https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 02:28:25 -04:00
.crtc_modes = {
{
.output = 1,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
}
},
.n_monitors = 2,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 768, .height = 1024 },
.scale = 1,
.transform = META_MONITOR_TRANSFORM_270
},
{
.monitors = { 1 },
.n_monitors = 1,
.layout = { .x = 768, .y = 0, .width = 1024, .height = 768 },
.scale = 1
}
},
.n_logical_monitors = 2,
.primary_logical_monitor = 0,
.n_outputs = 2,
.crtcs = {
{
.current_mode = 0,
.transform = META_MONITOR_TRANSFORM_270
},
{
.current_mode = 0,
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
.x = 768,
tests: Test that transforms are properly configured https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 02:28:25 -04:00
}
},
.n_crtcs = 2,
.screen_width = 768 + 1024,
.screen_height = 1024
}
};
MetaMonitorTestSetup *test_setup;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
tests: Test that transforms are properly configured https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 02:28:25 -04:00
MONITOR_TEST_FLAG_NONE);
set_custom_monitor_config ("first-rotated.xml");
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
tests: Test that transforms are properly configured https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 02:28:25 -04:00
}
static void
meta_test_monitor_custom_second_rotated_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.000495910644531
}
},
.n_modes = 1,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
},
{
.crtc = 1,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 1 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
}
},
.n_outputs = 2,
.crtcs = {
{
.current_mode = 0
},
{
.current_mode = 0
}
},
.n_crtcs = 2
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.000495910644531,
tests: Test that transforms are properly configured https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 02:28:25 -04:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
},
{
.outputs = { 1 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.000495910644531,
tests: Test that transforms are properly configured https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 02:28:25 -04:00
.crtc_modes = {
{
.output = 1,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
}
},
.n_monitors = 2,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 256, .width = 1024, .height = 768 },
.scale = 1
},
{
.monitors = { 1 },
.n_monitors = 1,
.layout = { .x = 1024, .y = 0, .width = 768, .height = 1024 },
.scale = 1,
.transform = META_MONITOR_TRANSFORM_90
}
},
.n_logical_monitors = 2,
.primary_logical_monitor = 0,
.n_outputs = 2,
.crtcs = {
{
.current_mode = 0,
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
.y = 256,
tests: Test that transforms are properly configured https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 02:28:25 -04:00
},
{
.current_mode = 0,
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
.transform = META_MONITOR_TRANSFORM_90,
.x = 1024,
tests: Test that transforms are properly configured https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 02:28:25 -04:00
}
},
.n_crtcs = 2,
.screen_width = 768 + 1024,
.screen_height = 1024
}
};
MetaMonitorTestSetup *test_setup;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
tests: Test that transforms are properly configured https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 02:28:25 -04:00
MONITOR_TEST_FLAG_NONE);
set_custom_monitor_config ("second-rotated.xml");
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
tests: Test that transforms are properly configured https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 02:28:25 -04:00
}
tests: Test rotation of tiled monitors https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 03:38:56 -04:00
static void
meta_test_monitor_custom_second_rotated_tiled_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.000495910644531
},
{
.width = 400,
.height = 600,
.refresh_rate = 60.000495910644531
}
},
.n_modes = 2,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
},
{
.crtc = -1,
.modes = { 1 },
.n_modes = 1,
.preferred_mode = 1,
.possible_crtcs = { 1, 2 },
.n_possible_crtcs = 2,
.width_mm = 222,
.height_mm = 125,
.tile_info = {
.group_id = 1,
.max_h_tiles = 2,
.max_v_tiles = 1,
.loc_h_tile = 0,
.loc_v_tile = 0,
.tile_w = 400,
.tile_h = 600
}
},
{
.crtc = -1,
.modes = { 1 },
.n_modes = 1,
.preferred_mode = 1,
.possible_crtcs = { 1, 2 },
.n_possible_crtcs = 2,
.width_mm = 222,
.height_mm = 125,
.tile_info = {
.group_id = 1,
.max_h_tiles = 2,
.max_v_tiles = 1,
.loc_h_tile = 1,
.loc_v_tile = 0,
.tile_w = 400,
.tile_h = 600
}
}
},
.n_outputs = 3,
.crtcs = {
{
.current_mode = -1
},
{
.current_mode = -1
},
{
.current_mode = -1
}
},
.n_crtcs = 3
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.000495910644531,
tests: Test rotation of tiled monitors https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 03:38:56 -04:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
},
{
.outputs = { 1, 2 },
.n_outputs = 2,
.modes = {
{
.width = 800,
.height = 600,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.000495910644531,
tests: Test rotation of tiled monitors https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 03:38:56 -04:00
.crtc_modes = {
{
.output = 1,
.crtc_mode = 1,
},
{
.output = 2,
.crtc_mode = 1,
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
}
},
.n_monitors = 2,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 256, .width = 1024, .height = 768 },
.scale = 1
},
{
.monitors = { 1 },
.n_monitors = 1,
.layout = { .x = 1024, .y = 0, .width = 600, .height = 800 },
.scale = 1,
.transform = META_MONITOR_TRANSFORM_90
}
},
.n_logical_monitors = 2,
.primary_logical_monitor = 0,
.n_outputs = 3,
.crtcs = {
{
.current_mode = 0,
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
.y = 256,
tests: Test rotation of tiled monitors https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 03:38:56 -04:00
},
{
.current_mode = 1,
.transform = META_MONITOR_TRANSFORM_90,
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
.x = 1024,
monitor: Fix tile coordinate calculation Previously the tile coordinate was used to offset a CRTC scanout coordinate within a larger framebuffer. Since 3.36 we're always scanning out from (0, 0) as we always have one framebuffer per CRTC; we instead use the tile coordinate to calculate the coordinate the tile has in the stage view. Adapt calculation to fulfil this promise instead of the old one. This also corrects the tiled custom monitor test case. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1199
2020-04-14 15:11:28 -04:00
.y = 0,
tests: Test rotation of tiled monitors https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 03:38:56 -04:00
},
{
.current_mode = 1,
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
.transform = META_MONITOR_TRANSFORM_90,
.x = 1024,
monitor: Fix tile coordinate calculation Previously the tile coordinate was used to offset a CRTC scanout coordinate within a larger framebuffer. Since 3.36 we're always scanning out from (0, 0) as we always have one framebuffer per CRTC; we instead use the tile coordinate to calculate the coordinate the tile has in the stage view. Adapt calculation to fulfil this promise instead of the old one. This also corrects the tiled custom monitor test case. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1199
2020-04-14 15:11:28 -04:00
.y = 400,
tests: Test rotation of tiled monitors https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 03:38:56 -04:00
}
},
.n_crtcs = 3,
.n_tiled_monitors = 1,
.screen_width = 1024 + 600,
.screen_height = 1024
}
};
MetaMonitorTestSetup *test_setup;
tests: Test non-native monitor transform Test that configuration works as expected when the backend doesn't support handling the transform and an intermediate offscreen framebuffer is used. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 05:28:45 -04:00
MetaBackend *backend = meta_get_backend ();
MetaMonitorManager *monitor_manager =
meta_backend_get_monitor_manager (backend);
MetaMonitorManagerTest *monitor_manager_test =
META_MONITOR_MANAGER_TEST (monitor_manager);
tests: Test rotation of tiled monitors https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 03:38:56 -04:00
tests: Test non-native monitor transform Test that configuration works as expected when the backend doesn't support handling the transform and an intermediate offscreen framebuffer is used. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 05:28:45 -04:00
meta_monitor_manager_test_set_handles_transforms (monitor_manager_test,
TRUE);
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
tests: Test rotation of tiled monitors https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 03:38:56 -04:00
MONITOR_TEST_FLAG_NONE);
set_custom_monitor_config ("second-rotated-tiled.xml");
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
tests: Test rotation of tiled monitors https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 03:38:56 -04:00
}
tests/monitor-unit-tests: Test non-hw-transform rotated tiled monitors Should affect the assigned transform, but not the layout, as that is the layout on the stage, not the coordinates in any buffer. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1199
2020-04-14 04:41:37 -04:00
static void
meta_test_monitor_custom_second_rotated_nonnative_tiled_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.000495910644531
},
{
.width = 400,
.height = 600,
.refresh_rate = 60.000495910644531
}
},
.n_modes = 2,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
},
{
.crtc = -1,
.modes = { 1 },
.n_modes = 1,
.preferred_mode = 1,
.possible_crtcs = { 1, 2 },
.n_possible_crtcs = 2,
.width_mm = 222,
.height_mm = 125,
.tile_info = {
.group_id = 1,
.max_h_tiles = 2,
.max_v_tiles = 1,
.loc_h_tile = 0,
.loc_v_tile = 0,
.tile_w = 400,
.tile_h = 600
}
},
{
.crtc = -1,
.modes = { 1 },
.n_modes = 1,
.preferred_mode = 1,
.possible_crtcs = { 1, 2 },
.n_possible_crtcs = 2,
.width_mm = 222,
.height_mm = 125,
.tile_info = {
.group_id = 1,
.max_h_tiles = 2,
.max_v_tiles = 1,
.loc_h_tile = 1,
.loc_v_tile = 0,
.tile_w = 400,
.tile_h = 600
}
}
},
.n_outputs = 3,
.crtcs = {
{
.current_mode = -1
},
{
.current_mode = -1
},
{
.current_mode = -1
}
},
.n_crtcs = 3
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.000495910644531,
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
},
{
.outputs = { 1, 2 },
.n_outputs = 2,
.modes = {
{
.width = 800,
.height = 600,
.refresh_rate = 60.000495910644531,
.crtc_modes = {
{
.output = 1,
.crtc_mode = 1,
},
{
.output = 2,
.crtc_mode = 1,
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
}
},
.n_monitors = 2,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 256, .width = 1024, .height = 768 },
.scale = 1
},
{
.monitors = { 1 },
.n_monitors = 1,
.layout = { .x = 1024, .y = 0, .width = 600, .height = 800 },
.scale = 1,
.transform = META_MONITOR_TRANSFORM_90
}
},
.n_logical_monitors = 2,
.primary_logical_monitor = 0,
.n_outputs = 3,
.crtcs = {
{
.current_mode = 0,
.y = 256,
},
{
.current_mode = 1,
.transform = META_MONITOR_TRANSFORM_NORMAL,
.x = 1024,
.y = 0,
},
{
.current_mode = 1,
.transform = META_MONITOR_TRANSFORM_NORMAL,
.x = 1024,
.y = 400,
}
},
.n_crtcs = 3,
.n_tiled_monitors = 1,
.screen_width = 1024 + 600,
.screen_height = 1024
}
};
MetaMonitorTestSetup *test_setup;
MetaBackend *backend = meta_get_backend ();
MetaMonitorManager *monitor_manager =
meta_backend_get_monitor_manager (backend);
MetaMonitorManagerTest *monitor_manager_test =
META_MONITOR_MANAGER_TEST (monitor_manager);
meta_monitor_manager_test_set_handles_transforms (monitor_manager_test,
FALSE);
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
tests/monitor-unit-tests: Test non-hw-transform rotated tiled monitors Should affect the assigned transform, but not the layout, as that is the layout on the stage, not the coordinates in any buffer. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1199
2020-04-14 04:41:37 -04:00
MONITOR_TEST_FLAG_NONE);
set_custom_monitor_config ("second-rotated-tiled.xml");
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
tests/monitor-unit-tests: Test non-hw-transform rotated tiled monitors Should affect the assigned transform, but not the layout, as that is the layout on the stage, not the coordinates in any buffer. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1199
2020-04-14 04:41:37 -04:00
}
tests: Test non-native monitor transform Test that configuration works as expected when the backend doesn't support handling the transform and an intermediate offscreen framebuffer is used. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 05:28:45 -04:00
static void
meta_test_monitor_custom_second_rotated_nonnative_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.000495910644531
}
},
.n_modes = 1,
.outputs = {
{
.crtc = 0,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
},
{
.crtc = 1,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 1 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
}
},
.n_outputs = 2,
.crtcs = {
{
.current_mode = 0
},
{
.current_mode = 0
}
},
.n_crtcs = 2
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.000495910644531,
tests: Test non-native monitor transform Test that configuration works as expected when the backend doesn't support handling the transform and an intermediate offscreen framebuffer is used. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 05:28:45 -04:00
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
},
{
.outputs = { 1 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
tests: Test monitor mode refresh rate Check that the monitor refresh rate corresponds to the CRTC mode refresh rate. https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:08:43 -04:00
.refresh_rate = 60.000495910644531,
tests: Test non-native monitor transform Test that configuration works as expected when the backend doesn't support handling the transform and an intermediate offscreen framebuffer is used. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 05:28:45 -04:00
.crtc_modes = {
{
.output = 1,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
}
},
.n_monitors = 2,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 256, .width = 1024, .height = 768 },
.scale = 1
},
{
.monitors = { 1 },
.n_monitors = 1,
.layout = { .x = 1024, .y = 0, .width = 768, .height = 1024 },
.scale = 1,
.transform = META_MONITOR_TRANSFORM_90
}
},
.n_logical_monitors = 2,
.primary_logical_monitor = 0,
.n_outputs = 2,
.crtcs = {
{
.current_mode = 0,
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
.y = 256,
tests: Test non-native monitor transform Test that configuration works as expected when the backend doesn't support handling the transform and an intermediate offscreen framebuffer is used. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 05:28:45 -04:00
},
{
.current_mode = 0,
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
.transform = META_MONITOR_TRANSFORM_NORMAL,
.x = 1024,
tests: Test non-native monitor transform Test that configuration works as expected when the backend doesn't support handling the transform and an intermediate offscreen framebuffer is used. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 05:28:45 -04:00
}
},
.n_crtcs = 2,
.screen_width = 768 + 1024,
.screen_height = 1024
}
};
MetaMonitorTestSetup *test_setup;
MetaBackend *backend = meta_get_backend ();
MetaMonitorManager *monitor_manager =
meta_backend_get_monitor_manager (backend);
MetaMonitorManagerTest *monitor_manager_test =
META_MONITOR_MANAGER_TEST (monitor_manager);
if (!meta_is_stage_views_enabled ())
{
g_test_skip ("Not using stage views");
return;
}
meta_monitor_manager_test_set_handles_transforms (monitor_manager_test,
FALSE);
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
tests: Test non-native monitor transform Test that configuration works as expected when the backend doesn't support handling the transform and an intermediate offscreen framebuffer is used. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 05:28:45 -04:00
MONITOR_TEST_FLAG_NONE);
set_custom_monitor_config ("second-rotated.xml");
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
tests: Test non-native monitor transform Test that configuration works as expected when the backend doesn't support handling the transform and an intermediate offscreen framebuffer is used. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-21 05:28:45 -04:00
}
tests: Add test for setting an interlaced monitor mode https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:42:48 -04:00
static void
meta_test_monitor_custom_interlaced_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.000495910644531
},
{
.width = 1024,
.height = 768,
.refresh_rate = 60.000495910644531,
.flags = META_CRTC_MODE_FLAG_INTERLACE,
}
},
.n_modes = 2,
.outputs = {
{
.crtc = 0,
.modes = { 0, 1 },
.n_modes = 2,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125
},
},
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0
},
},
.n_crtcs = 1
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.000495910644531,
.flags = META_CRTC_MODE_FLAG_NONE,
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0,
},
}
},
{
.width = 1024,
.height = 768,
.refresh_rate = 60.000495910644531,
.flags = META_CRTC_MODE_FLAG_INTERLACE,
.crtc_modes = {
{
.output = 0,
.crtc_mode = 1,
}
}
}
},
.n_modes = 2,
.current_mode = 1,
.width_mm = 222,
.height_mm = 125,
}
},
.n_monitors = 1,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 1024, .height = 768 },
.scale = 1
}
},
.n_logical_monitors = 1,
.primary_logical_monitor = 0,
.n_outputs = 1,
.crtcs = {
{
.current_mode = 1,
}
},
.n_crtcs = 1,
.n_tiled_monitors = 0,
.screen_width = 1024,
.screen_height = 768
}
};
MetaMonitorTestSetup *test_setup;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
tests: Add test for setting an interlaced monitor mode https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:42:48 -04:00
MONITOR_TEST_FLAG_NONE);
set_custom_monitor_config ("interlaced.xml");
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
tests: Add test for setting an interlaced monitor mode https://bugzilla.gnome.org/show_bug.cgi?id=765011
2017-06-14 02:42:48 -04:00
}
monitor-unit-tests: Test configs with explicitly disabled monitors Check that configurations where monitors are disabled are properly used. Also test that old configurations with explicitly disabled outputs are migrated properly. https://bugzilla.gnome.org/show_bug.cgi?id=787629
2017-09-28 11:57:50 -04:00
static void
meta_test_monitor_custom_oneoff (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 800,
.height = 600,
.refresh_rate = 60.0
}
},
.n_modes = 1,
.outputs = {
{
.crtc = -1,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0, 1 },
.n_possible_crtcs = 2,
.width_mm = 222,
.height_mm = 125
},
{
.crtc = -1,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0, 1 },
.n_possible_crtcs = 2,
.width_mm = 222,
.height_mm = 125,
.serial = "0x654321"
}
},
.n_outputs = 2,
.crtcs = {
{
.current_mode = -1
},
{
.current_mode = -1
}
},
.n_crtcs = 2
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 800,
.height = 600,
.refresh_rate = 60.0,
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125
},
{
.outputs = { 1 },
.n_outputs = 1,
.modes = {
{
.width = 800,
.height = 600,
.refresh_rate = 60.0,
.crtc_modes = {
{
.output = 1,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = -1,
.width_mm = 222,
.height_mm = 125
}
},
.n_monitors = 2,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 800, .height = 600 },
.scale = 1,
.transform = META_MONITOR_TRANSFORM_NORMAL
},
},
.n_logical_monitors = 1,
.primary_logical_monitor = 0,
.n_outputs = 2,
.crtcs = {
{
.current_mode = 0,
},
{
.current_mode = -1,
}
},
.n_crtcs = 2,
.screen_width = 800,
.screen_height = 600,
}
};
MetaMonitorTestSetup *test_setup;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Test configs with explicitly disabled monitors Check that configurations where monitors are disabled are properly used. Also test that old configurations with explicitly disabled outputs are migrated properly. https://bugzilla.gnome.org/show_bug.cgi?id=787629
2017-09-28 11:57:50 -04:00
MONITOR_TEST_FLAG_NONE);
set_custom_monitor_config ("oneoff.xml");
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Test configs with explicitly disabled monitors Check that configurations where monitors are disabled are properly used. Also test that old configurations with explicitly disabled outputs are migrated properly. https://bugzilla.gnome.org/show_bug.cgi?id=787629
2017-09-28 11:57:50 -04:00
}
monitor-unit-tests: Check config loading on lid switches Check that we apply the correct stored configuration when the lid is opend and closed while an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 04:27:23 -05:00
static void
meta_test_monitor_custom_lid_switch_config (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.000495910644531
}
},
.n_modes = 1,
.outputs = {
{
monitor-unit-tests: initial crtcs in custom_lid_switch This test forgot to specify the existing CRTC routings in the setup. For the first output the default 0 was ok, now it is -1 to ensure that the code will assign it correctly. For the second output the default 0 was incorrect, because possible_crtcs does not include 0. Now that CRTC is initialized to off instead, because the second output is hotplugged later and running a CRTC without an output does not make sense. This fix will keep this test passing when a future patch attempts to preserve existing CRTC routings. Assuming that any existing routing is valid, such routing will be kept. In this test case the existing routing was illegal, it should have been impossible, which then causes that future patch to fail the test by assigning the wrong CRTC. https://gitlab.gnome.org/GNOME/mutter/issues/373
2019-01-29 07:27:25 -05:00
.crtc = -1,
monitor-unit-tests: Check config loading on lid switches Check that we apply the correct stored configuration when the lid is opend and closed while an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 04:27:23 -05:00
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
.is_laptop_panel = TRUE
},
{
monitor-unit-tests: initial crtcs in custom_lid_switch This test forgot to specify the existing CRTC routings in the setup. For the first output the default 0 was ok, now it is -1 to ensure that the code will assign it correctly. For the second output the default 0 was incorrect, because possible_crtcs does not include 0. Now that CRTC is initialized to off instead, because the second output is hotplugged later and running a CRTC without an output does not make sense. This fix will keep this test passing when a future patch attempts to preserve existing CRTC routings. Assuming that any existing routing is valid, such routing will be kept. In this test case the existing routing was illegal, it should have been impossible, which then causes that future patch to fail the test by assigning the wrong CRTC. https://gitlab.gnome.org/GNOME/mutter/issues/373
2019-01-29 07:27:25 -05:00
.crtc = -1,
monitor-unit-tests: Check config loading on lid switches Check that we apply the correct stored configuration when the lid is opend and closed while an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 04:27:23 -05:00
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 1 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125,
}
},
.n_outputs = 1, /* Second one hot plugged later */
.crtcs = {
{
.current_mode = 0,
},
{
.current_mode = 0
}
},
.n_crtcs = 2
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.000495910644531,
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
},
{
.outputs = { 1 },
.n_outputs = 1,
.modes = {
{
.width = 1024,
.height = 768,
.refresh_rate = 60.000495910644531,
.crtc_modes = {
{
.output = 1,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125,
}
},
.n_monitors = 1, /* Second one hot plugged later */
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 768, .height = 1024 },
.scale = 1,
.transform = META_MONITOR_TRANSFORM_270
},
{
.monitors = { 1 },
.n_monitors = 1,
.layout = { .x = 1024, .y = 0, .width = 768, .height = 1024 },
.scale = 1
}
},
.n_logical_monitors = 1, /* Second one hot plugged later */
.primary_logical_monitor = 0,
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0,
.transform = META_MONITOR_TRANSFORM_270
},
{
.current_mode = -1,
}
},
.n_crtcs = 2,
.screen_width = 768,
.screen_height = 1024
}
};
MetaMonitorTestSetup *test_setup;
MetaBackend *backend = meta_get_backend ();
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Check config loading on lid switches Check that we apply the correct stored configuration when the lid is opend and closed while an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 04:27:23 -05:00
MONITOR_TEST_FLAG_NONE);
set_custom_monitor_config ("lid-switch.xml");
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Check config loading on lid switches Check that we apply the correct stored configuration when the lid is opend and closed while an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 04:27:23 -05:00
/* External monitor connected */
test_case.setup.n_outputs = 2;
test_case.expect.n_monitors = 2;
test_case.expect.n_outputs = 2;
test_case.expect.crtcs[0].transform = META_MONITOR_TRANSFORM_NORMAL;
test_case.expect.crtcs[1].current_mode = 0;
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
test_case.expect.crtcs[1].x = 1024;
monitor-unit-tests: Check config loading on lid switches Check that we apply the correct stored configuration when the lid is opend and closed while an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 04:27:23 -05:00
test_case.expect.crtcs[1].transform = META_MONITOR_TRANSFORM_270;
test_case.expect.logical_monitors[0].layout =
(MetaRectangle) { .width = 1024, .height = 768 };
test_case.expect.logical_monitors[0].transform = META_MONITOR_TRANSFORM_NORMAL;
test_case.expect.logical_monitors[1].transform = META_MONITOR_TRANSFORM_270;
test_case.expect.n_logical_monitors = 2;
test_case.expect.screen_width = 1024 + 768;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Check config loading on lid switches Check that we apply the correct stored configuration when the lid is opend and closed while an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 04:27:23 -05:00
MONITOR_TEST_FLAG_NONE);
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Check config loading on lid switches Check that we apply the correct stored configuration when the lid is opend and closed while an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 04:27:23 -05:00
/* Lid was closed */
test_case.expect.crtcs[0].current_mode = -1;
test_case.expect.crtcs[1].transform = META_MONITOR_TRANSFORM_90;
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
test_case.expect.crtcs[1].x = 0;
monitor-unit-tests: Check config loading on lid switches Check that we apply the correct stored configuration when the lid is opend and closed while an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 04:27:23 -05:00
test_case.expect.monitors[0].current_mode = -1;
test_case.expect.logical_monitors[0].layout =
(MetaRectangle) { .width = 768, .height = 1024 };
test_case.expect.logical_monitors[0].monitors[0] = 1;
test_case.expect.logical_monitors[0].transform = META_MONITOR_TRANSFORM_90;
test_case.expect.n_logical_monitors = 1;
test_case.expect.screen_width = 768;
backend: Move lid-is-closed handling to MetaBackend Rather than handle UpClient in both MetaBackend (to reset the idletime when the lid is opened), and in MetaMonitorManager and MetaMonitorConfigManager (to turn the screen under the lid on/off depending on its status), move the ability to get the lid status from UPower or mock it in one place, in MetaBackend.
2018-04-16 14:07:45 -04:00
meta_backend_test_set_is_lid_closed (META_BACKEND_TEST (backend), TRUE);
monitor-unit-tests: Check config loading on lid switches Check that we apply the correct stored configuration when the lid is opend and closed while an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 04:27:23 -05:00
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Check config loading on lid switches Check that we apply the correct stored configuration when the lid is opend and closed while an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 04:27:23 -05:00
MONITOR_TEST_FLAG_NONE);
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Check config loading on lid switches Check that we apply the correct stored configuration when the lid is opend and closed while an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 04:27:23 -05:00
/* Lid was opened */
test_case.expect.crtcs[0].current_mode = 0;
test_case.expect.crtcs[0].transform = META_MONITOR_TRANSFORM_NORMAL;
test_case.expect.crtcs[1].current_mode = 0;
test_case.expect.crtcs[1].transform = META_MONITOR_TRANSFORM_270;
crtc: Move configured state to separate struct To make it more reliable to distinguish between values that are read from the backend implementation (which is likely to be irrelevant for anything but the backend implementation), split out those values (e.g. layout). This changes the meaning of what was MetaCrtc::rect, to a MetaCrtcConfig::layout which is the layout the CRTC has in the global coordinate space. https://gitlab.gnome.org/GNOME/mutter/merge_requests/1042
2020-01-14 16:34:44 -05:00
test_case.expect.crtcs[1].x = 1024;
monitor-unit-tests: Check config loading on lid switches Check that we apply the correct stored configuration when the lid is opend and closed while an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 04:27:23 -05:00
test_case.expect.monitors[0].current_mode = 0;
test_case.expect.logical_monitors[0].layout =
(MetaRectangle) { .width = 1024, .height = 768 };
test_case.expect.logical_monitors[0].monitors[0] = 0;
test_case.expect.logical_monitors[0].transform = META_MONITOR_TRANSFORM_NORMAL;
test_case.expect.logical_monitors[1].transform = META_MONITOR_TRANSFORM_270;
test_case.expect.n_logical_monitors = 2;
test_case.expect.screen_width = 1024 + 768;
backend: Move lid-is-closed handling to MetaBackend Rather than handle UpClient in both MetaBackend (to reset the idletime when the lid is opened), and in MetaMonitorManager and MetaMonitorConfigManager (to turn the screen under the lid on/off depending on its status), move the ability to get the lid status from UPower or mock it in one place, in MetaBackend.
2018-04-16 14:07:45 -04:00
meta_backend_test_set_is_lid_closed (META_BACKEND_TEST (backend), FALSE);
monitor-unit-tests: Check config loading on lid switches Check that we apply the correct stored configuration when the lid is opend and closed while an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 04:27:23 -05:00
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-unit-tests: Check config loading on lid switches Check that we apply the correct stored configuration when the lid is opend and closed while an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 04:27:23 -05:00
MONITOR_TEST_FLAG_NONE);
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-unit-tests: Check config loading on lid switches Check that we apply the correct stored configuration when the lid is opend and closed while an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 04:27:23 -05:00
}
tests: Add monitor config migration tests So far some basic testing, including: * Test that the migrated configuration is applicable * Test that a monitors.xml with multiple configurations are translated * Test rotation * Test tiled monitor discovery (well, test a made up tiled monitor configuration since I don't have a real one) https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-08-10 05:12:39 -04:00
static void
meta_test_monitor_migrated_rotated (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 800,
.height = 600,
.refresh_rate = 60.0
}
},
.n_modes = 1,
.outputs = {
{
.crtc = -1,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125
}
},
.n_outputs = 1,
.crtcs = {
{
.current_mode = -1
}
},
.n_crtcs = 1
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 800,
.height = 600,
.refresh_rate = 60.0,
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125
}
},
.n_monitors = 1,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 600, .height = 800 },
.scale = 1,
.transform = META_MONITOR_TRANSFORM_270
},
},
.n_logical_monitors = 1,
.primary_logical_monitor = 0,
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0,
monitor-unit-tests: Always reset CRTC transform ability Changing the test monitor managers ability to rotate CRTCs in one test affected the next test. Avoid leaking such state by resetting it before each test. To continue passing, some tests needed to be updated regarding to still pass. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 04:25:07 -05:00
.transform = META_MONITOR_TRANSFORM_270
tests: Add monitor config migration tests So far some basic testing, including: * Test that the migrated configuration is applicable * Test that a monitors.xml with multiple configurations are translated * Test rotation * Test tiled monitor discovery (well, test a made up tiled monitor configuration since I don't have a real one) https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-08-10 05:12:39 -04:00
}
},
.n_crtcs = 1,
.screen_width = 600,
.screen_height = 800,
}
};
MetaMonitorTestSetup *test_setup;
MetaBackend *backend = meta_get_backend ();
MetaMonitorManager *monitor_manager =
meta_backend_get_monitor_manager (backend);
MetaMonitorConfigManager *config_manager = monitor_manager->config_manager;
MetaMonitorConfigStore *config_store =
meta_monitor_config_manager_get_store (config_manager);
g_autofree char *migrated_path = NULL;
const char *old_config_path;
g_autoptr (GFile) old_config_file = NULL;
GError *error = NULL;
const char *expected_path;
g_autofree char *migrated_data = NULL;
g_autofree char *expected_data = NULL;
g_autoptr (GFile) migrated_file = NULL;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
tests: Add monitor config migration tests So far some basic testing, including: * Test that the migrated configuration is applicable * Test that a monitors.xml with multiple configurations are translated * Test rotation * Test tiled monitor discovery (well, test a made up tiled monitor configuration since I don't have a real one) https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-08-10 05:12:39 -04:00
MONITOR_TEST_FLAG_NONE);
migrated_path = g_build_filename (g_get_tmp_dir (),
"test-finished-migrated-monitors.xml",
NULL);
if (!meta_monitor_config_store_set_custom (config_store,
"/dev/null",
migrated_path,
monitor-config-store: Add way to define config store loading policy This adds a way to define a way, at the system level, to define a policy of how monitor configuration files are loaded. The intended use case is to e.g. either prefer system level monitor configurations before user levels, or only allow system level configurations. Examples: Prefer system over user level configurations: <monitors version="2"> <policy> <stores> <store>system</store> <store>user</store> </stores> </policy> <configuration> ... </configuration> </monitors> Only allow system level configurations: <monitors version="2"> <policy> <stores> <store>system</store> </stores> </policy> <configuration> ... </configuration> </monitors> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2022-01-17 05:45:53 -05:00
META_MONITORS_CONFIG_FLAG_NONE,
tests: Add monitor config migration tests So far some basic testing, including: * Test that the migrated configuration is applicable * Test that a monitors.xml with multiple configurations are translated * Test rotation * Test tiled monitor discovery (well, test a made up tiled monitor configuration since I don't have a real one) https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-08-10 05:12:39 -04:00
&error))
g_error ("Failed to set custom config store files: %s", error->message);
old_config_path = g_test_get_filename (G_TEST_DIST,
"tests", "migration",
"rotated-old.xml",
NULL);
old_config_file = g_file_new_for_path (old_config_path);
if (!meta_migrate_old_monitors_config (config_store,
old_config_file,
&error))
monitor-tests: Fix error message grammar mistake
2017-10-04 09:43:09 -04:00
g_error ("Failed to migrate config: %s", error->message);
tests: Add monitor config migration tests So far some basic testing, including: * Test that the migrated configuration is applicable * Test that a monitors.xml with multiple configurations are translated * Test rotation * Test tiled monitor discovery (well, test a made up tiled monitor configuration since I don't have a real one) https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-08-10 05:12:39 -04:00
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
tests: Add monitor config migration tests So far some basic testing, including: * Test that the migrated configuration is applicable * Test that a monitors.xml with multiple configurations are translated * Test rotation * Test tiled monitor discovery (well, test a made up tiled monitor configuration since I don't have a real one) https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-08-10 05:12:39 -04:00
expected_path = g_test_get_filename (G_TEST_DIST,
"tests", "migration",
"rotated-new-finished.xml",
NULL);
expected_data = read_file (expected_path);
migrated_data = read_file (migrated_path);
g_assert_nonnull (expected_data);
g_assert_nonnull (migrated_data);
g_assert (strcmp (expected_data, migrated_data) == 0);
migrated_file = g_file_new_for_path (migrated_path);
if (!g_file_delete (migrated_file, NULL, &error))
g_error ("Failed to remove test data output file: %s", error->message);
}
monitor-tests: Test config migration with refresh rate wiggle room Check that we finish configurations within range, and discard the ones out of range. https://bugzilla.gnome.org/show_bug.cgi?id=787668
2017-09-25 17:59:40 -04:00
static void
meta_test_monitor_migrated_wiggle_discard (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 800,
.height = 600,
.refresh_rate = 59.0
}
},
.n_modes = 1,
.outputs = {
{
.crtc = -1,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125
}
},
.n_outputs = 1,
.crtcs = {
{
.current_mode = -1
}
},
.n_crtcs = 1
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 800,
.height = 600,
.refresh_rate = 59.0,
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125
}
},
.n_monitors = 1,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 800, .height = 600 },
.scale = 1,
.transform = META_MONITOR_TRANSFORM_NORMAL
},
},
.n_logical_monitors = 1,
.primary_logical_monitor = 0,
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0,
}
},
.n_crtcs = 1,
.screen_width = 800,
.screen_height = 600,
}
};
MetaMonitorTestSetup *test_setup;
MetaBackend *backend = meta_get_backend ();
MetaMonitorManager *monitor_manager =
meta_backend_get_monitor_manager (backend);
MetaMonitorConfigManager *config_manager = monitor_manager->config_manager;
MetaMonitorConfigStore *config_store =
meta_monitor_config_manager_get_store (config_manager);
g_autofree char *migrated_path = NULL;
const char *old_config_path;
g_autoptr (GFile) old_config_file = NULL;
GError *error = NULL;
const char *expected_path;
g_autofree char *migrated_data = NULL;
g_autofree char *expected_data = NULL;
g_autoptr (GFile) migrated_file = NULL;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-tests: Test config migration with refresh rate wiggle room Check that we finish configurations within range, and discard the ones out of range. https://bugzilla.gnome.org/show_bug.cgi?id=787668
2017-09-25 17:59:40 -04:00
MONITOR_TEST_FLAG_NONE);
migrated_path = g_build_filename (g_get_tmp_dir (),
"test-finished-migrated-monitors.xml",
NULL);
if (!meta_monitor_config_store_set_custom (config_store,
"/dev/null",
migrated_path,
monitor-config-store: Add way to define config store loading policy This adds a way to define a way, at the system level, to define a policy of how monitor configuration files are loaded. The intended use case is to e.g. either prefer system level monitor configurations before user levels, or only allow system level configurations. Examples: Prefer system over user level configurations: <monitors version="2"> <policy> <stores> <store>system</store> <store>user</store> </stores> </policy> <configuration> ... </configuration> </monitors> Only allow system level configurations: <monitors version="2"> <policy> <stores> <store>system</store> </stores> </policy> <configuration> ... </configuration> </monitors> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2022-01-17 05:45:53 -05:00
META_MONITORS_CONFIG_FLAG_NONE,
monitor-tests: Test config migration with refresh rate wiggle room Check that we finish configurations within range, and discard the ones out of range. https://bugzilla.gnome.org/show_bug.cgi?id=787668
2017-09-25 17:59:40 -04:00
&error))
g_error ("Failed to set custom config store files: %s", error->message);
old_config_path = g_test_get_filename (G_TEST_DIST,
"tests", "migration",
"wiggle-old.xml",
NULL);
old_config_file = g_file_new_for_path (old_config_path);
if (!meta_migrate_old_monitors_config (config_store,
old_config_file,
&error))
g_error ("Failed to migrate config: %s", error->message);
g_test_expect_message (G_LOG_DOMAIN, G_LOG_LEVEL_WARNING,
"Failed to finish monitors config migration: "
"Mode not available on monitor");
emulate_hotplug (test_setup);
g_test_assert_expected_messages ();
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-tests: Test config migration with refresh rate wiggle room Check that we finish configurations within range, and discard the ones out of range. https://bugzilla.gnome.org/show_bug.cgi?id=787668
2017-09-25 17:59:40 -04:00
expected_path = g_test_get_filename (G_TEST_DIST,
"tests", "migration",
"wiggle-new-discarded.xml",
NULL);
expected_data = read_file (expected_path);
migrated_data = read_file (migrated_path);
g_assert_nonnull (expected_data);
g_assert_nonnull (migrated_data);
g_assert (strcmp (expected_data, migrated_data) == 0);
migrated_file = g_file_new_for_path (migrated_path);
if (!g_file_delete (migrated_file, NULL, &error))
g_error ("Failed to remove test data output file: %s", error->message);
}
tests/monitor-unit-tests: Add window tiling hot plug test This test that we handle hot plugs correctly together with tiled windows. https://gitlab.gnome.org/GNOME/mutter/merge_requests/912
2019-11-01 08:38:25 -04:00
static gboolean
quit_main_loop (gpointer data)
{
GMainLoop *loop = data;
g_main_loop_quit (loop);
return G_SOURCE_REMOVE;
}
static void
dispatch (void)
{
GMainLoop *loop;
loop = g_main_loop_new (NULL, FALSE);
meta_later_add (META_LATER_BEFORE_REDRAW,
quit_main_loop,
loop,
NULL);
g_main_loop_run (loop);
}
tests/utils: Prefix TestClient with Meta Soon we'll expose it via a libmutter-test library. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-06 17:34:36 -04:00
static MetaTestClient *
tests: Move 'wait-for-X11-display' helper to MetaContextTest Gets rid of a un-prefixed helper function relying on a global singleton. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-11 03:35:04 -04:00
create_test_window (MetaContext *context,
const char *window_name)
tests/monitor-unit-tests: Add window tiling hot plug test This test that we handle hot plugs correctly together with tiled windows. https://gitlab.gnome.org/GNOME/mutter/merge_requests/912
2019-11-01 08:38:25 -04:00
{
tests/utils: Prefix TestClient with Meta Soon we'll expose it via a libmutter-test library. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-06 17:34:36 -04:00
MetaTestClient *test_client;
tests/monitor-unit-tests: Add window tiling hot plug test This test that we handle hot plugs correctly together with tiled windows. https://gitlab.gnome.org/GNOME/mutter/merge_requests/912
2019-11-01 08:38:25 -04:00
static int client_count = 0;
g_autofree char *client_name = NULL;
g_autoptr (GError) error = NULL;
client_name = g_strdup_printf ("test_client_%d", client_count++);
tests: Move 'wait-for-X11-display' helper to MetaContextTest Gets rid of a un-prefixed helper function relying on a global singleton. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-11 03:35:04 -04:00
test_client = meta_test_client_new (context,
client_name, META_WINDOW_CLIENT_TYPE_WAYLAND,
tests/utils: Prefix TestClient with Meta Soon we'll expose it via a libmutter-test library. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-06 17:34:36 -04:00
&error);
tests/monitor-unit-tests: Add window tiling hot plug test This test that we handle hot plugs correctly together with tiled windows. https://gitlab.gnome.org/GNOME/mutter/merge_requests/912
2019-11-01 08:38:25 -04:00
if (!test_client)
g_error ("Failed to launch test client: %s", error->message);
tests/utils: Prefix TestClient with Meta Soon we'll expose it via a libmutter-test library. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-06 17:34:36 -04:00
if (!meta_test_client_do (test_client, &error,
"create", window_name,
NULL))
tests/monitor-unit-tests: Add window tiling hot plug test This test that we handle hot plugs correctly together with tiled windows. https://gitlab.gnome.org/GNOME/mutter/merge_requests/912
2019-11-01 08:38:25 -04:00
g_error ("Failed to create window: %s", error->message);
return test_client;
}
static void
meta_test_monitor_wm_tiling (void)
{
tests: Move 'wait-for-X11-display' helper to MetaContextTest Gets rid of a un-prefixed helper function relying on a global singleton. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-11 03:35:04 -04:00
MetaContext *context = test_context;
tests/monitor-unit-tests: Add window tiling hot plug test This test that we handle hot plugs correctly together with tiled windows. https://gitlab.gnome.org/GNOME/mutter/merge_requests/912
2019-11-01 08:38:25 -04:00
MonitorTestCase test_case = initial_test_case;
MetaMonitorTestSetup *test_setup;
g_autoptr (GError) error = NULL;
tests/utils: Prefix TestClient with Meta Soon we'll expose it via a libmutter-test library. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-06 17:34:36 -04:00
MetaTestClient *test_client;
tests/monitor-unit-tests: Add window tiling hot plug test This test that we handle hot plugs correctly together with tiled windows. https://gitlab.gnome.org/GNOME/mutter/merge_requests/912
2019-11-01 08:38:25 -04:00
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
tests/monitor-unit-tests: Add window tiling hot plug test This test that we handle hot plugs correctly together with tiled windows. https://gitlab.gnome.org/GNOME/mutter/merge_requests/912
2019-11-01 08:38:25 -04:00
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
/*
* 1) Start with two monitors connected.
* 2) Tile it on the second monitor.
* 3) Unplug both monitors.
* 4) Replug in first monitor.
*/
const char *test_window_name= "window1";
tests: Move 'wait-for-X11-display' helper to MetaContextTest Gets rid of a un-prefixed helper function relying on a global singleton. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-11 03:35:04 -04:00
test_client = create_test_window (context, test_window_name);
tests/monitor-unit-tests: Add window tiling hot plug test This test that we handle hot plugs correctly together with tiled windows. https://gitlab.gnome.org/GNOME/mutter/merge_requests/912
2019-11-01 08:38:25 -04:00
tests/utils: Prefix TestClient with Meta Soon we'll expose it via a libmutter-test library. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-06 17:34:36 -04:00
if (!meta_test_client_do (test_client, &error,
"show", test_window_name,
NULL))
tests/monitor-unit-tests: Add window tiling hot plug test This test that we handle hot plugs correctly together with tiled windows. https://gitlab.gnome.org/GNOME/mutter/merge_requests/912
2019-11-01 08:38:25 -04:00
g_error ("Failed to show the window: %s", error->message);
MetaWindow *test_window =
tests/utils: Prefix TestClient with Meta Soon we'll expose it via a libmutter-test library. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-06 17:34:36 -04:00
meta_test_client_find_window (test_client,
test_window_name,
&error);
tests/monitor-unit-tests: Add window tiling hot plug test This test that we handle hot plugs correctly together with tiled windows. https://gitlab.gnome.org/GNOME/mutter/merge_requests/912
2019-11-01 08:38:25 -04:00
if (!test_window)
g_error ("Failed to find the window: %s", error->message);
tests/utils: Prefix TestClient with Meta Soon we'll expose it via a libmutter-test library. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-06 17:34:36 -04:00
meta_test_client_wait_for_window_shown (test_client, test_window);
tests/monitor-unit-tests: Add window tiling hot plug test This test that we handle hot plugs correctly together with tiled windows. https://gitlab.gnome.org/GNOME/mutter/merge_requests/912
2019-11-01 08:38:25 -04:00
meta_window_tile (test_window, META_TILE_MAXIMIZED);
meta_window_move_to_monitor (test_window, 1);
check_test_client_state (test_client);
test_case.setup.n_outputs = 0;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
tests/monitor-unit-tests: Add window tiling hot plug test This test that we handle hot plugs correctly together with tiled windows. https://gitlab.gnome.org/GNOME/mutter/merge_requests/912
2019-11-01 08:38:25 -04:00
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
test_case.setup.n_outputs = 1;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
tests/monitor-unit-tests: Add window tiling hot plug test This test that we handle hot plugs correctly together with tiled windows. https://gitlab.gnome.org/GNOME/mutter/merge_requests/912
2019-11-01 08:38:25 -04:00
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
dispatch ();
tests/monitor-unit-tests: Add another tiling window hot plug test Checks that we handle hot plugs of a untiled window, that was previously tiled. https://gitlab.gnome.org/GNOME/mutter/merge_requests/912
2019-11-01 08:48:50 -04:00
/*
* 1) Start with two monitors connected.
* 2) Tile a window on the second monitor.
* 3) Untile window.
* 4) Unplug monitor.
* 5) Tile window again.
*/
test_case.setup.n_outputs = 2;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
tests/monitor-unit-tests: Add another tiling window hot plug test Checks that we handle hot plugs of a untiled window, that was previously tiled. https://gitlab.gnome.org/GNOME/mutter/merge_requests/912
2019-11-01 08:48:50 -04:00
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
meta_window_move_to_monitor (test_window, 1);
meta_window_tile (test_window, META_TILE_NONE);
test_case.setup.n_outputs = 1;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
tests/monitor-unit-tests: Add another tiling window hot plug test Checks that we handle hot plugs of a untiled window, that was previously tiled. https://gitlab.gnome.org/GNOME/mutter/merge_requests/912
2019-11-01 08:48:50 -04:00
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
meta_window_tile (test_window, META_TILE_MAXIMIZED);
tests/utils: Prefix TestClient with Meta Soon we'll expose it via a libmutter-test library. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-06 17:34:36 -04:00
meta_test_client_destroy (test_client);
tests/monitor-unit-tests: Add window tiling hot plug test This test that we handle hot plugs correctly together with tiled windows. https://gitlab.gnome.org/GNOME/mutter/merge_requests/912
2019-11-01 08:38:25 -04:00
}
monitor-tests: Test config migration with refresh rate wiggle room Check that we finish configurations within range, and discard the ones out of range. https://bugzilla.gnome.org/show_bug.cgi?id=787668
2017-09-25 17:59:40 -04:00
static void
meta_test_monitor_migrated_wiggle (void)
{
MonitorTestCase test_case = {
.setup = {
.modes = {
{
.width = 800,
.height = 600,
.refresh_rate = 60.0
}
},
.n_modes = 1,
.outputs = {
{
.crtc = -1,
.modes = { 0 },
.n_modes = 1,
.preferred_mode = 0,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125
}
},
.n_outputs = 1,
.crtcs = {
{
.current_mode = -1
}
},
.n_crtcs = 1
},
.expect = {
.monitors = {
{
.outputs = { 0 },
.n_outputs = 1,
.modes = {
{
.width = 800,
.height = 600,
.refresh_rate = 60.0,
.crtc_modes = {
{
.output = 0,
.crtc_mode = 0
}
}
}
},
.n_modes = 1,
.current_mode = 0,
.width_mm = 222,
.height_mm = 125
}
},
.n_monitors = 1,
.logical_monitors = {
{
.monitors = { 0 },
.n_monitors = 1,
.layout = { .x = 0, .y = 0, .width = 600, .height = 800 },
.scale = 1,
.transform = META_MONITOR_TRANSFORM_90
},
},
.n_logical_monitors = 1,
.primary_logical_monitor = 0,
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0,
monitor-unit-tests: Always reset CRTC transform ability Changing the test monitor managers ability to rotate CRTCs in one test affected the next test. Avoid leaking such state by resetting it before each test. To continue passing, some tests needed to be updated regarding to still pass. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 04:25:07 -05:00
.transform = META_MONITOR_TRANSFORM_90
monitor-tests: Test config migration with refresh rate wiggle room Check that we finish configurations within range, and discard the ones out of range. https://bugzilla.gnome.org/show_bug.cgi?id=787668
2017-09-25 17:59:40 -04:00
}
},
.n_crtcs = 1,
.screen_width = 600,
.screen_height = 800,
}
};
MetaMonitorTestSetup *test_setup;
MetaBackend *backend = meta_get_backend ();
MetaMonitorManager *monitor_manager =
meta_backend_get_monitor_manager (backend);
MetaMonitorConfigManager *config_manager = monitor_manager->config_manager;
MetaMonitorConfigStore *config_store =
meta_monitor_config_manager_get_store (config_manager);
g_autofree char *migrated_path = NULL;
const char *old_config_path;
g_autoptr (GFile) old_config_file = NULL;
GError *error = NULL;
const char *expected_path;
g_autofree char *migrated_data = NULL;
g_autofree char *expected_data = NULL;
g_autoptr (GFile) migrated_file = NULL;
tests/monitor-unit-tests: Use TestCaseSetup for building TestSetup We're going to move the functions for building MonitorTestSetups to the common monitor-test-utils.c file. To make building test setups a bit more straightforward in case no TestCaseExpect is wanted, change create_monitor_test_setup() to take a MonitorTestCaseSetup instead of a MonitorTestCase as an argument. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 15:03:47 -04:00
test_setup = create_monitor_test_setup (&test_case.setup,
monitor-tests: Test config migration with refresh rate wiggle room Check that we finish configurations within range, and discard the ones out of range. https://bugzilla.gnome.org/show_bug.cgi?id=787668
2017-09-25 17:59:40 -04:00
MONITOR_TEST_FLAG_NONE);
migrated_path = g_build_filename (g_get_tmp_dir (),
"test-finished-migrated-monitors.xml",
NULL);
if (!meta_monitor_config_store_set_custom (config_store,
"/dev/null",
migrated_path,
monitor-config-store: Add way to define config store loading policy This adds a way to define a way, at the system level, to define a policy of how monitor configuration files are loaded. The intended use case is to e.g. either prefer system level monitor configurations before user levels, or only allow system level configurations. Examples: Prefer system over user level configurations: <monitors version="2"> <policy> <stores> <store>system</store> <store>user</store> </stores> </policy> <configuration> ... </configuration> </monitors> Only allow system level configurations: <monitors version="2"> <policy> <stores> <store>system</store> </stores> </policy> <configuration> ... </configuration> </monitors> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2030>
2022-01-17 05:45:53 -05:00
META_MONITORS_CONFIG_FLAG_NONE,
monitor-tests: Test config migration with refresh rate wiggle room Check that we finish configurations within range, and discard the ones out of range. https://bugzilla.gnome.org/show_bug.cgi?id=787668
2017-09-25 17:59:40 -04:00
&error))
g_error ("Failed to set custom config store files: %s", error->message);
old_config_path = g_test_get_filename (G_TEST_DIST,
"tests", "migration",
"wiggle-old.xml",
NULL);
old_config_file = g_file_new_for_path (old_config_path);
if (!meta_migrate_old_monitors_config (config_store,
old_config_file,
&error))
g_error ("Failed to migrate config: %s", error->message);
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor configuration",
check_monitor_configuration (&test_case.expect));
tests/monitor-unit-tests: Check test state outside of common function check_monitor_test_clients_state() is a function that's only meant to be used in the monitor-unit-tests, and since we're going to move the functions for creating MonitorTestSetups into a common file, this function is going to be in the way of that. So move the checking of the test client state outside of check_monitor_test_clients_state(). https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1243
2020-05-08 17:09:06 -04:00
check_monitor_test_clients_state ();
monitor-tests: Test config migration with refresh rate wiggle room Check that we finish configurations within range, and discard the ones out of range. https://bugzilla.gnome.org/show_bug.cgi?id=787668
2017-09-25 17:59:40 -04:00
expected_path = g_test_get_filename (G_TEST_DIST,
"tests", "migration",
"wiggle-new-finished.xml",
NULL);
expected_data = read_file (expected_path);
migrated_data = read_file (migrated_path);
g_assert_nonnull (expected_data);
g_assert_nonnull (migrated_data);
g_assert (strcmp (expected_data, migrated_data) == 0);
migrated_file = g_file_new_for_path (migrated_path);
if (!g_file_delete (migrated_file, NULL, &error))
g_error ("Failed to remove test data output file: %s", error->message);
}
monitor-unit-tests: Check integer scaling values are matching expectations A per previous commit we can now ensure that all the scaling values when using non-fractional scaling have the value we expect. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1878>
2021-05-28 13:32:42 -04:00
static void
meta_test_monitor_supported_integer_scales (void)
{
MonitorTestCase test_case = {
.setup = {
.n_modes = 21,
.modes = {
{
.width = 800,
.height = 600,
.refresh_rate = 60.0
},
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0
},
{
.width = 1280,
.height = 720,
.refresh_rate = 60.0,
},
{
.width = 1280,
.height = 800,
.refresh_rate = 60.0,
},
{
.width = 1280,
.height = 1024,
.refresh_rate = 60.0,
},
{
.width = 1366,
.height = 768,
.refresh_rate = 60.0,
},
{
.width = 1440,
.height = 900,
.refresh_rate = 60.0,
},
{
.width = 1400,
.height = 1050,
.refresh_rate = 60.0,
},
{
.width = 1600,
.height = 900,
.refresh_rate = 60.0,
},
{
.width = 1920,
.height = 1080,
.refresh_rate = 60.0,
},
{
.width = 1920,
.height = 1200,
.refresh_rate = 60.0,
},
{
.width = 2650,
.height = 1440,
.refresh_rate = 60.0,
},
{
.width = 2880,
.height = 1800,
.refresh_rate = 60.0,
},
{
.width = 3200,
.height = 1800,
.refresh_rate = 60.0,
},
{
.width = 3200,
.height = 2048,
.refresh_rate = 60.0,
},
{
.width = 3840,
.height = 2160,
.refresh_rate = 60.0,
},
{
.width = 3840,
.height = 2400,
.refresh_rate = 60.0,
},
{
.width = 4096,
.height = 2160,
.refresh_rate = 60.0,
},
{
.width = 4096,
.height = 3072,
.refresh_rate = 60.0,
},
{
.width = 5120,
.height = 2880,
.refresh_rate = 60.0,
},
{
.width = 7680,
.height = 4320,
.refresh_rate = 60.0,
},
},
.outputs = {
{
.crtc = -1,
.modes = { 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16,
17, 18, 19, 20 },
.n_modes = 21,
.preferred_mode = 5,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125
}
},
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0
}
},
.n_crtcs = 1
},
.expect = {
.n_monitors = 1,
.monitors = {
{
.n_modes = 21,
.modes = {
{
.width = 800,
.height = 600,
.n_scales = 1,
.scales = { 1.0 },
},
{
.width = 1024,
.height = 768,
.n_scales = 1,
.scales = { 1.0 },
},
{
.width = 1280,
.height = 720,
.n_scales = 1,
.scales = { 1.0 },
},
{
.width = 1280,
.height = 800,
.n_scales = 1,
.scales = { 1.0 },
},
{
.width = 1280,
.height = 1024,
.n_scales = 1,
.scales = { 1.0 },
},
{
.width = 1366,
.height = 768,
.n_scales = 1,
.scales = { 1.0 },
},
{
.width = 1440,
.height = 900,
.n_scales = 1,
.scales = { 1.0 },
},
{
.width = 1400,
.height = 1050,
.n_scales = 1,
.scales = { 1.0 },
},
{
.width = 1600,
.height = 900,
.n_scales = 1,
.scales = { 1.0 },
},
{
.width = 1920,
.height = 1080,
.n_scales = 2,
.scales = { 1.0, 2.0 },
},
{
.width = 1920,
.height = 1200,
.n_scales = 2,
.scales = { 1.0, 2.0 },
},
{
.width = 2650,
.height = 1440,
.n_scales = 3,
.scales = { 1.0, 2.0, 3.0 },
},
{
.width = 2880,
.height = 1800,
.n_scales = 3,
.scales = { 1.0, 2.0, 3.0 },
},
{
.width = 3200,
.height = 1800,
.n_scales = 3,
.scales = { 1.0, 2.0, 3.0 },
},
{
.width = 3200,
.height = 2048,
.n_scales = 4,
.scales = { 1.0, 2.0, 3.0, 4.0 },
},
{
.width = 3840,
.height = 2160,
.n_scales = 4,
.scales = { 1.0, 2.0, 3.0, 4.0 },
},
{
.width = 3840,
.height = 2400,
.n_scales = 4,
.scales = { 1.0, 2.0, 3.0, 4.0 },
},
{
.width = 4096,
.height = 2160,
.n_scales = 4,
.scales = { 1.0, 2.0, 3.0, 4.0 },
},
{
.width = 4096,
.height = 3072,
.n_scales = 4,
.scales = { 1.0, 2.0, 3.0, 4.0 },
},
{
.width = 5120,
.height = 2880,
.n_scales = 4,
.scales = { 1.0, 2.0, 3.0, 4.0 },
},
{
.width = 7680,
.height = 4320,
.n_scales = 4,
.scales = { 1.0, 2.0, 3.0, 4.0 },
},
},
},
},
},
};
MetaMonitorTestSetup *test_setup;
test_setup = create_monitor_test_setup (&test_case.setup,
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor scaling values",
check_monitor_scales (&test_case.expect,
META_MONITOR_SCALES_CONSTRAINT_NO_FRAC));
monitor-unit-tests: Check integer scaling values are matching expectations A per previous commit we can now ensure that all the scaling values when using non-fractional scaling have the value we expect. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1878>
2021-05-28 13:32:42 -04:00
}
monitor-unit-tests: Add tests to verify the computed scaling values Scaling values computation code served us well in the past years but it's quite delicate and it has some issues in edge cases, so add a test that verifies that the computed scaling values for all the most common resolutions (and some that may be common in future) are what we expect to be. This may also serve us in future when we'd define a better algorithm to compute the preferred scale, but this not the day. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1878>
2021-05-28 09:48:46 -04:00
static void
meta_test_monitor_supported_fractional_scales (void)
{
MonitorTestCase test_case = {
.setup = {
.n_modes = 21,
.modes = {
{
.width = 800,
.height = 600,
.refresh_rate = 60.0
},
{
.width = 1024,
.height = 768,
.refresh_rate = 60.0
},
{
.width = 1280,
.height = 720,
.refresh_rate = 60.0,
},
{
.width = 1280,
.height = 800,
.refresh_rate = 60.0,
},
{
.width = 1280,
.height = 1024,
.refresh_rate = 60.0,
},
{
.width = 1366,
.height = 768,
.refresh_rate = 60.0,
},
{
.width = 1440,
.height = 900,
.refresh_rate = 60.0,
},
{
.width = 1400,
.height = 1050,
.refresh_rate = 60.0,
},
{
.width = 1600,
.height = 900,
.refresh_rate = 60.0,
},
{
.width = 1920,
.height = 1080,
.refresh_rate = 60.0,
},
{
.width = 1920,
.height = 1200,
.refresh_rate = 60.0,
},
{
.width = 2650,
.height = 1440,
.refresh_rate = 60.0,
},
{
.width = 2880,
.height = 1800,
.refresh_rate = 60.0,
},
{
.width = 3200,
.height = 1800,
.refresh_rate = 60.0,
},
{
.width = 3200,
.height = 2048,
.refresh_rate = 60.0,
},
{
.width = 3840,
.height = 2160,
.refresh_rate = 60.0,
},
{
.width = 3840,
.height = 2400,
.refresh_rate = 60.0,
},
{
.width = 4096,
.height = 2160,
.refresh_rate = 60.0,
},
{
.width = 4096,
.height = 3072,
.refresh_rate = 60.0,
},
{
.width = 5120,
.height = 2880,
.refresh_rate = 60.0,
},
{
.width = 7680,
.height = 4320,
.refresh_rate = 60.0,
},
},
.outputs = {
{
.crtc = -1,
.modes = { 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16,
17, 18, 19, 20 },
.n_modes = 21,
.preferred_mode = 5,
.possible_crtcs = { 0 },
.n_possible_crtcs = 1,
.width_mm = 222,
.height_mm = 125
}
},
.n_outputs = 1,
.crtcs = {
{
.current_mode = 0
}
},
.n_crtcs = 1
},
.expect = {
.n_monitors = 1,
.monitors = {
{
.n_modes = 21,
.modes = {
{
.width = 800,
.height = 600,
.n_scales = 1,
.scales = { 1.000000 },
},
{
.width = 1024,
.height = 768,
.n_scales = 2,
.scales = { 1.000000, 1.24878049 },
},
{
.width = 1280,
.height = 720,
.n_scales = 3,
.scales = { 1.000000, 1.250000, 1.509434 },
},
{
.width = 1280,
.height = 800,
.n_scales = 3,
.scales = { 1.000000, 1.250000, 1.495327 },
},
{
.width = 1280,
.height = 1024,
.n_scales = 4,
.scales = { 1.000000, 1.248780, 1.497076, 1.753425 },
},
{
.width = 1366,
.height = 768,
.n_scales = 1,
.scales = { 1.000000 },
},
{
.width = 1440,
.height = 900,
.n_scales = 4,
.scales = { 1.000000, 1.250000, 1.500000, 1.747573 },
},
{
.width = 1400,
.height = 1050,
.n_scales = 4,
.scales = { 1.000000, 1.250000, 1.502146, 1.750000 },
},
{
.width = 1600,
.height = 900,
.n_scales = 4,
.scales = { 1.000000, 1.250000, 1.492537, 1.754386 },
},
{
.width = 1920,
.height = 1080,
.n_scales = 6,
.scales = { 1.000000, 1.250000, 1.500000, 1.739130, 2.000000,
2.307692 },
},
{
.width = 1920,
.height = 1200,
.n_scales = 6,
.scales = { 1.000000, 1.250000, 1.500000, 1.751825, 2.000000,
2.242991 },
},
{
.width = 2650,
.height = 1440,
.n_scales = 6,
.scales = { 1.000000, 1.250000, 1.428571, 1.666667, 2.000000,
2.500000
},
},
{
.width = 2880,
.height = 1800,
.n_scales = 11,
.scales = { 1.000000, 1.250000, 1.500000, 1.747573, 2.000000,
2.250000, 2.500000, 2.748092, 3.000000, 3.243243,
3.495146
},
},
{
.width = 3200,
.height = 1800,
.n_scales = 12,
.scales = { 1.000000, 1.250000, 1.503759, 1.754386, 2.000000,
2.247191, 2.500000, 2.739726, 2.985075, 3.225806,
3.508772, 3.773585
},
},
{
.width = 3200,
.height = 2048,
.n_scales = 13,
.scales = { 1.000000, 1.254902, 1.505882, 1.753425, 2.000000,
2.245614, 2.509804, 2.723404, 2.976744, 3.282051,
3.459460, 3.764706, 4.000000,
},
},
{
.width = 3840,
.height = 2160,
.n_scales = 13,
.scales = { 1.000000, 1.250000, 1.500000, 1.751825, 2.000000,
2.201835, 2.500000, 2.758621, 3.000000, 3.243243,
3.478261, 3.750000, 4.000000
},
},
{
.width = 3840,
.height = 2400,
.n_scales = 13,
.scales = { 1.000000, 1.250000, 1.500000, 1.751825, 2.000000,
2.253521, 2.500000, 2.742857, 3.000000, 3.243243,
3.503650, 3.750000, 4.000000
},
},
{
.width = 4096,
.height = 2160,
monitor: Do not overlap when checking for applicable scaling values With some resolutions (such as 4096x2160) we may compute duplicated scale factors because we used a too wide threshold to check for an applicable value. In fact, while when we're at the first and last values it's fine to search applicable values up to SCALE_FACTORS_STEP, on intermediate ones we should stop in the middle of it, or we're end up overlapping the previous scaling value domain. In the said example in fact we were returning 2.666667 both when looking to a scaling value close to 2.75 and 3.00 as the upper bound of 2.75 (3.0) was overlapping with the lower bound of 3.0 (2.75). With the current code, the lower and upper bounds will be instead 2.875. Adapt test to this, and this allows to also ensure that we're always returning a sorted and unique list of scales (which is useful as also g-c-c can ensure that this is true). Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1878>
2021-05-28 13:45:42 -04:00
.n_scales = 8,
monitor-unit-tests: Add tests to verify the computed scaling values Scaling values computation code served us well in the past years but it's quite delicate and it has some issues in edge cases, so add a test that verifies that the computed scaling values for all the most common resolutions (and some that may be common in future) are what we expect to be. This may also serve us in future when we'd define a better algorithm to compute the preferred scale, but this not the day. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1878>
2021-05-28 09:48:46 -04:00
.scales = { 1.000000, 1.333333, 1.454545, 1.777778, 2.000000,
monitor: Do not overlap when checking for applicable scaling values With some resolutions (such as 4096x2160) we may compute duplicated scale factors because we used a too wide threshold to check for an applicable value. In fact, while when we're at the first and last values it's fine to search applicable values up to SCALE_FACTORS_STEP, on intermediate ones we should stop in the middle of it, or we're end up overlapping the previous scaling value domain. In the said example in fact we were returning 2.666667 both when looking to a scaling value close to 2.75 and 3.00 as the upper bound of 2.75 (3.0) was overlapping with the lower bound of 3.0 (2.75). With the current code, the lower and upper bounds will be instead 2.875. Adapt test to this, and this allows to also ensure that we're always returning a sorted and unique list of scales (which is useful as also g-c-c can ensure that this is true). Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1878>
2021-05-28 13:45:42 -04:00
2.666667, 3.200000, 4.000000
monitor-unit-tests: Add tests to verify the computed scaling values Scaling values computation code served us well in the past years but it's quite delicate and it has some issues in edge cases, so add a test that verifies that the computed scaling values for all the most common resolutions (and some that may be common in future) are what we expect to be. This may also serve us in future when we'd define a better algorithm to compute the preferred scale, but this not the day. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1878>
2021-05-28 09:48:46 -04:00
}
},
{
.width = 4096,
.height = 3072,
.n_scales = 13,
.scales = { 1.000000, 1.250305, 1.499268, 1.750427, 2.000000,
2.245614, 2.497561, 2.752688, 3.002933, 3.250794,
3.494880, 3.750916, 4.000000
},
},
{
.width = 5120,
.height = 2880,
.n_scales = 13,
.scales = { 1.000000, 1.250000, 1.495327, 1.748634, 2.000000,
2.253521, 2.500000, 2.758621, 2.990654, 3.265306,
3.516484, 3.764706, 4.000000
},
},
{
.width = 7680,
.height = 4320,
.n_scales = 13,
.scales = { 1.000000, 1.250000, 1.500000, 1.751825, 2.000000,
2.211982, 2.500000, 2.742857, 3.000000, 3.243243,
3.503650, 3.750000, 4.000000
},
},
},
},
},
},
};
MetaMonitorTestSetup *test_setup;
test_setup = create_monitor_test_setup (&test_case.setup,
MONITOR_TEST_FLAG_NO_STORED);
emulate_hotplug (test_setup);
monitor-test-utils: Add debug friendly statements during tests Monitor configuration check tests can be very complex and in case of failures we can't easily catch where a failure happened without entering in debug mode, something that isn't always an option in CI or external builders. So add more debug statements in configuration check functions and use macros to ensure that we print the caller function and location on more complex check functions. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2021-07-22 14:51:34 -04:00
META_TEST_LOG_CALL ("Checking monitor scaling values",
check_monitor_scales (&test_case.expect,
META_MONITOR_SCALES_CONSTRAINT_NONE));
monitor-unit-tests: Add tests to verify the computed scaling values Scaling values computation code served us well in the past years but it's quite delicate and it has some issues in edge cases, so add a test that verifies that the computed scaling values for all the most common resolutions (and some that may be common in future) are what we expect to be. This may also serve us in future when we'd define a better algorithm to compute the preferred scale, but this not the day. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1878>
2021-05-28 09:48:46 -04:00
}
tests/monitor-unit-tests: Clear config history before each test To not let different tests interfere with each other, clear the config history before each run.
2017-08-17 12:53:32 -04:00
static void
test_case_setup (void **fixture,
const void *data)
{
MetaBackend *backend = meta_get_backend ();
MetaMonitorManager *monitor_manager =
meta_backend_get_monitor_manager (backend);
monitor-unit-tests: Always reset CRTC transform ability Changing the test monitor managers ability to rotate CRTCs in one test affected the next test. Avoid leaking such state by resetting it before each test. To continue passing, some tests needed to be updated regarding to still pass. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 04:25:07 -05:00
MetaMonitorManagerTest *monitor_manager_test =
META_MONITOR_MANAGER_TEST (monitor_manager);
tests/monitor-unit-tests: Clear config history before each test To not let different tests interfere with each other, clear the config history before each run.
2017-08-17 12:53:32 -04:00
MetaMonitorConfigManager *config_manager = monitor_manager->config_manager;
monitor-unit-tests: Always reset CRTC transform ability Changing the test monitor managers ability to rotate CRTCs in one test affected the next test. Avoid leaking such state by resetting it before each test. To continue passing, some tests needed to be updated regarding to still pass. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 04:25:07 -05:00
meta_monitor_manager_test_set_handles_transforms (monitor_manager_test,
TRUE);
tests/monitor-unit-tests: Clear config history before each test To not let different tests interfere with each other, clear the config history before each run.
2017-08-17 12:53:32 -04:00
meta_monitor_config_manager_set_current (config_manager, NULL);
meta_monitor_config_manager_clear_history (config_manager);
}
tests/monitor-unit-tests: Use special purpose add test helper Will later be used to set a setup function.
2017-08-17 12:52:06 -04:00
static void
add_monitor_test (const char *test_path,
GTestFunc test_func)
{
g_test_add (test_path, gpointer, NULL,
tests/monitor-unit-tests: Clear config history before each test To not let different tests interfere with each other, clear the config history before each run.
2017-08-17 12:53:32 -04:00
test_case_setup,
tests/monitor-unit-tests: Use special purpose add test helper Will later be used to set a setup function.
2017-08-17 12:52:06 -04:00
(void (* ) (void **, const void *)) test_func,
NULL);
}
tests/monitor-unit-tests: Set initial state during backend construction This way we can construct CRTCs and Outputs and associated them with the fake GPUs at construction. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1287
2020-02-25 04:18:22 -05:00
static MetaMonitorTestSetup *
create_initial_test_setup (void)
{
return create_monitor_test_setup (&initial_test_case.setup,
MONITOR_TEST_FLAG_NO_STORED);
}
tests: Add basic monitor configuration tests The added test checks that two monitors are lied out on a row next to each other. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-05 05:40:44 -05:00
void
init_monitor_tests (void)
{
tests/monitor-unit-tests: Set initial state during backend construction This way we can construct CRTCs and Outputs and associated them with the fake GPUs at construction. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1287
2020-02-25 04:18:22 -05:00
meta_monitor_manager_test_init_test_setup (create_initial_test_setup);
tests: Make monitor unit tests create initial config This way we have both the test setup and testing in the same file. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-05 08:28:22 -05:00
monitor-unit-tests: Add tests to verify config manager history Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2021-07-27 12:01:47 -04:00
add_monitor_test ("/backends/monitor/config-store/set_current-on-empty",
meta_test_monitor_config_store_set_current_on_empty);
monitor-manager: Add config relationships and use it for orientation events When we get an orientation event we don't care about keeping track of the configuration changes, but actually we can consider the new configuration just a variant of the previous one, adapted to floating device hardware events, so we only want to apply it if possible, but we don't want to keep a record of it for reverting capabilities. Doing that would in fact, break the ability of reverting back to an actual temporary or persistent configuration. For example when device orientation events happen while we're waiting for an user resolution change confirmation, we would save our new rotated configuration in the history, making then impossible to revert back to the original persistent one. So in such case, don't keep track of those configurations in the history, but only keep track of the last one as current, checking whether the new current is child or sibling of the previously one. Fixes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1221 Related to: https://gitlab.gnome.org/GNOME/mutter/-/issues/646 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-01 09:53:55 -04:00
add_monitor_test ("/backends/monitor/config-store/set_current-with-parent-on-empty",
meta_test_monitor_config_store_set_current_with_parent_on_empty);
monitor-unit-tests: Add tests to verify config manager history Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2021-07-27 12:01:47 -04:00
add_monitor_test ("/backends/monitor/config-store/set_current",
meta_test_monitor_config_store_set_current);
monitor-manager: Add config relationships and use it for orientation events When we get an orientation event we don't care about keeping track of the configuration changes, but actually we can consider the new configuration just a variant of the previous one, adapted to floating device hardware events, so we only want to apply it if possible, but we don't want to keep a record of it for reverting capabilities. Doing that would in fact, break the ability of reverting back to an actual temporary or persistent configuration. For example when device orientation events happen while we're waiting for an user resolution change confirmation, we would save our new rotated configuration in the history, making then impossible to revert back to the original persistent one. So in such case, don't keep track of those configurations in the history, but only keep track of the last one as current, checking whether the new current is child or sibling of the previously one. Fixes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1221 Related to: https://gitlab.gnome.org/GNOME/mutter/-/issues/646 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-01 09:53:55 -04:00
add_monitor_test ("/backends/monitor/config-store/set_current-with-parent",
meta_test_monitor_config_store_set_current_with_parent);
monitor-unit-tests: Add tests to verify config manager history Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2021-07-27 12:01:47 -04:00
add_monitor_test ("/backends/monitor/config-store/set_current-max-size",
meta_test_monitor_config_store_set_current_max_size);
add_monitor_test ("/backends/monitor/config-store/set_current-null",
meta_test_monitor_config_store_set_current_null);
tests/monitor-unit-tests: Use special purpose add test helper Will later be used to set a setup function.
2017-08-17 12:52:06 -04:00
add_monitor_test ("/backends/monitor/initial-linear-config",
meta_test_monitor_initial_linear_config);
add_monitor_test ("/backends/monitor/one-disconnected-linear-config",
meta_test_monitor_one_disconnected_linear_config);
add_monitor_test ("/backends/monitor/one-off-linear-config",
meta_test_monitor_one_off_linear_config);
add_monitor_test ("/backends/monitor/preferred-linear-config",
meta_test_monitor_preferred_linear_config);
add_monitor_test ("/backends/monitor/tiled-linear-config",
meta_test_monitor_tiled_linear_config);
add_monitor_test ("/backends/monitor/tiled-non-preferred-linear-config",
meta_test_monitor_tiled_non_preferred_linear_config);
add_monitor_test ("/backends/monitor/tiled-non-main-origin-linear-config",
meta_test_monitor_tiled_non_main_origin_linear_config);
add_monitor_test ("/backends/monitor/hidpi-linear-config",
meta_test_monitor_hidpi_linear_config);
add_monitor_test ("/backends/monitor/suggested-config",
meta_test_monitor_suggested_config);
monitor-unit-tests: Add test for overlapping monitor config Verify that when we've monitors with overlapping preferred configuration, we fallback to the default linear configuration. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2019-04-03 12:56:45 -04:00
add_monitor_test ("/backends/monitor/suggested-config-overlapping",
meta_test_monitor_suggested_config_overlapping);
monitor-unit-tests: Check suggested configuration has adjacent outputs Verify that the suggested monitor configuration contains only adjacent monitors, and that if this is not the case we fallback to the linear configuration. This can happen in case of multi-DPI setup, so add a test checking this too. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/522>
2019-04-03 13:02:42 -04:00
add_monitor_test ("/backends/monitor/suggested-config-not-adjacent",
meta_test_monitor_suggested_config_not_adjacent);
add_monitor_test ("/backends/monitor/suggested-config-multi-dpi",
meta_test_monitor_suggested_config_multi_dpi);
tests/monitor-unit-tests: Use special purpose add test helper Will later be used to set a setup function.
2017-08-17 12:52:06 -04:00
add_monitor_test ("/backends/monitor/limited-crtcs",
meta_test_monitor_limited_crtcs);
add_monitor_test ("/backends/monitor/lid-switch-config",
meta_test_monitor_lid_switch_config);
add_monitor_test ("/backends/monitor/lid-opened-config",
meta_test_monitor_lid_opened_config);
add_monitor_test ("/backends/monitor/lid-closed-no-external",
meta_test_monitor_lid_closed_no_external);
monitor-unit-tests: Add test for lid closed after hot plug Add a test case that checks that we don't try to revert to a laptop-panel-only configuration after closing the lid after an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-03 04:11:27 -04:00
add_monitor_test ("/backends/monitor/lid-closed-with-hotplugged-external",
meta_test_monitor_lid_closed_with_hotplugged_external);
monitor-unit-tests: Ensure configuration is preserved in laptop with closed lid https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1200
2020-04-16 04:58:43 -04:00
add_monitor_test ("/backends/monitor/lid-scaled-closed-opened",
meta_test_monitor_lid_scaled_closed_opened);
tests/monitor-unit-tests: Use special purpose add test helper Will later be used to set a setup function.
2017-08-17 12:52:06 -04:00
add_monitor_test ("/backends/monitor/no-outputs",
meta_test_monitor_no_outputs);
add_monitor_test ("/backends/monitor/underscanning-config",
meta_test_monitor_underscanning_config);
monitor-unit-tests: Check non-first preferred modes Check that if there are multiple modes with the same ID (resolution, refresh rate and handled flags) we correctly add the preferred mode to the list of monitor modes. https://bugzilla.gnome.org/show_bug.cgi?id=789153
2017-10-18 11:24:36 -04:00
add_monitor_test ("/backends/monitor/preferred-non-first-mode",
meta_test_monitor_preferred_non_first_mode);
monitor-unit-tests: Add non upright panel test https://bugzilla.gnome.org/show_bug.cgi?id=782294
2017-10-26 05:50:10 -04:00
add_monitor_test ("/backends/monitor/non-upright-panel",
meta_test_monitor_non_upright_panel);
monitor-config-manager: Handle multiple builtin panels gracefully While multiple built-in panels isn't actually supported in any meaningful manner, if we would ever end up with such a situation, e.g. due to kernel bugs[0], we shouldn't crash when trying to set an 'external only' without any external monitors. While we could handle this with more degraded functionality (e.g. don't support the 'switch' method of monitor configuration at all), handle it by simply not trying to switch to external-only when there are no, according to the kernel, external monitors available. This would e.g. still allow betwene 'mirror-all', and 'linear' switches. The crash itself was disguised as an arbitrary X11 BadValue error, due to mutter trying to resize the root window to 0x0, as the monitor configuration that was applied consisted of zero logical monitors, thus was effectively empty. [0] https://bugzilla.redhat.com/show_bug.cgi?id=1896904 Related: https://bugzilla.redhat.com/show_bug.cgi?id=1899260 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1607>
2020-11-27 03:03:38 -05:00
add_monitor_test ("/backends/monitor/switch-external-without-external",
meta_test_monitor_switch_external_without_external);
tests/monitor-unit-tests: Use special purpose add test helper Will later be used to set a setup function.
2017-08-17 12:52:06 -04:00
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
add_monitor_test ("/backends/monitor/orientation/is-managed",
meta_test_monitor_orientation_is_managed);
add_monitor_test ("/backends/monitor/orientation/initial-rotated",
meta_test_monitor_orientation_initial_rotated);
add_monitor_test ("/backends/monitor/orientation/initial-rotated-no-touch",
meta_test_monitor_orientation_initial_rotated_no_touch_mode);
add_monitor_test ("/backends/monitor/orientation/initial-stored-rotated",
meta_test_monitor_orientation_initial_stored_rotated);
add_monitor_test ("/backends/monitor/orientation/initial-stored-rotated-no-touch",
meta_test_monitor_orientation_initial_stored_rotated_no_touch);
add_monitor_test ("/backends/monitor/orientation/changes",
meta_test_monitor_orientation_changes);
monitor-unit-tests: Check orientation changes with transformed panels Ensure that orientation changes still work as expected when using a panel that has some native transformation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2090>
2021-11-24 06:14:44 -05:00
add_monitor_test ("/backends/monitor/orientation/changes-transformed-panel",
meta_test_monitor_orientation_changes_for_transformed_panel);
monitor-unit-tests: Add tests with dynamic orientation changes Verify monitors disposition when we have rotation changes coming from MetaOrientationManager, using our mock dbus implementation. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1233>
2020-05-04 16:47:34 -04:00
add_monitor_test ("/backends/monitor/orientation/changes-with-hotplugging",
meta_test_monitor_orientation_changes_with_hotplugging);
tests/monitor-unit-tests: Use special purpose add test helper Will later be used to set a setup function.
2017-08-17 12:52:06 -04:00
add_monitor_test ("/backends/monitor/custom/vertical-config",
meta_test_monitor_custom_vertical_config);
add_monitor_test ("/backends/monitor/custom/primary-config",
meta_test_monitor_custom_primary_config);
add_monitor_test ("/backends/monitor/custom/underscanning-config",
meta_test_monitor_custom_underscanning_config);
add_monitor_test ("/backends/monitor/custom/scale-config",
meta_test_monitor_custom_scale_config);
add_monitor_test ("/backends/monitor/custom/fractional-scale-config",
meta_test_monitor_custom_fractional_scale_config);
add_monitor_test ("/backends/monitor/custom/high-precision-fractional-scale-config",
meta_test_monitor_custom_high_precision_fractional_scale_config);
add_monitor_test ("/backends/monitor/custom/tiled-config",
meta_test_monitor_custom_tiled_config);
add_monitor_test ("/backends/monitor/custom/tiled-custom-resolution-config",
meta_test_monitor_custom_tiled_custom_resolution_config);
add_monitor_test ("/backends/monitor/custom/tiled-non-preferred-config",
meta_test_monitor_custom_tiled_non_preferred_config);
add_monitor_test ("/backends/monitor/custom/mirrored-config",
meta_test_monitor_custom_mirrored_config);
add_monitor_test ("/backends/monitor/custom/first-rotated-config",
meta_test_monitor_custom_first_rotated_config);
add_monitor_test ("/backends/monitor/custom/second-rotated-config",
meta_test_monitor_custom_second_rotated_config);
add_monitor_test ("/backends/monitor/custom/second-rotated-tiled-config",
meta_test_monitor_custom_second_rotated_tiled_config);
tests/monitor-unit-tests: Test non-hw-transform rotated tiled monitors Should affect the assigned transform, but not the layout, as that is the layout on the stage, not the coordinates in any buffer. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1199
2020-04-14 04:41:37 -04:00
add_monitor_test ("/backends/monitor/custom/second-rotated-nonnative-tiled-config",
meta_test_monitor_custom_second_rotated_nonnative_tiled_config);
tests/monitor-unit-tests: Use special purpose add test helper Will later be used to set a setup function.
2017-08-17 12:52:06 -04:00
add_monitor_test ("/backends/monitor/custom/second-rotated-nonnative-config",
meta_test_monitor_custom_second_rotated_nonnative_config);
add_monitor_test ("/backends/monitor/custom/interlaced-config",
meta_test_monitor_custom_interlaced_config);
monitor-unit-tests: Test configs with explicitly disabled monitors Check that configurations where monitors are disabled are properly used. Also test that old configurations with explicitly disabled outputs are migrated properly. https://bugzilla.gnome.org/show_bug.cgi?id=787629
2017-09-28 11:57:50 -04:00
add_monitor_test ("/backends/monitor/custom/oneoff-config",
meta_test_monitor_custom_oneoff);
monitor-unit-tests: Check config loading on lid switches Check that we apply the correct stored configuration when the lid is opend and closed while an external monitor is connected. https://bugzilla.gnome.org/show_bug.cgi?id=788915
2017-11-09 04:27:23 -05:00
add_monitor_test ("/backends/monitor/custom/lid-switch-config",
meta_test_monitor_custom_lid_switch_config);
tests/monitor-unit-tests: Use special purpose add test helper Will later be used to set a setup function.
2017-08-17 12:52:06 -04:00
add_monitor_test ("/backends/monitor/migrated/rotated",
meta_test_monitor_migrated_rotated);
monitor-tests: Test config migration with refresh rate wiggle room Check that we finish configurations within range, and discard the ones out of range. https://bugzilla.gnome.org/show_bug.cgi?id=787668
2017-09-25 17:59:40 -04:00
add_monitor_test ("/backends/monitor/migrated/wiggle",
meta_test_monitor_migrated_wiggle);
add_monitor_test ("/backends/monitor/migrated/wiggle-discard",
meta_test_monitor_migrated_wiggle_discard);
tests/monitor-unit-tests: Add window tiling hot plug test This test that we handle hot plugs correctly together with tiled windows. https://gitlab.gnome.org/GNOME/mutter/merge_requests/912
2019-11-01 08:38:25 -04:00
add_monitor_test ("/backends/monitor/wm/tiling",
meta_test_monitor_wm_tiling);
monitor-unit-tests: Add tests to verify the computed scaling values Scaling values computation code served us well in the past years but it's quite delicate and it has some issues in edge cases, so add a test that verifies that the computed scaling values for all the most common resolutions (and some that may be common in future) are what we expect to be. This may also serve us in future when we'd define a better algorithm to compute the preferred scale, but this not the day. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1878>
2021-05-28 09:48:46 -04:00
monitor-unit-tests: Check integer scaling values are matching expectations A per previous commit we can now ensure that all the scaling values when using non-fractional scaling have the value we expect. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1878>
2021-05-28 13:32:42 -04:00
add_monitor_test ("/backends/monitor/suppported_scales/integer",
meta_test_monitor_supported_integer_scales);
monitor-unit-tests: Add tests to verify the computed scaling values Scaling values computation code served us well in the past years but it's quite delicate and it has some issues in edge cases, so add a test that verifies that the computed scaling values for all the most common resolutions (and some that may be common in future) are what we expect to be. This may also serve us in future when we'd define a better algorithm to compute the preferred scale, but this not the day. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1878>
2021-05-28 09:48:46 -04:00
add_monitor_test ("/backends/monitor/suppported_scales/fractional",
meta_test_monitor_supported_fractional_scales);
tests: Add basic monitor configuration tests The added test checks that two monitors are lied out on a row next to each other. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-05 05:40:44 -05:00
}
tests/monitor-unit-tests: Run a client while testing Run a client while testing and check that it's alive when checking each monitor configuration. https://bugzilla.gnome.org/show_bug.cgi?id=730551
2017-08-18 02:37:53 -04:00
void
tests: Move 'wait-for-X11-display' helper to MetaContextTest Gets rid of a un-prefixed helper function relying on a global singleton. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-11 03:35:04 -04:00
pre_run_monitor_tests (MetaContext *context)
tests/monitor-unit-tests: Run a client while testing Run a client while testing and check that it's alive when checking each monitor configuration. https://bugzilla.gnome.org/show_bug.cgi?id=730551
2017-08-18 02:37:53 -04:00
{
tests: Move 'wait-for-X11-display' helper to MetaContextTest Gets rid of a un-prefixed helper function relying on a global singleton. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1861>
2021-05-11 03:35:04 -04:00
create_monitor_test_clients (context);
tests/monitor-unit-tests: Run a client while testing Run a client while testing and check that it's alive when checking each monitor configuration. https://bugzilla.gnome.org/show_bug.cgi?id=730551
2017-08-18 02:37:53 -04:00
}
void
finish_monitor_tests (void)
{
monitor-unit-tests: Also run a X11 client while testing We already ran a Wayland client to test various Wayland paths. What was missing to also run a X11 client was to hook in the X11 async waiter wires, so do that and run both types of clients. https://bugzilla.gnome.org/show_bug.cgi?id=790207
2018-02-06 02:39:06 -05:00
destroy_monitor_test_clients ();
tests/monitor-unit-tests: Run a client while testing Run a client while testing and check that it's alive when checking each monitor configuration. https://bugzilla.gnome.org/show_bug.cgi?id=730551
2017-08-18 02:37:53 -04:00
}
Reference in New Issue Copy Permalink