2019-07-03 07:43:25 -04:00
|
|
|
clutter_test_utils = files (
|
|
|
|
|
'clutter-test-utils.c',
|
|
|
|
|
'clutter-test-utils.h',
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
if have_clutter_tests
|
|
|
|
|
subdir('clutter')
|
|
|
|
|
endif
|
2019-07-03 05:51:45 -04:00
|
|
|
|
Add meson build support
This commit adds meson build support to mutter. It takes a step away
from the three separate code bases with three different autotools setups
into a single meson build system. There are still places that can be
unified better, for example by removing various "config.h" style files
from cogl and clutter, centralizing debug C flags and other configurable
macros, and similar artifacts that are there only because they were once
separate code bases.
There are some differences between the autotools setup and the new
meson. Here are a few:
The meson setup doesn't generate wrapper scripts for various cogl and
clutter test cases. What these tests did was more or less generate a
tiny script that called an executable with a test name as the argument.
To run particular tests, just run the test executable with the name of
the test as the argument.
The meson setup doesn't install test files anymore. The autotools test
suite was designed towards working with installed tests, but it didn't
really still, and now with meson, it doesn't install anything at all,
but instead makes sure that everything runs with the uninstalled input
files, binaries and libraries when running the test suite. Installable
tests may come later.
Tests from cogl, clutter and mutter are run on 'meson test'. In
autotools, only cogl and clutter tests were run on 'make check'.
2018-05-22 09:55:35 -04:00
|
|
|
tests_includepath = mutter_includes
|
|
|
|
|
tests_c_args = mutter_c_args
|
|
|
|
|
|
|
|
|
|
tests_deps = [
|
|
|
|
|
mutter_deps,
|
2018-11-06 14:50:24 -05:00
|
|
|
libmutter_dep,
|
Add meson build support
This commit adds meson build support to mutter. It takes a step away
from the three separate code bases with three different autotools setups
into a single meson build system. There are still places that can be
unified better, for example by removing various "config.h" style files
from cogl and clutter, centralizing debug C flags and other configurable
macros, and similar artifacts that are there only because they were once
separate code bases.
There are some differences between the autotools setup and the new
meson. Here are a few:
The meson setup doesn't generate wrapper scripts for various cogl and
clutter test cases. What these tests did was more or less generate a
tiny script that called an executable with a test name as the argument.
To run particular tests, just run the test executable with the name of
the test as the argument.
The meson setup doesn't install test files anymore. The autotools test
suite was designed towards working with installed tests, but it didn't
really still, and now with meson, it doesn't install anything at all,
but instead makes sure that everything runs with the uninstalled input
files, binaries and libraries when running the test suite. Installable
tests may come later.
Tests from cogl, clutter and mutter are run on 'meson test'. In
autotools, only cogl and clutter tests were run on 'make check'.
2018-05-22 09:55:35 -04:00
|
|
|
libmutter_cogl_dep,
|
|
|
|
|
libmutter_clutter_dep,
|
|
|
|
|
]
|
|
|
|
|
|
2018-12-17 10:26:07 -05:00
|
|
|
if have_installed_tests
|
|
|
|
|
stacking_files_datadir = join_paths(pkgdatadir, 'tests')
|
|
|
|
|
|
|
|
|
|
installed_tests_cdata = configuration_data()
|
|
|
|
|
installed_tests_cdata.set('libexecdir', libexecdir)
|
|
|
|
|
installed_tests_cdata.set('apiversion', libmutter_api_version)
|
|
|
|
|
|
|
|
|
|
configure_file(
|
|
|
|
|
input: 'mutter-all.test.in',
|
|
|
|
|
output: 'mutter-all.test',
|
|
|
|
|
configuration: installed_tests_cdata,
|
|
|
|
|
install: true,
|
|
|
|
|
install_dir: mutter_installed_tests_datadir,
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
install_subdir('stacking', install_dir: stacking_files_datadir)
|
|
|
|
|
endif
|
|
|
|
|
|
Add meson build support
This commit adds meson build support to mutter. It takes a step away
from the three separate code bases with three different autotools setups
into a single meson build system. There are still places that can be
unified better, for example by removing various "config.h" style files
from cogl and clutter, centralizing debug C flags and other configurable
macros, and similar artifacts that are there only because they were once
separate code bases.
There are some differences between the autotools setup and the new
meson. Here are a few:
The meson setup doesn't generate wrapper scripts for various cogl and
clutter test cases. What these tests did was more or less generate a
tiny script that called an executable with a test name as the argument.
To run particular tests, just run the test executable with the name of
the test as the argument.
The meson setup doesn't install test files anymore. The autotools test
suite was designed towards working with installed tests, but it didn't
really still, and now with meson, it doesn't install anything at all,
but instead makes sure that everything runs with the uninstalled input
files, binaries and libraries when running the test suite. Installable
tests may come later.
Tests from cogl, clutter and mutter are run on 'meson test'. In
autotools, only cogl and clutter tests were run on 'make check'.
2018-05-22 09:55:35 -04:00
|
|
|
test_env = environment()
|
2019-04-04 22:35:44 -04:00
|
|
|
test_env.set('G_TEST_SRCDIR', join_paths(meson.source_root(), 'src'))
|
|
|
|
|
test_env.set('G_TEST_BUILDDIR', meson.build_root())
|
Add meson build support
This commit adds meson build support to mutter. It takes a step away
from the three separate code bases with three different autotools setups
into a single meson build system. There are still places that can be
unified better, for example by removing various "config.h" style files
from cogl and clutter, centralizing debug C flags and other configurable
macros, and similar artifacts that are there only because they were once
separate code bases.
There are some differences between the autotools setup and the new
meson. Here are a few:
The meson setup doesn't generate wrapper scripts for various cogl and
clutter test cases. What these tests did was more or less generate a
tiny script that called an executable with a test name as the argument.
To run particular tests, just run the test executable with the name of
the test as the argument.
The meson setup doesn't install test files anymore. The autotools test
suite was designed towards working with installed tests, but it didn't
really still, and now with meson, it doesn't install anything at all,
but instead makes sure that everything runs with the uninstalled input
files, binaries and libraries when running the test suite. Installable
tests may come later.
Tests from cogl, clutter and mutter are run on 'meson test'. In
autotools, only cogl and clutter tests were run on 'make check'.
2018-05-22 09:55:35 -04:00
|
|
|
test_env.set('MUTTER_TEST_PLUGIN_PATH', '@0@'.format(default_plugin.full_path()))
|
|
|
|
|
|
|
|
|
|
test_client = executable('mutter-test-client',
|
|
|
|
|
sources: ['test-client.c'],
|
|
|
|
|
include_directories: tests_includepath,
|
|
|
|
|
c_args: tests_c_args,
|
|
|
|
|
dependencies: [
|
|
|
|
|
gtk3_dep,
|
|
|
|
|
gio_unix_dep,
|
2018-11-12 22:04:22 -05:00
|
|
|
x11_dep,
|
Add meson build support
This commit adds meson build support to mutter. It takes a step away
from the three separate code bases with three different autotools setups
into a single meson build system. There are still places that can be
unified better, for example by removing various "config.h" style files
from cogl and clutter, centralizing debug C flags and other configurable
macros, and similar artifacts that are there only because they were once
separate code bases.
There are some differences between the autotools setup and the new
meson. Here are a few:
The meson setup doesn't generate wrapper scripts for various cogl and
clutter test cases. What these tests did was more or less generate a
tiny script that called an executable with a test name as the argument.
To run particular tests, just run the test executable with the name of
the test as the argument.
The meson setup doesn't install test files anymore. The autotools test
suite was designed towards working with installed tests, but it didn't
really still, and now with meson, it doesn't install anything at all,
but instead makes sure that everything runs with the uninstalled input
files, binaries and libraries when running the test suite. Installable
tests may come later.
Tests from cogl, clutter and mutter are run on 'meson test'. In
autotools, only cogl and clutter tests were run on 'make check'.
2018-05-22 09:55:35 -04:00
|
|
|
xext_dep,
|
|
|
|
|
],
|
2018-12-17 10:26:07 -05:00
|
|
|
install: have_installed_tests,
|
|
|
|
|
install_dir: mutter_installed_tests_libexecdir,
|
Add meson build support
This commit adds meson build support to mutter. It takes a step away
from the three separate code bases with three different autotools setups
into a single meson build system. There are still places that can be
unified better, for example by removing various "config.h" style files
from cogl and clutter, centralizing debug C flags and other configurable
macros, and similar artifacts that are there only because they were once
separate code bases.
There are some differences between the autotools setup and the new
meson. Here are a few:
The meson setup doesn't generate wrapper scripts for various cogl and
clutter test cases. What these tests did was more or less generate a
tiny script that called an executable with a test name as the argument.
To run particular tests, just run the test executable with the name of
the test as the argument.
The meson setup doesn't install test files anymore. The autotools test
suite was designed towards working with installed tests, but it didn't
really still, and now with meson, it doesn't install anything at all,
but instead makes sure that everything runs with the uninstalled input
files, binaries and libraries when running the test suite. Installable
tests may come later.
Tests from cogl, clutter and mutter are run on 'meson test'. In
autotools, only cogl and clutter tests were run on 'make check'.
2018-05-22 09:55:35 -04:00
|
|
|
)
|
|
|
|
|
|
|
|
|
|
test_runner = executable('mutter-test-runner',
|
|
|
|
|
sources: [
|
|
|
|
|
'test-utils.c',
|
|
|
|
|
'test-utils.h',
|
|
|
|
|
'test-runner.c',
|
|
|
|
|
],
|
|
|
|
|
include_directories: tests_includepath,
|
|
|
|
|
c_args: tests_c_args,
|
|
|
|
|
dependencies: [tests_deps],
|
2018-12-17 10:26:07 -05:00
|
|
|
install: have_installed_tests,
|
|
|
|
|
install_dir: mutter_installed_tests_libexecdir,
|
Add meson build support
This commit adds meson build support to mutter. It takes a step away
from the three separate code bases with three different autotools setups
into a single meson build system. There are still places that can be
unified better, for example by removing various "config.h" style files
from cogl and clutter, centralizing debug C flags and other configurable
macros, and similar artifacts that are there only because they were once
separate code bases.
There are some differences between the autotools setup and the new
meson. Here are a few:
The meson setup doesn't generate wrapper scripts for various cogl and
clutter test cases. What these tests did was more or less generate a
tiny script that called an executable with a test name as the argument.
To run particular tests, just run the test executable with the name of
the test as the argument.
The meson setup doesn't install test files anymore. The autotools test
suite was designed towards working with installed tests, but it didn't
really still, and now with meson, it doesn't install anything at all,
but instead makes sure that everything runs with the uninstalled input
files, binaries and libraries when running the test suite. Installable
tests may come later.
Tests from cogl, clutter and mutter are run on 'meson test'. In
autotools, only cogl and clutter tests were run on 'make check'.
2018-05-22 09:55:35 -04:00
|
|
|
)
|
|
|
|
|
|
|
|
|
|
unit_tests = executable('mutter-test-unit-tests',
|
|
|
|
|
sources: [
|
|
|
|
|
'test-utils.c',
|
|
|
|
|
'test-utils.h',
|
|
|
|
|
'unit-tests.c',
|
|
|
|
|
'boxes-tests.c',
|
|
|
|
|
'boxes-tests.h',
|
|
|
|
|
'meta-backend-test.c',
|
|
|
|
|
'meta-backend-test.h',
|
2019-01-11 09:35:42 -05:00
|
|
|
'meta-gpu-test.c',
|
|
|
|
|
'meta-gpu-test.h',
|
Add meson build support
This commit adds meson build support to mutter. It takes a step away
from the three separate code bases with three different autotools setups
into a single meson build system. There are still places that can be
unified better, for example by removing various "config.h" style files
from cogl and clutter, centralizing debug C flags and other configurable
macros, and similar artifacts that are there only because they were once
separate code bases.
There are some differences between the autotools setup and the new
meson. Here are a few:
The meson setup doesn't generate wrapper scripts for various cogl and
clutter test cases. What these tests did was more or less generate a
tiny script that called an executable with a test name as the argument.
To run particular tests, just run the test executable with the name of
the test as the argument.
The meson setup doesn't install test files anymore. The autotools test
suite was designed towards working with installed tests, but it didn't
really still, and now with meson, it doesn't install anything at all,
but instead makes sure that everything runs with the uninstalled input
files, binaries and libraries when running the test suite. Installable
tests may come later.
Tests from cogl, clutter and mutter are run on 'meson test'. In
autotools, only cogl and clutter tests were run on 'make check'.
2018-05-22 09:55:35 -04:00
|
|
|
'meta-monitor-manager-test.c',
|
|
|
|
|
'meta-monitor-manager-test.h',
|
|
|
|
|
'monitor-config-migration-unit-tests.c',
|
|
|
|
|
'monitor-config-migration-unit-tests.h',
|
|
|
|
|
'monitor-store-unit-tests.c',
|
|
|
|
|
'monitor-store-unit-tests.h',
|
|
|
|
|
'monitor-test-utils.c',
|
|
|
|
|
'monitor-test-utils.h',
|
|
|
|
|
'monitor-unit-tests.c',
|
|
|
|
|
'monitor-unit-tests.h',
|
|
|
|
|
],
|
|
|
|
|
include_directories: tests_includepath,
|
|
|
|
|
c_args: tests_c_args,
|
|
|
|
|
dependencies: [tests_deps],
|
2018-12-17 10:26:07 -05:00
|
|
|
install: have_installed_tests,
|
|
|
|
|
install_dir: mutter_installed_tests_libexecdir,
|
Add meson build support
This commit adds meson build support to mutter. It takes a step away
from the three separate code bases with three different autotools setups
into a single meson build system. There are still places that can be
unified better, for example by removing various "config.h" style files
from cogl and clutter, centralizing debug C flags and other configurable
macros, and similar artifacts that are there only because they were once
separate code bases.
There are some differences between the autotools setup and the new
meson. Here are a few:
The meson setup doesn't generate wrapper scripts for various cogl and
clutter test cases. What these tests did was more or less generate a
tiny script that called an executable with a test name as the argument.
To run particular tests, just run the test executable with the name of
the test as the argument.
The meson setup doesn't install test files anymore. The autotools test
suite was designed towards working with installed tests, but it didn't
really still, and now with meson, it doesn't install anything at all,
but instead makes sure that everything runs with the uninstalled input
files, binaries and libraries when running the test suite. Installable
tests may come later.
Tests from cogl, clutter and mutter are run on 'meson test'. In
autotools, only cogl and clutter tests were run on 'make check'.
2018-05-22 09:55:35 -04:00
|
|
|
)
|
|
|
|
|
|
|
|
|
|
headless_start_test = executable('mutter-headless-start-test',
|
|
|
|
|
sources: [
|
|
|
|
|
'headless-start-test.c',
|
|
|
|
|
'meta-backend-test.c',
|
|
|
|
|
'meta-backend-test.h',
|
2019-01-11 09:35:42 -05:00
|
|
|
'meta-gpu-test.c',
|
|
|
|
|
'meta-gpu-test.h',
|
Add meson build support
This commit adds meson build support to mutter. It takes a step away
from the three separate code bases with three different autotools setups
into a single meson build system. There are still places that can be
unified better, for example by removing various "config.h" style files
from cogl and clutter, centralizing debug C flags and other configurable
macros, and similar artifacts that are there only because they were once
separate code bases.
There are some differences between the autotools setup and the new
meson. Here are a few:
The meson setup doesn't generate wrapper scripts for various cogl and
clutter test cases. What these tests did was more or less generate a
tiny script that called an executable with a test name as the argument.
To run particular tests, just run the test executable with the name of
the test as the argument.
The meson setup doesn't install test files anymore. The autotools test
suite was designed towards working with installed tests, but it didn't
really still, and now with meson, it doesn't install anything at all,
but instead makes sure that everything runs with the uninstalled input
files, binaries and libraries when running the test suite. Installable
tests may come later.
Tests from cogl, clutter and mutter are run on 'meson test'. In
autotools, only cogl and clutter tests were run on 'make check'.
2018-05-22 09:55:35 -04:00
|
|
|
'meta-monitor-manager-test.c',
|
|
|
|
|
'meta-monitor-manager-test.h',
|
|
|
|
|
'test-utils.c',
|
|
|
|
|
'test-utils.h',
|
|
|
|
|
],
|
|
|
|
|
include_directories: tests_includepath,
|
|
|
|
|
c_args: tests_c_args,
|
|
|
|
|
dependencies: [tests_deps],
|
2018-12-17 10:26:07 -05:00
|
|
|
install: have_installed_tests,
|
|
|
|
|
install_dir: mutter_installed_tests_libexecdir,
|
Add meson build support
This commit adds meson build support to mutter. It takes a step away
from the three separate code bases with three different autotools setups
into a single meson build system. There are still places that can be
unified better, for example by removing various "config.h" style files
from cogl and clutter, centralizing debug C flags and other configurable
macros, and similar artifacts that are there only because they were once
separate code bases.
There are some differences between the autotools setup and the new
meson. Here are a few:
The meson setup doesn't generate wrapper scripts for various cogl and
clutter test cases. What these tests did was more or less generate a
tiny script that called an executable with a test name as the argument.
To run particular tests, just run the test executable with the name of
the test as the argument.
The meson setup doesn't install test files anymore. The autotools test
suite was designed towards working with installed tests, but it didn't
really still, and now with meson, it doesn't install anything at all,
but instead makes sure that everything runs with the uninstalled input
files, binaries and libraries when running the test suite. Installable
tests may come later.
Tests from cogl, clutter and mutter are run on 'meson test'. In
autotools, only cogl and clutter tests were run on 'make check'.
2018-05-22 09:55:35 -04:00
|
|
|
)
|
|
|
|
|
|
2018-11-13 20:36:35 -05:00
|
|
|
stacking_tests = [
|
|
|
|
|
'basic-x11',
|
|
|
|
|
'basic-wayland',
|
|
|
|
|
'client-side-decorated',
|
|
|
|
|
'closed-transient',
|
2018-11-13 01:48:53 -05:00
|
|
|
'closed-transient-no-input-no-take-focus-parent',
|
|
|
|
|
'closed-transient-no-input-no-take-focus-parents',
|
|
|
|
|
'closed-transient-no-input-parent',
|
2018-11-13 18:08:34 -05:00
|
|
|
'closed-transient-no-input-parent-delayed-focus-default-cancelled',
|
window-x11: Use any focusable window as fallback delayed focus window
As per commit f71151a5 we focus an input window if no take-focus-window accepts
it. This might lead to an infinite loop if there are various focusable but
non-input windows in the stack.
When the current focus window is unmanaging and we're trying to focus a
WM_TAKE_FOCUS window, we intent to give the focus to the first focusable input
window in the stack.
However, if an application (such as the Java ones) only uses non-input
WM_TAKE_FOCUS windows, are not requesting these ones to get the focus. This
might lead to a state where no window is focused, or a wrong one is.
So, instead of only focus the first eventually input window available, try to
request to all the take-focus windows that are in the stack between the
destroyed one and the first input one to acquire the input focus.
Use a queue to keep track of those windows, that is passed around stealing
ownership, while we protect for unmanaged queued windows.
Also, reduce the default timeout value, as the previous one might lead to an
excessive long wait.
Added metatests verifying these situations.
Closes: https://gitlab.gnome.org/GNOME/mutter/issues/660
https://gitlab.gnome.org/GNOME/mutter/merge_requests/669
2019-07-03 06:04:08 -04:00
|
|
|
'closed-transient-no-input-parents',
|
|
|
|
|
'closed-transient-no-input-parents-queued-default-focus-destroyed',
|
|
|
|
|
'closed-transient-only-take-focus-parents',
|
2018-11-13 20:36:35 -05:00
|
|
|
'minimized',
|
|
|
|
|
'mixed-windows',
|
|
|
|
|
'set-parent',
|
|
|
|
|
'override-redirect',
|
2019-10-28 23:22:19 -04:00
|
|
|
'set-override-redirect-parent',
|
2018-11-13 20:36:35 -05:00
|
|
|
'set-parent-exported',
|
|
|
|
|
]
|
Add meson build support
This commit adds meson build support to mutter. It takes a step away
from the three separate code bases with three different autotools setups
into a single meson build system. There are still places that can be
unified better, for example by removing various "config.h" style files
from cogl and clutter, centralizing debug C flags and other configurable
macros, and similar artifacts that are there only because they were once
separate code bases.
There are some differences between the autotools setup and the new
meson. Here are a few:
The meson setup doesn't generate wrapper scripts for various cogl and
clutter test cases. What these tests did was more or less generate a
tiny script that called an executable with a test name as the argument.
To run particular tests, just run the test executable with the name of
the test as the argument.
The meson setup doesn't install test files anymore. The autotools test
suite was designed towards working with installed tests, but it didn't
really still, and now with meson, it doesn't install anything at all,
but instead makes sure that everything runs with the uninstalled input
files, binaries and libraries when running the test suite. Installable
tests may come later.
Tests from cogl, clutter and mutter are run on 'meson test'. In
autotools, only cogl and clutter tests were run on 'make check'.
2018-05-22 09:55:35 -04:00
|
|
|
|
2018-11-13 20:36:35 -05:00
|
|
|
foreach stacking_test: stacking_tests
|
|
|
|
|
test(stacking_test, test_runner,
|
|
|
|
|
suite: ['core', 'mutter/stacking'],
|
|
|
|
|
env: test_env,
|
|
|
|
|
args: [
|
|
|
|
|
files(join_paths('stacking', stacking_test + '.metatest')),
|
|
|
|
|
],
|
|
|
|
|
is_parallel: false,
|
|
|
|
|
timeout: 60,
|
|
|
|
|
)
|
|
|
|
|
endforeach
|
Add meson build support
This commit adds meson build support to mutter. It takes a step away
from the three separate code bases with three different autotools setups
into a single meson build system. There are still places that can be
unified better, for example by removing various "config.h" style files
from cogl and clutter, centralizing debug C flags and other configurable
macros, and similar artifacts that are there only because they were once
separate code bases.
There are some differences between the autotools setup and the new
meson. Here are a few:
The meson setup doesn't generate wrapper scripts for various cogl and
clutter test cases. What these tests did was more or less generate a
tiny script that called an executable with a test name as the argument.
To run particular tests, just run the test executable with the name of
the test as the argument.
The meson setup doesn't install test files anymore. The autotools test
suite was designed towards working with installed tests, but it didn't
really still, and now with meson, it doesn't install anything at all,
but instead makes sure that everything runs with the uninstalled input
files, binaries and libraries when running the test suite. Installable
tests may come later.
Tests from cogl, clutter and mutter are run on 'meson test'. In
autotools, only cogl and clutter tests were run on 'make check'.
2018-05-22 09:55:35 -04:00
|
|
|
|
2018-11-13 20:37:23 -05:00
|
|
|
test('normal', unit_tests,
|
|
|
|
|
suite: ['core', 'mutter/unit'],
|
Add meson build support
This commit adds meson build support to mutter. It takes a step away
from the three separate code bases with three different autotools setups
into a single meson build system. There are still places that can be
unified better, for example by removing various "config.h" style files
from cogl and clutter, centralizing debug C flags and other configurable
macros, and similar artifacts that are there only because they were once
separate code bases.
There are some differences between the autotools setup and the new
meson. Here are a few:
The meson setup doesn't generate wrapper scripts for various cogl and
clutter test cases. What these tests did was more or less generate a
tiny script that called an executable with a test name as the argument.
To run particular tests, just run the test executable with the name of
the test as the argument.
The meson setup doesn't install test files anymore. The autotools test
suite was designed towards working with installed tests, but it didn't
really still, and now with meson, it doesn't install anything at all,
but instead makes sure that everything runs with the uninstalled input
files, binaries and libraries when running the test suite. Installable
tests may come later.
Tests from cogl, clutter and mutter are run on 'meson test'. In
autotools, only cogl and clutter tests were run on 'make check'.
2018-05-22 09:55:35 -04:00
|
|
|
env: test_env,
|
|
|
|
|
is_parallel: false,
|
|
|
|
|
timeout: 60,
|
|
|
|
|
)
|
|
|
|
|
|
2018-11-13 20:37:23 -05:00
|
|
|
test('headless-start', headless_start_test,
|
|
|
|
|
suite: ['core', 'mutter/unit'],
|
Add meson build support
This commit adds meson build support to mutter. It takes a step away
from the three separate code bases with three different autotools setups
into a single meson build system. There are still places that can be
unified better, for example by removing various "config.h" style files
from cogl and clutter, centralizing debug C flags and other configurable
macros, and similar artifacts that are there only because they were once
separate code bases.
There are some differences between the autotools setup and the new
meson. Here are a few:
The meson setup doesn't generate wrapper scripts for various cogl and
clutter test cases. What these tests did was more or less generate a
tiny script that called an executable with a test name as the argument.
To run particular tests, just run the test executable with the name of
the test as the argument.
The meson setup doesn't install test files anymore. The autotools test
suite was designed towards working with installed tests, but it didn't
really still, and now with meson, it doesn't install anything at all,
but instead makes sure that everything runs with the uninstalled input
files, binaries and libraries when running the test suite. Installable
tests may come later.
Tests from cogl, clutter and mutter are run on 'meson test'. In
autotools, only cogl and clutter tests were run on 'make check'.
2018-05-22 09:55:35 -04:00
|
|
|
env: test_env,
|
|
|
|
|
is_parallel: false,
|
|
|
|
|
timeout: 60,
|
|
|
|
|
)
|