TEST · Runik
On-prem binary that drives 5G SA procedures. Same flow in the lab and in CI. Unsigned community floor: NGAP, SBI, REST, and JUnit, up to 1000 UE. PFCP and load are licensed — not on the unsigned binary. Runik workers are daemons that attach to a lab host.
The problem
Most teams arrive with scripts, a load tool, and an appliance — each covering a slice, none living where the code does.
Socket scripts give control but no structure. Reporting is reinvented per test, and NGAP and Diameter suites slowly stop agreeing.
A conformance harness proves one UE took the right path; a load tool proves the AMF survives a thousand. Different tools mean different code paths.
Appliances cover what they ship, live behind a GUI, and never land in a PR or CI runner. Gaps need authoring you cannot do.
What it does
A declarative state machine drives the wire. The same YAML runs in the lab and in CI. Load is licensed.
Each flow is a protocol FSM — states wait, transitions check, extract, then send. Six action types, fourteen check operators, schema-enforced at load.
Same YAML for a single-UE check in the lab and in the pipeline. Load (high-rate bursts) is a licensed capability, not the unsigned floor.
NGAP, NAS, SBI, REST, plus GTP-U on the unsigned binary. PFCP is licensed — not a peer on the community floor.
Ordered flow steps as one cycle: provision, run, tear down. stop_on_failure gates the cycle; always_run cleans up even on failure.
run-flow and run-suite exit 0 on pass, non-zero otherwise. Gate on exit code, or capture JSON/JUnit with -output.
After PDU session setup, uplane_start arms N3 traffic and measures packets, bytes, RTT, jitter, and drop. Userspace or embedded DPDK.
Wire protocols
Real 3GPP and IETF stacks, driven by the same FSM dispatcher. PFCP is licensed — not on the unsigned binary.
Next step
Tell us what you're testing — or read the docs and run your first flow in about ten minutes.
