65 lines
3.3 KiB
Markdown
65 lines
3.3 KiB
Markdown
# Integration tests
|
|
|
|
`make test` is hardware/server independent: offline render tests, concurrent
|
|
plan-replacement stress, and (when JACK headers are present) JACK ABI fault
|
|
injection. The fake links against installed declarations without linking
|
|
libjack. It does not claim to reproduce JACK scheduling; the separate
|
|
threaded stress test exercises publication/reclamation.
|
|
|
|
`make test-jack` explicitly runs a five-second live JACK loopback test. Requires
|
|
an existing JACK or PipeWire JACK-compatible server; does not start a server,
|
|
change its sample rate/block size, or connect physical outputs. Source output
|
|
is connected only to the test's capture client, then disconnected and removed.
|
|
It checks finite/bounded captured samples at two gains, active plan replacement,
|
|
status and ten restart cycles. For a longer run:
|
|
|
|
```sh
|
|
make build/test_jack
|
|
./build/test_jack 30
|
|
```
|
|
|
|
On the inspected system the 30-second test passed at 48000 Hz (initial 1024
|
|
frames): 704 engine blocks, 716 probe blocks, both gains observed, zero xruns,
|
|
and ten restart cycles. This is a limited software-loopback result, not an
|
|
endurance or physical-device qualification. No live server termination or global
|
|
format change is performed on the shared server. Those paths, missing server,
|
|
port/callback setup failure, activation/deactivation/close failure, null buffers,
|
|
invalid configuration, oversize buffers, and reopen are tested with injected
|
|
JACK callbacks/results in `tests/unit/test_backend.c`.
|
|
|
|
## FLTK shell tests
|
|
|
|
```sh
|
|
make gui test-gui
|
|
# Optional, requires a running JACK-compatible server:
|
|
make test-gui-jack
|
|
```
|
|
|
|
These targets require FLTK development files, `xvfb-run` and Xvfb. No additional
|
|
GUI test library is needed. `test_gui.cpp` uses real widgets, menus and timers
|
|
with a fake public C backend. It covers Play/Stop/Reconnect, view switching,
|
|
persistent startup/control errors, server loss/rate changes, partial handles,
|
|
close-failure retry and timer removal. All 18 opened handles are closed.
|
|
`test_gui_jack.cpp` uses the real backend, repeats start/stop nine times across
|
|
three windows, reconnects, and closes each window while running. No audio ports
|
|
are connected. Both tests passed on the inspected host.
|
|
|
|
A separate xdotool smoke run against `build/xtc` under a 1280x800 Xvfb display
|
|
exercised F5/F8/F6, Space, Ctrl+1/2/3 and Ctrl+Q. The app exited successfully;
|
|
visual inspection confirmed running status and mixer view switching.
|
|
|
|
Clang ASan/UBSan found no application errors in the GUI tests. The unsuppressed
|
|
run reports exit-time allocations originating in the installed fontconfig
|
|
library used by FLTK/Pango. `lsan.supp` narrowly suppresses that library; leak
|
|
checking stays enabled for application allocations. This is not a claim that
|
|
the third-party font stack is leak-free. Apply only to GUI sanitizer tests:
|
|
|
|
```sh
|
|
LSAN_OPTIONS=suppressions=tests/integration/lsan.supp xvfb-run -a -s '-screen 0 1280x800x24' ./build/gui-sanitize/test_gui
|
|
```
|
|
|
|
Build that binary with Clang/Clang++, `-fsanitize=address,undefined` in both
|
|
CFLAGS/CXXFLAGS and LDFLAGS, using the baseline warning/include/standard flags
|
|
from BUILD.md. Keep FLTK's `-I` and `-D` flags from `fltk-config --cxxflags`,
|
|
but exclude the distribution's GCC-specific LTO/object-code flags for Clang.
|
|
No suppressions are used for core/backend/realtime sanitizer tests.
|