Test Environment and Tooling⚓︎

This page defines the environment every procedure in the acceptance test catalog assumes: the reference topology and its capture points, the tools a tester needs, what the devices and SIMs must be able to do, and how evidence is named and kept. Read it once before planning a campaign; the procedures refer to it rather than repeating it.

Reference topology⚓︎

The platform is exercised on two access paths that share one Mobile Asset, one xControl and one enterprise network. On the local-radio path, customer-controlled radios attach directly to an Expeto Edge (xCore) instance at the site; authentication is performed by the subscriber database inside that xCore and nothing leaves the site. On the public-radio path, the same SIM attaches to the mobile operator's macro network; the operator's core reaches Expeto Gateway (xRouter), which authenticates the subscriber and forwards user-plane traffic over a secure link to the xCore instance dedicated to that customer in its public configuration. Both xCores and the xRouter are managed by Expeto Management (xControl and xView) through an agent that connects outbound from each site.

Capture points⚓︎

Every procedure that ends with "inspect the signalling capture" expects a capture at one or more of these points. Capture on the host interface that carries the traffic (with tcpdump on the node, or a port mirror on the switch) or on the radio itself.

Tools⚓︎

CLI commands used by the procedures⚓︎

Open the CLI with kubectl exec -it <release>-xfabric-agent-0 -c agent-cli -- cli on xCore, or kubectl exec -it <release>-agent-0 -c cli -- cli on xRouter and xControl. Commands are folder-scoped: cd to the folder first. Options are key=value; list filters are -f key=value; -s <n> sets the page size. A one-shot form for scripts is cli "cd /debug/ops && cmd sync-sub-check mode=FULL".

show pgw and show sgw are not implemented and are never cited.

Devices and SIMs⚓︎

• At least two UEs with SIMs provisioned as Mobile Assets on a System of the Site under test. Capacity tests state their own counts.
• Each UE supports the radio access technology under test (LTE, and 5G Standalone where 5G is tested), has the APN of its System Profile configured, and can browse the web or run a terminal application that sends ICMP echo requests.
• A UE application that shows the registration and radio connection state (for example the phone's field-test menu) is needed for the idle-mode procedures.
• For transitions between the public and the private radio, the UE must be able to select the private network's PLMN: either automatically, because the SIM's MNO-controlled PLMN list or the MNO's steering configuration lists it, or manually through the device's network selection menu. State which method the campaign uses in the results sheet.
• Speed and byte-count procedures assume the UE generates no background traffic during the measurement; disable automatic updates and cloud synchronization on the test devices, or use a data-only device.

Evidence⚓︎

Name every evidence file <test ID>_<YYYYMMDD>_<item>.<ext>, for example EXP-SES-001_20260917_s1mme.pcapng or EXP-POL-001_20260917_speedtest-after.png. Keep the files with the completed results sheet for the campaign. Expeto keeps the evidence of its own release-candidate runs with the acceptance test report for that release.

The results template has one row per published test with columns for the result, tester, date, evidence reference and deviation.