Test harness for the F-Stack lib/ glue layer. It contains two suites:

Total: 189 unit test cases across 11 binaries + 8 integration test cases.

• gcc + GNU make
• pkg-config reporting cmocka >= 1.1.7
  • TencentOS 4.x: dnf install -y libcmocka libcmocka-devel
  • Verify: pkg-config --modversion cmocka
• DPDK 23.11 / 24.11 headers + runtime libs under /usr/local (rte_config.h, librte_*.so)
• lcov / genhtml (for coverage reports)
• valgrind (for make check memcheck)

Coverage and integration binaries are linked against the DPDK shared libs, so they need the runtime path at execution time:

export LD_LIBRARY_PATH=/usr/local/lib64:$LD_LIBRARY_PATH

The Makefiles already inject this via RUN_ENV for make test / make check / make coverage; you only need it when launching a binary by hand (e.g. ./test_ff_dpdk_kni).

cd /data/workspace/f-stack/tests/unit

make help            # list all targets
make test            # build + run every unit binary (189 TC)
make check           # re-run everything under valgrind memcheck (0 leak gate)
./run_coverage.sh    # build with gcov + run + lcov HTML + G8 threshold gate

Whole-project (unit + integration merged) coverage:

cd /data/workspace/f-stack/tests
./run_full_coverage.sh   # merges unit + integration into one report

You can also build/run a single binary:

make test_ff_config
LD_LIBRARY_PATH=/usr/local/lib64:$LD_LIBRARY_PATH ./test_ff_config

./run_coverage.sh              # full: clean + gcov build + run + report + G8 summary
./run_coverage.sh --quick      # reuse existing .gcda (skip rebuild)
./run_coverage.sh --file ff_config.c   # per-line gcov detail for one file
./run_coverage.sh --serve      # also serve HTML report on :8080
./run_coverage.sh --clean      # remove all coverage artifacts and exit
./run_coverage.sh -h           # help

Exit codes: 0 success & all G8 thresholds met · 1 build/test failure or G8 violation · 2 bad CLI args.

HTML report: unit/coverage_report/index.html.

Invoked automatically at the end of run_coverage.sh. It parses coverage.info and enforces a per-file minimum line and branch percentage. Thresholds are maintained as tline["<file>"] / tbr["<file>"] entries and are ratcheted upward after each coverage-boost stage (kept at actual − ~5pp as a regression guard).

cd tests
./run_full_coverage.sh         # build + run both suites, merge, report
./run_full_coverage.sh --quick # reuse existing .info traces
./run_full_coverage.sh --clean # remove all coverage artifacts

Merged HTML report: tests/full_coverage_report/index.html.

Unlike the unit suite, this harness boots a real DPDK EAL (--no-huge, --no-pci) so it can exercise ff_dpdk_if.c paths that depend on live mempools, rings and ethdev. If EAL init fails (e.g. insufficient permissions), the affected TCs skip() rather than fail.

cd tests/integration
make help
make test            # run integration tests (8 TC)
make check           # under valgrind
make coverage        # gcov build + report -> coverage_report/index.html
make clean

Numbers are produced by run_coverage.sh / run_full_coverage.sh; re-run them to refresh. The authoritative source is always the freshly generated coverage.info, not this table.

1. Add a per-target rule in unit/Makefile listing the lib_objs/*.o + stubs to link, and any -Wl,--wrap=<sym> flags the file needs (see WRAP_FF_LOG, WRAP_FF_DPDKIF, the test_ff_config --wrap=calloc, and the ff_dpdk_kni.o: KNI_EXTRA_CFLAGS := -DFF_KNI per-object override for examples).
2. Add the binary name to the right P{0,1,2,3}_TESTS group.
3. Create test_<file>.c following the cmocka template (group_setup / test_setup / cmocka_unit_test_setup_teardown).
4. Naming convention: test_<function>_<scenario>_<expected>.
5. make test_<file> to build, run, then ./run_coverage.sh --file <file>.c to confirm the targeted branches are now covered.

• common/rte_stub.c — __wrap_rte_exit / __wrap_rte_panic redirect to cmocka mock_assert, so a regression can never SIGABRT the harness.
• common/ff_log_stub.{c,h} — provides struct ff_config ff_global_cfg and a no-op ff_log for binaries that do not link lib/ff_log.c.
• OOM testing: --wrap=calloc with an armed counter (g_calloc_fail_after) passes through to __real_calloc unless armed, letting a TC force the Nth allocation to fail without disturbing cmocka's own allocations.
• Inline DPDK helpers (rte_eth_tx_burst, rte_eth_rx_burst, rte_ring_dequeue_burst) are static inline and cannot be --wrap-ed; testing those paths requires the integration suite with a real PMD.

• All transient file deletions go through /data/workspace/rm_tmp_file.sh (the Makefile clean target uses it; no direct rm).
• No direct rm / kill / pkill / killall / chmod anywhere in the tree.
• Test processes never call real rte_exit / rte_panic (intercepted via __wrap_* → mock_assert).

• Specs: docs/unit_test_spec/zh_cn/ (04-cmocka-framework-and-impl.md, 06-test-cases-and-acceptance.md, Stage-7 7x-*.md, Stage-8 8x-*.md)
• Methodology: c-unittest-expert skill (Unity-based, mapped to CMocka API)
• Stage reviews: docs/unit_test_spec/zh_cn/{99-*,79-stage7-review,89-stage8-review}.md