mirrors/pipewire
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/pipewire/pipewire.git synced 2025-11-03 09:01:54 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions
pipewire/spa/tests/meson.build

87 lines
2.6 KiB
Meson
Raw Normal View History

spa: Update tests and examples Keep tests in spa/tests Make spa/examples Remove some old examples
2019-01-17 09:27:41 +01:00
test_apps = [
'test-buffer',
io: add clock_id to clock Can be used to determine if we need to slave or not. Add node abi test Fix some headers
2019-10-23 13:13:01 +02:00
'test-node',
spa: Update tests and examples Keep tests in spa/tests Make spa/examples Remove some old examples
2019-01-17 09:27:41 +01:00
'test-pod',
'test-utils',
spa: move json parser to utils Add unit test Add escape function
2020-11-28 15:34:01 +01:00
'test-json',
spa: Update tests and examples Keep tests in spa/tests Make spa/examples Remove some old examples
2019-01-17 09:27:41 +01:00
]
spa: tests: add automated unit test for spa_dict
2018-10-30 20:04:05 +02:00
spa: Update tests and examples Keep tests in spa/tests Make spa/examples Remove some old examples
2019-01-17 09:27:41 +01:00
foreach a : test_apps
meson: prefix the names of the tests so that they are unique in the tree meson < 0.46 does not allow two targets to share the same name; meson >= 0.46 relaxes that requirement, but I see no reason to require a new version of meson just for this
2019-02-08 14:07:19 +02:00
test('spa-' + a,
executable('spa-' + a, a + '.c',
audioconvert: add unit test for format conversion Add unit test for fmt conversion and fix some bugs Add empty fmt-ops benchmark
2019-01-23 15:59:54 +01:00
dependencies : [dl_lib, pthread_lib, mathlib ],
spa: don't run the spa_scnprintf abort test under valgrind valgrind doesn't know we expect this to fail, so let's not confuse it
2021-06-08 14:33:13 +10:00
include_directories : [spa_inc, includes_inc ],
Optionally install examples and tests This makes it easier to test PipeWire in its "as-installed" state, for example in an OS distribution. The .test metadata files in ${datadir}/installed-tests/${package} are a convention taken from GNOME's installed-tests initiative, allowing a generic test-runner like gnome-desktop-testing to discover and run tests in an automatic way. The installation path ${libexecdir}/installed-tests/${package} is also a convention borrowed from GNOME's installed-tests initiative. In addition to the automated tests, I've installed example executables in the same place, for manual testing. They could be separated into a different directory if desired, but they seem like they have more similarities with the automated tests than differences: both are there to test that PipeWire works correctly, and neither should be relied on for production use. Some examples are installed in deeper subdirectories to avoid name clashes. Signed-off-by: Simon McVittie <smcv@debian.org>
2020-06-05 14:06:36 +01:00
install : installed_tests_enabled,
install_dir : installed_tests_execdir),
spa: Update tests and examples Keep tests in spa/tests Make spa/examples Remove some old examples
2019-01-17 09:27:41 +01:00
env : [
'SPA_PLUGIN_DIR=@0@/spa/plugins/'.format(meson.build_root()),
])
Optionally install examples and tests This makes it easier to test PipeWire in its "as-installed" state, for example in an OS distribution. The .test metadata files in ${datadir}/installed-tests/${package} are a convention taken from GNOME's installed-tests initiative, allowing a generic test-runner like gnome-desktop-testing to discover and run tests in an automatic way. The installation path ${libexecdir}/installed-tests/${package} is also a convention borrowed from GNOME's installed-tests initiative. In addition to the automated tests, I've installed example executables in the same place, for manual testing. They could be separated into a different directory if desired, but they seem like they have more similarities with the automated tests than differences: both are there to test that PipeWire works correctly, and neither should be relied on for production use. Some examples are installed in deeper subdirectories to avoid name clashes. Signed-off-by: Simon McVittie <smcv@debian.org>
2020-06-05 14:06:36 +01:00
if installed_tests_enabled
test_conf = configuration_data()
meson: replace join_paths(a, b) with a / b More readable and from the meson reference manual: (since 0.49.0) Using the/ operator on strings is equivalent to calling join_paths.
2021-04-15 14:41:04 +10:00
test_conf.set('exec', installed_tests_execdir / 'spa-' + a)
Optionally install examples and tests This makes it easier to test PipeWire in its "as-installed" state, for example in an OS distribution. The .test metadata files in ${datadir}/installed-tests/${package} are a convention taken from GNOME's installed-tests initiative, allowing a generic test-runner like gnome-desktop-testing to discover and run tests in an automatic way. The installation path ${libexecdir}/installed-tests/${package} is also a convention borrowed from GNOME's installed-tests initiative. In addition to the automated tests, I've installed example executables in the same place, for manual testing. They could be separated into a different directory if desired, but they seem like they have more similarities with the automated tests than differences: both are there to test that PipeWire works correctly, and neither should be relied on for production use. Some examples are installed in deeper subdirectories to avoid name clashes. Signed-off-by: Simon McVittie <smcv@debian.org>
2020-06-05 14:06:36 +01:00
configure_file(
input: installed_tests_template,
output: 'spa-' + a + '.test',
install_dir: installed_tests_metadir,
configuration: test_conf
)
endif
spa: Update tests and examples Keep tests in spa/tests Make spa/examples Remove some old examples
2019-01-17 09:27:41 +01:00
endforeach
spa: add a test for missing includes For each header in the spa directory, generate a compilation test that includes just that header. This way we can pick up missing #includes. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2021-06-07 14:09:20 +10:00
# Generate a compilation test for each SPA header, excluding the type-info.h
# ones which have circular dependencies and take some effort to fix.
spa: switch the include header test to C++ by default If we have a C++ compiler, compile all the #include tests with that - it'll pick up any issues that a C compiler will pick up anyway. This saves us from having a separate C++ compiler test and it'll test each header separately for C++ compatibility..
2021-06-08 11:19:33 +10:00
# Do it for C++ if possible (picks up C++-specific errors), otherwise for C.
spa: add a test for missing includes For each header in the spa directory, generate a compilation test that includes just that header. This way we can pick up missing #includes. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2021-06-07 14:09:20 +10:00
find = find_program('find', required: false)
if find.found()
spa_headers = run_command(find_program('find'),
meson.source_root() / 'spa' / 'include',
'-name', '*.h',
'-not', '-name', 'type-info.h',
'-type', 'f',
'-printf', '%P\n')
foreach spa_header : spa_headers.stdout().split('\n')
if spa_header.endswith('.h') # skip empty lines
spa: switch the include header test to C++ by default If we have a C++ compiler, compile all the #include tests with that - it'll pick up any issues that a C compiler will pick up anyway. This saves us from having a separate C++ compiler test and it'll test each header separately for C++ compatibility..
2021-06-08 11:19:33 +10:00
ext = have_cpp ? '.cpp' : '.c'
spa: add a test for missing includes For each header in the spa directory, generate a compilation test that includes just that header. This way we can pick up missing #includes. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2021-06-07 14:09:20 +10:00
c = configuration_data()
c.set('INCLUDE', spa_header)
src = configure_file(input: 'spa-include-test-template.c',
spa: switch the include header test to C++ by default If we have a C++ compiler, compile all the #include tests with that - it'll pick up any issues that a C compiler will pick up anyway. This saves us from having a separate C++ compiler test and it'll test each header separately for C++ compatibility..
2021-06-08 11:19:33 +10:00
output: 'spa-include-test-@0@.@1@'.format(spa_header.underscorify(), ext),
spa: add a test for missing includes For each header in the spa directory, generate a compilation test that includes just that header. This way we can pick up missing #includes. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2021-06-07 14:09:20 +10:00
configuration: c)
executable('spa-include-test-@0@'.format(spa_header.underscorify()),
src,
include_directories: [spa_inc],
install: false)
endif
endforeach
endif
pod: improve parser and builder Remove the spa_pod_iter helpers Remove builder/parser vararg recurse option, you have to manually recurse into structures when needed. This simplifies things a lot. Pass spa_pod_frames to builder and parser explicitly, we don't have to keep an internal stack anymore. The parser is now almost a mirror image of the builder. Make the parser safer when iterating over objects, add functions to check and get pod contents in a safe way. Make the builder return errno style results on errors Improve performance of object properties when they are stored and retrieved in the same order. Add many more tests for the builder and parser Add some benchmarks
2019-01-22 17:38:23 +01:00
benchmark_apps = [
'stress-ringbuffer',
'benchmark-pod',
tests: add small dict benchmark
2020-01-14 13:52:08 +01:00
'benchmark-dict',
pod: improve parser and builder Remove the spa_pod_iter helpers Remove builder/parser vararg recurse option, you have to manually recurse into structures when needed. This simplifies things a lot. Pass spa_pod_frames to builder and parser explicitly, we don't have to keep an internal stack anymore. The parser is now almost a mirror image of the builder. Make the parser safer when iterating over objects, add functions to check and get pod contents in a safe way. Make the builder return errno style results on errors Improve performance of object properties when they are stored and retrieved in the same order. Add many more tests for the builder and parser Add some benchmarks
2019-01-22 17:38:23 +01:00
]
foreach a : benchmark_apps
meson: prefix the names of the tests so that they are unique in the tree meson < 0.46 does not allow two targets to share the same name; meson >= 0.46 relaxes that requirement, but I see no reason to require a new version of meson just for this
2019-02-08 14:07:19 +02:00
benchmark('spa-' + a,
executable('spa-' + a, a + '.c',
audioconvert: add unit test for format conversion Add unit test for fmt conversion and fix some bugs Add empty fmt-ops benchmark
2019-01-23 15:59:54 +01:00
dependencies : [dl_lib, pthread_lib, mathlib ],
pod: improve parser and builder Remove the spa_pod_iter helpers Remove builder/parser vararg recurse option, you have to manually recurse into structures when needed. This simplifies things a lot. Pass spa_pod_frames to builder and parser explicitly, we don't have to keep an internal stack anymore. The parser is now almost a mirror image of the builder. Make the parser safer when iterating over objects, add functions to check and get pod contents in a safe way. Make the builder return errno style results on errors Improve performance of object properties when they are stored and retrieved in the same order. Add many more tests for the builder and parser Add some benchmarks
2019-01-22 17:38:23 +01:00
include_directories : [spa_inc ],
Optionally install examples and tests This makes it easier to test PipeWire in its "as-installed" state, for example in an OS distribution. The .test metadata files in ${datadir}/installed-tests/${package} are a convention taken from GNOME's installed-tests initiative, allowing a generic test-runner like gnome-desktop-testing to discover and run tests in an automatic way. The installation path ${libexecdir}/installed-tests/${package} is also a convention borrowed from GNOME's installed-tests initiative. In addition to the automated tests, I've installed example executables in the same place, for manual testing. They could be separated into a different directory if desired, but they seem like they have more similarities with the automated tests than differences: both are there to test that PipeWire works correctly, and neither should be relied on for production use. Some examples are installed in deeper subdirectories to avoid name clashes. Signed-off-by: Simon McVittie <smcv@debian.org>
2020-06-05 14:06:36 +01:00
install : installed_tests_enabled,
install_dir : installed_tests_execdir),
pod: improve parser and builder Remove the spa_pod_iter helpers Remove builder/parser vararg recurse option, you have to manually recurse into structures when needed. This simplifies things a lot. Pass spa_pod_frames to builder and parser explicitly, we don't have to keep an internal stack anymore. The parser is now almost a mirror image of the builder. Make the parser safer when iterating over objects, add functions to check and get pod contents in a safe way. Make the builder return errno style results on errors Improve performance of object properties when they are stored and retrieved in the same order. Add many more tests for the builder and parser Add some benchmarks
2019-01-22 17:38:23 +01:00
env : [
'SPA_PLUGIN_DIR=@0@/spa/plugins/'.format(meson.build_root()),
])
Optionally install examples and tests This makes it easier to test PipeWire in its "as-installed" state, for example in an OS distribution. The .test metadata files in ${datadir}/installed-tests/${package} are a convention taken from GNOME's installed-tests initiative, allowing a generic test-runner like gnome-desktop-testing to discover and run tests in an automatic way. The installation path ${libexecdir}/installed-tests/${package} is also a convention borrowed from GNOME's installed-tests initiative. In addition to the automated tests, I've installed example executables in the same place, for manual testing. They could be separated into a different directory if desired, but they seem like they have more similarities with the automated tests than differences: both are there to test that PipeWire works correctly, and neither should be relied on for production use. Some examples are installed in deeper subdirectories to avoid name clashes. Signed-off-by: Simon McVittie <smcv@debian.org>
2020-06-05 14:06:36 +01:00
if installed_tests_enabled
test_conf = configuration_data()
meson: replace join_paths(a, b) with a / b More readable and from the meson reference manual: (since 0.49.0) Using the/ operator on strings is equivalent to calling join_paths.
2021-04-15 14:41:04 +10:00
test_conf.set('exec', installed_tests_execdir / 'spa-' + a)
Optionally install examples and tests This makes it easier to test PipeWire in its "as-installed" state, for example in an OS distribution. The .test metadata files in ${datadir}/installed-tests/${package} are a convention taken from GNOME's installed-tests initiative, allowing a generic test-runner like gnome-desktop-testing to discover and run tests in an automatic way. The installation path ${libexecdir}/installed-tests/${package} is also a convention borrowed from GNOME's installed-tests initiative. In addition to the automated tests, I've installed example executables in the same place, for manual testing. They could be separated into a different directory if desired, but they seem like they have more similarities with the automated tests than differences: both are there to test that PipeWire works correctly, and neither should be relied on for production use. Some examples are installed in deeper subdirectories to avoid name clashes. Signed-off-by: Simon McVittie <smcv@debian.org>
2020-06-05 14:06:36 +01:00
configure_file(
input: installed_tests_template,
output: 'spa-' + a + '.test',
install_dir: installed_tests_metadir,
configuration: test_conf
)
endif
pod: improve parser and builder Remove the spa_pod_iter helpers Remove builder/parser vararg recurse option, you have to manually recurse into structures when needed. This simplifies things a lot. Pass spa_pod_frames to builder and parser explicitly, we don't have to keep an internal stack anymore. The parser is now almost a mirror image of the builder. Make the parser safer when iterating over objects, add functions to check and get pod contents in a safe way. Make the builder return errno style results on errors Improve performance of object properties when they are stored and retrieved in the same order. Add many more tests for the builder and parser Add some benchmarks
2019-01-22 17:38:23 +01:00
endforeach
Reference in a new issue Copy permalink