AuroraMiddleware/gtk2
1
0
Fork 0
forked from AuroraMiddleware/gtk
Code Issues Pull Requests Projects Releases Wiki Activity
36b4b39619
gtk2/testsuite/a11y/meson.build

156 lines
3.9 KiB
Meson
Raw Normal View History

Fix test environments
2017-10-18 08:55:02 +00:00
testexecdir = join_paths(installed_test_bindir, 'a11y')
testdatadir = join_paths(installed_test_datadir, 'a11y')
tests: Split out the accessibility dump tests Instead of having a single massive test running through the a11y directory, we can split off each individual file into its own unit. Having individual units has several advantages: - units are executed in parallel - it's easier to identify the failing units - logs for failed units are easier to read
2018-04-14 14:59:12 +00:00
a11y_state_tests = [
testsuite: Clean up a11y menu tests We don't need some of the tests anymore, since we just have popovers now.
2020-02-06 22:12:34 +00:00
'about',
tests: Split out the accessibility dump tests Instead of having a single massive test running through the a11y directory, we can split off each individual file into its own unit. Having individual units has several advantages: - units are executed in parallel - it's easier to identify the failing units - logs for failed units are easier to read
2018-04-14 14:59:12 +00:00
'accessible-name',
testsuite: Clean up a11y menu tests We don't need some of the tests anymore, since we just have popovers now.
2020-02-06 22:12:34 +00:00
'actionbar',
'assistant',
Disable the buttons a11y test The test fails because radio buttons are currently broken.
2020-02-10 20:06:56 +00:00
#'buttons',
testsuite: Clean up a11y menu tests We don't need some of the tests anymore, since we just have popovers now.
2020-02-06 22:12:34 +00:00
'calendar',
tests: Split out the accessibility dump tests Instead of having a single massive test running through the a11y directory, we can split off each individual file into its own unit. Having individual units has several advantages: - units are executed in parallel - it's easier to identify the failing units - logs for failed units are easier to read
2018-04-14 14:59:12 +00:00
'colorchooser',
testsuite: Clean up a11y menu tests We don't need some of the tests anymore, since we just have popovers now.
2020-02-06 22:12:34 +00:00
'combos',
'entries',
tests: Split out the accessibility dump tests Instead of having a single massive test running through the a11y directory, we can split off each individual file into its own unit. Having individual units has several advantages: - units are executed in parallel - it's easier to identify the failing units - logs for failed units are easier to read
2018-04-14 14:59:12 +00:00
'expander',
testsuite: Clean up a11y menu tests We don't need some of the tests anymore, since we just have popovers now.
2020-02-06 22:12:34 +00:00
'headerbar',
'hello-world',
'iconview',
'infobar',
tests: Split out the accessibility dump tests Instead of having a single massive test running through the a11y directory, we can split off each individual file into its own unit. Having individual units has several advantages: - units are executed in parallel - it's easier to identify the failing units - logs for failed units are easier to read
2018-04-14 14:59:12 +00:00
'label',
testsuite: Clean up a11y menu tests We don't need some of the tests anymore, since we just have popovers now.
2020-02-06 22:12:34 +00:00
'link',
'listbox',
tests: Split out the accessibility dump tests Instead of having a single massive test running through the a11y directory, we can split off each individual file into its own unit. Having individual units has several advantages: - units are executed in parallel - it's easier to identify the failing units - logs for failed units are easier to read
2018-04-14 14:59:12 +00:00
'lockbutton',
'menubutton',
'menubutton2',
testsuite: Clean up a11y menu tests We don't need some of the tests anymore, since we just have popovers now.
2020-02-06 22:12:34 +00:00
'messagedialog',
'mnemonic',
'notebook',
'paned',
'pickers',
'placeholder-text',
'progress',
'range',
'scale-drawvalue',
'spinner',
'statusbar',
tests: Split out the accessibility dump tests Instead of having a single massive test running through the a11y directory, we can split off each individual file into its own unit. Having individual units has several advantages: - units are executed in parallel - it's easier to identify the failing units - logs for failed units are easier to read
2018-04-14 14:59:12 +00:00
'stack',
testsuite: Clean up a11y menu tests We don't need some of the tests anymore, since we just have popovers now.
2020-02-06 22:12:34 +00:00
'text',
tests: Split out the accessibility dump tests Instead of having a single massive test running through the a11y directory, we can split off each individual file into its own unit. Having individual units has several advantages: - units are executed in parallel - it's easier to identify the failing units - logs for failed units are easier to read
2018-04-14 14:59:12 +00:00
'tooltips',
testsuite: Clean up a11y menu tests We don't need some of the tests anymore, since we just have popovers now.
2020-02-06 22:12:34 +00:00
'tree',
tests: Split out the accessibility dump tests Instead of having a single massive test running through the a11y directory, we can split off each individual file into its own unit. Having individual units has several advantages: - units are executed in parallel - it's easier to identify the failing units - logs for failed units are easier to read
2018-04-14 14:59:12 +00:00
]
a11y_dump_bin = executable('accessibility-dump',
'accessibility-dump.c',
testsuite/a11y: Add common_cflags to build
2020-03-06 17:19:24 +00:00
c_args: common_cflags,
tests: Split out the accessibility dump tests Instead of having a single massive test running through the a11y directory, we can split off each individual file into its own unit. Having individual units has several advantages: - units are executed in parallel - it's easier to identify the failing units - logs for failed units are easier to read
2018-04-14 14:59:12 +00:00
dependencies: libgtk_dep,
testsuite: Install accessibility-dump executable alongside tests The installed-tests want to run this. Signed-off-by: Simon McVittie <smcv@debian.org>
2018-09-14 12:15:09 +00:00
install: get_option('install-tests'),
install_dir: testexecdir,
tests: Split out the accessibility dump tests Instead of having a single massive test running through the a11y directory, we can split off each individual file into its own unit. Having individual units has several advantages: - units are executed in parallel - it's easier to identify the failing units - logs for failed units are easier to read
2018-04-14 14:59:12 +00:00
)
foreach t: a11y_state_tests
ui_path = join_paths(meson.current_source_dir(), t + '.ui')
test (t + ' state',
a11y_dump_bin,
args: [ '--tap', '-k', ui_path ],
testsuite: Tell meson we use TAP This makes meson actually parse the individual test results. Most of the time, it does not make a difference, but one case where it does is when all the individual tests of a binary are skipped, meson will mark the test as skipped.
2020-03-20 13:39:56 +00:00
protocol: 'tap',
tests: Split out the accessibility dump tests Instead of having a single massive test running through the a11y directory, we can split off each individual file into its own unit. Having individual units has several advantages: - units are executed in parallel - it's easier to identify the failing units - logs for failed units are easier to read
2018-04-14 14:59:12 +00:00
env: [
'G_TEST_SRCDIR=@0@'.format(meson.current_source_dir()),
'G_TEST_BUILDDIR=@0@'.format(meson.current_build_dir()),
],
suite: 'a11y',
)
endforeach
build: Port the a11y test suite to Meson Copy the location of the test data and binaries from the autotools build, even though it's not really correct; currently we install the test data under libexecdir, but it should live under datadir, and we should use `G_TEST_DIST` to figure it out. The `state` subdirectory is missing.
2017-04-30 21:14:37 +00:00
a11y_tests = [
'tree-performance',
'text',
'children',
'derive',
'value',
'misc',
'tree-relationships',
'util',
]
meson: Sort input files by name
2016-09-26 10:51:17 +00:00
build: Port the a11y test suite to Meson Copy the location of the test data and binaries from the autotools build, even though it's not really correct; currently we install the test data under libexecdir, but it should live under datadir, and we should use `G_TEST_DIST` to figure it out. The `state` subdirectory is missing.
2017-04-30 21:14:37 +00:00
foreach t: a11y_tests
test_prefix = 'a11y'
meson: Sort input files by name
2016-09-26 10:51:17 +00:00
Reshuffle the a11y tests a bit
2017-10-10 04:16:10 +00:00
test (t,
executable (t, '@0@.c'.format(t),
install: get_option('install-tests'),
install_dir: testexecdir,
build: Port the a11y test suite to Meson Copy the location of the test data and binaries from the autotools build, even though it's not really correct; currently we install the test data under libexecdir, but it should live under datadir, and we should use `G_TEST_DIST` to figure it out. The `state` subdirectory is missing.
2017-04-30 21:14:37 +00:00
dependencies: libgtk_dep),
args: [ '--tap', '-k', ],
testsuite: Tell meson we use TAP This makes meson actually parse the individual test results. Most of the time, it does not make a difference, but one case where it does is when all the individual tests of a binary are skipped, meson will mark the test as skipped.
2020-03-20 13:39:56 +00:00
protocol: 'tap',
tests: Split out the accessibility dump tests Instead of having a single massive test running through the a11y directory, we can split off each individual file into its own unit. Having individual units has several advantages: - units are executed in parallel - it's easier to identify the failing units - logs for failed units are easier to read
2018-04-14 14:59:12 +00:00
timeout: 120,
tests: Centralize our test setup a bit Put all of the constant environment into the toplevel meson.build file, to reduce repetition and copy-paste errors.
2020-05-15 16:57:49 +00:00
env: [
Fix test environments
2017-10-18 08:55:02 +00:00
'G_TEST_SRCDIR=@0@'.format(meson.current_source_dir()),
tests: Make GSETTINGS_SCHEMA_DIR point to the compiled schemas in the build dir With autotools the schemas were compiled into each test suite directory and the tests set GSETTINGS_SCHEMA_DIR to the test build directory. With meson's gnome.compile_schemas() we can not define a target directory so just make sure it is built in the gtk directory and set GSETTINGS_SCHEMA_DIR to the gtk build directory when running the tests. This makes the gtk+:gtk suite pass when no gtk is installed on the system.
2018-02-17 08:48:12 +00:00
'G_TEST_BUILDDIR=@0@'.format(meson.current_build_dir()),
Fix test environments
2017-10-18 08:55:02 +00:00
],
testsuite: cosmetics Put all tests in a suite, and order them in a nicer way. This makes the test output look better.
2017-10-12 00:33:43 +00:00
suite: 'a11y')
build: Port the a11y test suite to Meson Copy the location of the test data and binaries from the autotools build, even though it's not really correct; currently we install the test data under libexecdir, but it should live under datadir, and we should use `G_TEST_DIST` to figure it out. The `state` subdirectory is missing.
2017-04-30 21:14:37 +00:00
endforeach
a11y_installed_tests = [
Test suite cosmetics Reshuffle things a bit more, sort the test files into subdirectories, and shorten their names.
2017-10-18 00:48:16 +00:00
'tests.test',
'children.test',
'tree.test',
'value.test',
'derive.test',
'text.test',
'util.test',
'misc.test',
build: Port the a11y test suite to Meson Copy the location of the test data and binaries from the autotools build, even though it's not really correct; currently we install the test data under libexecdir, but it should live under datadir, and we should use `G_TEST_DIST` to figure it out. The `state` subdirectory is missing.
2017-04-30 21:14:37 +00:00
]
installed_test_data = [
testsuite: Clean up a11y menu tests We don't need some of the tests anymore, since we just have popovers now.
2020-02-06 22:12:34 +00:00
'about.ui', 'about.txt',
'accessible-name.ui', 'accessible-name.txt',
'actionbar.ui', 'actionbar.txt',
'assistant.ui', 'assistant.txt',
'buttons.ui', 'buttons.txt',
'calendar.ui', 'calendar.txt',
'colorchooser.ui', 'colorchooser.txt',
'combos.ui', 'combos.txt',
'entries.ui', 'entries.txt',
'expander.ui', 'expander.txt',
'headerbar.ui', 'headerbar.txt',
'hello-world.ui', 'hello-world.txt',
'iconview.ui', 'iconview.txt',
'infobar.ui', 'infobar.txt',
'label.ui', 'label.txt',
'link.ui', 'link.txt',
'listbox.ui', 'listbox.txt',
'lockbutton.ui', 'lockbutton.txt',
'menubutton.ui', 'menubutton.txt',
'menubutton2.ui', 'menubutton2.txt',
'messagedialog.ui', 'messagedialog.txt',
'mnemonic.ui', 'mnemonic.txt',
'notebook.ui', 'notebook.txt',
'paned.ui', 'paned.txt',
'pickers.ui', 'pickers.txt',
'placeholder-text.ui', 'placeholder-text.txt',
'progress.ui', 'progress.txt',
'range.ui', 'range.txt',
'scale-drawvalue.ui', 'scale-drawvalue.txt',
'spinner.ui', 'spinner.txt',
'stack.ui', 'stack.txt',
'statusbar.ui', 'statusbar.txt',
'text.ui', 'text.txt',
'tooltips.ui', 'tooltips.txt',
'tree.ui', 'tree.txt',
build: Port the a11y test suite to Meson Copy the location of the test data and binaries from the autotools build, even though it's not really correct; currently we install the test data under libexecdir, but it should live under datadir, and we should use `G_TEST_DIST` to figure it out. The `state` subdirectory is missing.
2017-04-30 21:14:37 +00:00
]
Reshuffle the a11y tests a bit
2017-10-10 04:16:10 +00:00
if get_option('install-tests')
test_cdata = configuration_data()
test_cdata.set('libexecdir', gtk_libexecdir)
foreach t: a11y_installed_tests
configure_file(input: '@0@.in'.format(t),
output: t,
configuration: test_cdata,
install: true,
Test suite cosmetics Reshuffle things a bit more, sort the test files into subdirectories, and shorten their names.
2017-10-18 00:48:16 +00:00
install_dir: testdatadir)
Reshuffle the a11y tests a bit
2017-10-10 04:16:10 +00:00
endforeach
install_data(installed_test_data, install_dir: testexecdir)
endif
Reference in New Issue Copy Permalink