Running tests
Coverage and requirement traceability
Measure 3GPP procedure coverage across campaigns and trace each executed test case back to the specification clause it validates.
6 min read
Coverage in conformance testing is not line coverage. It is the fraction of applicable specification requirements exercised by at least one executed test case, which is what auditors and customers actually ask about.
Query coverage
bashbash
aeon coverage show --build main --release 18 aeon coverage show --build main --domain nas --format json aeon coverage gaps --build main --top 20 # highest-risk unexercised requirements
Example output
texttext
domain applicable executed passed coverage NAS-5GS 184 184 181 100.0% RRC 206 198 193 96.1% PDCP 64 58 58 90.6% RLC 51 44 44 86.3% MAC 72 63 61 87.5% IMS/VoNR 70 0 0 0.0% <- gap total 647 547 537 84.5%
Traceability
Every case in a report links to its clause references, so you can answer a request like "show me the evidence for TS 24.501 clause 5.5.1.2.4" with a filtered artifact set rather than a manual search.
bashbash
aeon trace clause "24.501:5.5.1.2.4" --build main
Run this against a real SDR lane
The tester is a service, not a box. Push a build, reserve a lane, get a verdict.