Testing at Expeto⚓︎
This section describes how the Expeto Platform is verified before a release reaches a mobile operator, publishes the acceptance test catalog an MNO uses to plan its own verification, and states the platform's conformance to the 3GPP specifications it implements.
Expeto's approach is deliberately compact and deliberately transparent. The platform is a focused private-wireless core, not a national core, and the published tests reflect that: a catalog of end-to-end procedures that exercise the platform the way an MNO's enterprise customers use it, executed on real devices against a complete deployment, with signalling evidence captured where it matters. Behind the catalog sits a continuous verification pipeline that installs real cores on Kubernetes and drives them with 3GPP peer simulators on every code change.
Four layers of verification⚓︎
| Layer | What runs | Against | When |
|---|---|---|---|
| Component tests | Unit and component suites in every repository | The component in isolation, with real databases where the component needs one | Every merge request |
| Continuous end-to-end verification | Six platform suites that install xControl, xView and the cores from published charts, and browser tests of xControl | Real deployments on Kubernetes, 3GPP peer simulators for radio and core signalling, real Chromium browsers | Every merge request, plus a weekly deep soak |
| Release certification | Declarative core configurations driven end to end with subscriber lifecycle scenarios | A real cluster | Before a release is published |
| Acceptance testing | The published acceptance test catalog | A complete deployment with real devices and radios | Every release candidate in Expeto's lab, and the installation and upgrade verification set in the MNO's environment |
What is published here⚓︎
| Page | What it covers |
|---|---|
| How Expeto tests | Test levels, cadence, environments, release gating, evidence, and how the catalog is maintained as code. |
| Test environment and tooling | The reference topology, where to capture signalling, the tools each procedure assumes, and how evidence is named and kept. |
| How to read and run a procedure | The anatomy of a test card, how procedures chain, how results are recorded, and the glossary of xControl and 3GPP states. |
| Continuous verification | What runs automatically on every change: the platform suites, the xControl browser suite, release certification, component tests and supply-chain checks. |
| Acceptance test catalog | End-to-end tests of Expeto Edge (xCore), Expeto Gateway (xRouter) and Expeto Management (xControl and xView), by domain, with full procedures. |
| Installation and upgrade verification | The minimal set an MNO runs after every installation or upgrade, with its execution order and results sheet. |
| Standards coverage | The 3GPP procedure each test exercises, and which tests cover each cited clause. |
| Campaign planning and results | Effort and resources per domain, a suggested sequence, and the results template. |
| Standards conformance | The item-level conformance statements against the 3GPP and IETF specifications the network functions implement, generated from a structured source, with the capabilities the platform does not exercise marked as such. |
Principles⚓︎
Tests are code. Every acceptance test is a version-controlled source file in the same repository as this documentation. A test changes the same way the software does: through a reviewed merge request. The catalog pages are generated from those sources, and the documentation pipeline refuses to publish a page that differs from its source.
End to end, on real devices. Acceptance tests are executed with commercial UEs against a complete deployment of xCore, xRouter and xControl, not against mocks. Where a procedure has a defined 3GPP flow, the signalling capture is part of the evidence.
Stable identifiers. Each test has a permanent public identifier. Release notes cite test identifiers when a release adds, changes or retires a test, so an MNO can trace a release to the tests that gated it.
Nothing is published half-finished. Every procedure in the catalog is complete and reviewed before it is released; the result of executing it on a platform release is recorded per release in the acceptance test report. The continuous verification pages state the real cadence of every automated suite, including the ones that run on demand.
MNOs run the same tests. The installation and upgrade verification set is written to be executed by an operator's own test team in its own environment, and Expeto reviews the results with the MNO before sign-off.