2017-11-18 20:32:01 +03:00
# SPDX-License-Identifier: LGPL-2.1+
2019-12-08 13:24:39 +03:00
testdata_dir = testsdir + '/testdata/'
install_subdir ( 'journal-data' ,
install_dir : testdata_dir )
install_subdir ( 'units' ,
install_dir : testdata_dir )
install_subdir ( 'test-execute' ,
install_dir : testdata_dir )
install_subdir ( 'test-path' ,
install_dir : testdata_dir )
install_subdir ( 'test-umount' ,
install_dir : testdata_dir )
2019-12-10 15:04:39 +03:00
install_subdir ( 'test-network-generator-conversion' ,
install_dir : testdata_dir )
2019-12-09 21:19:05 +03:00
install_subdir ( 'testsuite-04.units' ,
install_dir : testdata_dir )
2019-12-09 21:42:57 +03:00
install_subdir ( 'testsuite-06.units' ,
install_dir : testdata_dir )
2019-12-09 22:42:48 +03:00
install_subdir ( 'testsuite-10.units' ,
install_dir : testdata_dir )
2019-12-09 22:53:38 +03:00
install_subdir ( 'testsuite-11.units' ,
install_dir : testdata_dir )
2019-12-10 10:16:40 +03:00
install_subdir ( 'testsuite-16.units' ,
install_dir : testdata_dir )
2019-12-10 11:32:44 +03:00
install_subdir ( 'testsuite-28.units' ,
install_dir : testdata_dir )
2019-12-10 15:45:48 +03:00
install_subdir ( 'testsuite-30.units' ,
install_dir : testdata_dir )
2017-04-14 03:47:20 +03:00
2019-12-10 18:05:48 +03:00
testsuite08_dir = testdata_dir + '/testsuite-08.units'
install_data ( 'testsuite-08.units/-.mount' ,
install_dir : testsuite08_dir )
install_data ( 'testsuite-08.units/systemd-remount-fs.service' ,
install_dir : testsuite08_dir )
meson . add_install_script ( meson_make_symlink ,
'./-.mount' ,
testsuite08_dir + '/root.mount' )
meson . add_install_script ( meson_make_symlink ,
'../-.mount' ,
testsuite08_dir + '/local-fs.target.wants/-.mount' )
2017-10-03 14:12:29 +03:00
if conf . get ( 'ENABLE_RESOLVE' ) == 1
2019-12-08 13:24:39 +03:00
install_subdir ( 'test-resolve' ,
install_dir : testdata_dir )
2017-04-14 03:47:20 +03:00
endif
2019-12-09 23:45:46 +03:00
install_data ( 'create-busybox-container' ,
install_mode : 'rwxr-xr-x' ,
install_dir : testdata_dir )
2019-12-10 15:04:39 +03:00
test_network_generator_conversion_sh = find_program ( 'test-network-generator-conversion.sh' )
2017-07-14 02:21:40 +03:00
############################################################
2017-11-22 14:42:28 +03:00
rule_syntax_check_py = find_program ( 'rule-syntax-check.py' )
2018-09-12 12:08:49 +03:00
if want_tests != 'false'
test ( 'rule-syntax-check' ,
rule_syntax_check_py ,
args : all_rules )
endif
2017-11-22 14:42:28 +03:00
############################################################
2017-10-08 23:14:45 +03:00
if conf . get ( 'HAVE_SYSV_COMPAT' ) == 1
sysv_generator_test_py = find_program ( 'sysv-generator-test.py' )
2018-09-12 12:08:49 +03:00
if want_tests != 'false'
test ( 'sysv-generator-test' ,
sysv_generator_test_py )
endif
2017-10-08 23:14:45 +03:00
endif
2017-09-26 14:39:43 +03:00
############################################################
tests: add a runner for installed tests
We have "installed tests", but don't provide an easy way to run them.
The protocol is very simple: each test must return 0 for success, 77 means
"skipped", anything else is an error. In addition, we want to print test
output only if the test failed.
I wrote this simple script. It is pretty basic, but implements the functions
listed above. Since it is written in python it should be easy to add option
parsing (like running only specific tests, or running unsafe tests, etc.)
I looked at the following alternatives:
- Ubuntu root-unittests: this works, but just dumps all output to the terminal,
has no coloring.
- @ssahani's test runner [2]
It uses the unittest library and the test suite was implented as a class, and
doesn't implement any of the functions listed above.
- cram [3,4]
cram runs our tests, but does not understand the "ignore the output" part,
has not support for our magic skip code (it uses hardcoded 80 instead),
and seems dead upstream.
- meson test
Here the idea would be to provide an almost-empty meson.build file under
/usr/lib/systemd/tests/ that would just define all the tests. This would
allow us to reuse the test runner we use normally. Unfortunately meson requires
a build directory and configuration to be done before running tests. This
would be possible, but seems a lot of effort to just run a few binaries.
[1] https://salsa.debian.org/systemd-team/systemd/blob/242c96addb06480ec9cd75248a5660f37a17b4b9/debian/tests/root-unittests
[2] https://github.com/systemd/systemd-fedora-ci/blob/master/upstream/systemd-upstream-tests.py
[3] https://bitheap.org/cram/
[4] https://pypi.org/project/pytest-cram/
Fixes #10069.
2018-09-20 17:34:14 +03:00
if install_tests
install_data ( 'run-unit-tests.py' ,
install_mode : 'rwxr-xr-x' ,
install_dir : testsdir )
2019-12-10 15:04:39 +03:00
install_data ( 'test-network-generator-conversion.sh' ,
install_mode : 'rwxr-xr-x' ,
install_dir : testsdir )
tests: add a runner for installed tests
We have "installed tests", but don't provide an easy way to run them.
The protocol is very simple: each test must return 0 for success, 77 means
"skipped", anything else is an error. In addition, we want to print test
output only if the test failed.
I wrote this simple script. It is pretty basic, but implements the functions
listed above. Since it is written in python it should be easy to add option
parsing (like running only specific tests, or running unsafe tests, etc.)
I looked at the following alternatives:
- Ubuntu root-unittests: this works, but just dumps all output to the terminal,
has no coloring.
- @ssahani's test runner [2]
It uses the unittest library and the test suite was implented as a class, and
doesn't implement any of the functions listed above.
- cram [3,4]
cram runs our tests, but does not understand the "ignore the output" part,
has not support for our magic skip code (it uses hardcoded 80 instead),
and seems dead upstream.
- meson test
Here the idea would be to provide an almost-empty meson.build file under
/usr/lib/systemd/tests/ that would just define all the tests. This would
allow us to reuse the test runner we use normally. Unfortunately meson requires
a build directory and configuration to be done before running tests. This
would be possible, but seems a lot of effort to just run a few binaries.
[1] https://salsa.debian.org/systemd-team/systemd/blob/242c96addb06480ec9cd75248a5660f37a17b4b9/debian/tests/root-unittests
[2] https://github.com/systemd/systemd-fedora-ci/blob/master/upstream/systemd-upstream-tests.py
[3] https://bitheap.org/cram/
[4] https://pypi.org/project/pytest-cram/
Fixes #10069.
2018-09-20 17:34:14 +03:00
endif
############################################################
2017-09-26 14:39:43 +03:00
# prepare test/sys tree
sys_script_py = find_program ( 'sys-script.py' )
custom_target (
'sys' ,
command : [ sys_script_py , meson . current_build_dir ( ) ] ,
output : 'sys' ,
2018-09-12 15:47:56 +03:00
build_by_default : want_tests != 'false' )
2017-09-26 14:39:43 +03:00
2018-03-22 10:34:21 +03:00
if perl . found ( )
udev_test_pl = find_program ( 'udev-test.pl' )
2018-09-12 12:08:49 +03:00
if want_tests != 'false'
test ( 'udev-test' ,
2019-01-19 00:32:42 +03:00
udev_test_pl ,
timeout : 180 )
2018-09-12 12:08:49 +03:00
endif
2018-03-22 10:34:21 +03:00
else
message ( 'Skipping udev-test because perl is not available' )
endif
2017-09-26 14:44:04 +03:00
2017-10-08 23:14:45 +03:00
if conf . get ( 'ENABLE_HWDB' ) == 1
hwdb_test_sh = find_program ( 'hwdb-test.sh' )
2018-09-12 12:08:49 +03:00
if want_tests != 'false'
test ( 'hwdb-test' ,
hwdb_test_sh ,
timeout : 90 )
endif
2017-10-08 23:14:45 +03:00
endif
2018-01-19 09:54:30 +03:00
2018-07-07 19:09:21 +03:00
subdir ( 'fuzz' )
