The current test directory contains tests that require functional DSP hardware to execute. This makes the test suite impossible to run during standard Linux distribution package builds, CI pipelines, or on architectures that lack DSP hardware.
Since fastrpc is being packaged for multiple Linux distributions (e.g., Debian and Fedora), maintainers need a way to verify that the package was built correctly without requiring specific hardware.
Please add at least one generic, hardware-independent test that exercises the core library APIs, such as initialization, basic handle management, or stub generation, in a way that either fails gracefully or uses a mock backend when DSP hardware is unavailable.
This would allow make check, or an equivalent test target, to run successfully on build machines while still providing meaningful validation that the build artifacts are functional.
The current test directory contains tests that require functional DSP hardware to execute. This makes the test suite impossible to run during standard Linux distribution package builds, CI pipelines, or on architectures that lack DSP hardware.
Since
fastrpcis being packaged for multiple Linux distributions (e.g., Debian and Fedora), maintainers need a way to verify that the package was built correctly without requiring specific hardware.Please add at least one generic, hardware-independent test that exercises the core library APIs, such as initialization, basic handle management, or stub generation, in a way that either fails gracefully or uses a mock backend when DSP hardware is unavailable.
This would allow
make check, or an equivalent test target, to run successfully on build machines while still providing meaningful validation that the build artifacts are functional.