Test Suite

Functional and integration tests that verify correctness of every layer — from raw io_uring events up to full GObj protocol stacks. All tests are registered as ctest targets and run automatically with yunetas test.

Source: tests/c/

# Run the full suite
yunetas test

# Run a single test by name
ctest -R test_c_timer --output-on-failure --test-dir build

# Run ctest in a loop until first failure (flaky-test detection)
./ctest-loop.sh

Event loop (yev_loop)¶

Low-level tests for the io_uring event loop, without the GObj layer.

Source: tests/c/yev_loop/yev_events/, tests/c/yev_loop/yev_events_tls/

Timers¶

Source: tests/c/c_timer/, tests/c/c_timer0/

TCP networking¶

Plain and TLS TCP through the full GObj protocol stack.

Source: tests/c/c_tcp/, tests/c/c_tcp2/, tests/c/c_tcps/, tests/c/c_tcps2/

TLS certificate hot-reload¶

Protects the cert-reload feature — validates that ytls_reload_certificates() swaps certificates atomically without dropping live sessions and rolls back cleanly on invalid material.

Source: tests/c/ytls/, tests/c/yev_loop/yev_events_tls/

HTTP parser (llhttp wrapper)¶

Source: tests/c/c_llhttp_parser/

OAuth2 / BFF (c_auth_bff)¶

Self-contained yunos that spin up a mock Keycloak (signed HS256 JWTs, scriptable latency / response status / body override) alongside C_AUTH_BFF and drive /auth/login, /auth/callback, /auth/refresh, /auth/logout through happy paths and failure modes. Each test is its own binary so a crash or leak cannot mask neighbours.

Source: tests/c/c_auth_bff/ (includes c_mock_keycloak, test_helpers).

MQTT¶

Source: tests/c/c_mqtt/

Subscriptions & link events¶

Source: tests/c/c_subscriptions/, tests/c/c_node_link_events/, tests/c/tr_treedb_link_events/

Timeranger2 persistence¶

Source: tests/c/timeranger2/

TR_MSG & TR_QUEUE¶

Source: tests/c/tr_msg/, tests/c/tr_queue/

TreeDB¶

Source: tests/c/tr_treedb/

Keyword matching¶

Source: tests/c/kw/

Generic message interchange¶

A JSON-driven test runner that executes scripted test sequences and validates event traces and error logs.

Source: tests/c/msg_interchange/

Debugging a test that corrupts the heap¶

A test that dies with “corrupted double-linked list” or “free(): chunks in smallbin corrupted” is reporting heap corruption that happened earlier: the abort lands at the next malloc/free, not at the write that caused it. The backtrace at that point names the detector, not the culprit.

AddressSanitizer finds it, but not by simply building with it. The test tree links the installed libraries from outputs/lib, not the ones in the build tree, so configuring a build with -fsanitize=address instruments the test’s own .c files and nothing else — and ASan reports nothing while the plain build keeps aborting, which reads as “it is not a real bug” and is only “you did not look at it”.

What actually works, and what it costs:

# 1. a non-static build, because -static and -fsanitize=address are exclusive
cp .config .config.bak && sed -i 's/^CONFIG_FULLY_STATIC=y/CONFIG_FULLY_STATIC=n/' .config

# 2. configure a separate tree WITH the sanitiser
cmake -S . -B build_asan -DCMAKE_BUILD_TYPE=Debug \
    -DCMAKE_C_FLAGS="-fsanitize=address -g -fno-omit-frame-pointer" \
    -DCMAKE_EXE_LINKER_FLAGS="-fsanitize=address"

# 3. build the LIBRARIES too, not only the test
cmake --build build_asan --target yunetas-gobj timeranger2 yev_loop ytls \
    yunetas-core-linux <the test> -j8

# 4. relink the test by hand against those libraries: take its link.txt and
#    replace every /outputs/lib/lib*.a with the build_asan path

And instrument jansson as well when the corruption is around json: it lives in outputs_ext/lib and is not part of the build. Compile kernel/c/linux-ext-libs/build/jansson/src/*.c with the sanitiser and with its own generated headers — -DHAVE_CONFIG_H -I<jansson>/build/private_include -I<jansson>/build/include —, or it builds but parses nothing and every test fails with “Cannot load json file, bad json”, which looks like a different bug entirely.

With all of it instrumented, ASan names the two lines that matter — where the memory was freed and where it was used afterwards — and a hunt that had taken hours takes a minute.

Restore .config afterwards.

The mistake it usually is¶

Three bench tests died this way on 2026-08-28, and all three were the same thing: a borrowed pointer handed to a function that owns what it is given.

json_array_get(), kw_get_dict(), treedb_get_node() and friends answer a pointer they still own; test_json() frees what it receives. Passing one to the other spends a reference that was never given, and the next json_decref() of the container frees the same block twice. Incref it at the call:

result += test_json(json_incref(record));   // record is borrowed

Build flag¶

Tests are enabled by default via .config (CONFIG_MODULE_TEST=y). Toggle with menuconfig or pass -DENABLE_TESTS=OFF to CMake.

Related¶

• Performance benchmarks live under performance/c/ — perf_c_tcp, perf_c_tcps, perf_yev_ping_pong, perf_yev_ping_pong2 and the new perf_auth_bff. That one measures live throughput over the BFF in the ping-pong style. A run is 10 s by default, and it does about 180 000 ops on the reference box.

• Stress runners live under stress/c/ — stress/auth_bff drives concurrent BFF login / refresh / logout cycles to expose races between the pending queue, the watchdog and the flush-on-disconnect path.