Getting started

Run your first TTCN-3 test case

Walk through one TTCN-3 execution in detail: suite selection, parameter files, live verdict streaming, and how to read the message sequence chart.

7 min read

A TTCN-3 execution has four inputs: a test case, a build, a lane, and a parameter set (PIXIT/PICS). The platform resolves defaults for everything you leave out.

Pick a test case

bashbash

aeon cases search "registration" --release 18
aeon cases show TC_6_1_1_1

Provide PICS/PIXIT

aeon.yamlyaml

project: nr-modem-x75
release: 18
pics:
  pc_NR_SA: true
  pc_IMS_VoNR: false
pixit:
  px_IMSI: "001010123456789"
  px_Band: n78
  px_SubcarrierSpacing: 30

Execute with live output

bashbash

aeon exec run --case TC_6_1_1_1 --build rc3 --follow

Reading the MSC

Every execution produces a message sequence chart alongside the log. The MSC is the fastest way to see which procedure step diverged from the expected 3GPP flow — the first red arrow is almost always the real failure, and everything after it is fallout.

Left column: UE. Right column: simulated network (gNB + AMF).
Timers (T3510, T3502, T310) render as spans, so expiries are visually obvious.
Click any message to open the decoded ASN.1 and the matching PCAP frame.

Run this against a real SDR lane

The tester is a service, not a box. Push a build, reserve a lane, get a verdict.

Previous Connect your UE to AEON Cloud NextInstall srsRAN UE