mutter/src/tests/stacking.test.in

[Test]
Description=Mutter stacking test: @stacking_test@
# Can't use TestEnvironment for GSETTINGS_BACKEND=memory until there's
# a solution for
# https://gitlab.gnome.org/GNOME/gnome-desktop-testing/-/issues/1,
# and anyway that wouldn't be sufficient to handle XDG_RUNTIME_DIR
Exec=sh -ec 'env GSETTINGS_BACKEND=memory XDG_RUNTIME_DIR="$(mktemp -d -t mutter-@apiversion@-@stacking_test@-XXXXXX)" @libexecdir@/installed-tests/mutter-@apiversion@/mutter-installed-dbus-session.py xvfb-run -a -s "+iglx -noreset" -- @libexecdir@/installed-tests/mutter-@apiversion@/mutter-test-runner @tests_datadir@/stacking/@stacking_test@.metatest'
Type=session
Output=TAP
tests: Break up stacking installed-tests into more, smaller tests Running each stacking test as a separate installed-test is analogous to what was done for build-time tests in c6d1cf4a (!442) and should make it easier to track regressions, by being able to see whether a regression is specific to one .metatest script or applies to more than one. Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2773> 2022-12-18 08:28:40 -05:00			`[Test]`
			`Description=Mutter stacking test: @stacking_test@`
			`# Can't use TestEnvironment for GSETTINGS_BACKEND=memory until there's`
			`# a solution for`
			`# https://gitlab.gnome.org/GNOME/gnome-desktop-testing/-/issues/1,`
			`# and anyway that wouldn't be sufficient to handle XDG_RUNTIME_DIR`
			`Exec=sh -ec 'env GSETTINGS_BACKEND=memory XDG_RUNTIME_DIR="$(mktemp -d -t mutter-@apiversion@-@stacking_test@-XXXXXX)" @libexecdir@/installed-tests/mutter-@apiversion@/mutter-installed-dbus-session.py xvfb-run -a -s "+iglx -noreset" -- @libexecdir@/installed-tests/mutter-@apiversion@/mutter-test-runner @tests_datadir@/stacking/@stacking_test@.metatest'`
			`Type=session`
			`Output=TAP`