Integration Tests

A set of integration tests validate the released Aether Blueprints. These tests exercise representative deployment scenarios and simulated 5G workloads used throughout this guide.

The GitHub Actions workflows in the aether-onramp repository under .github/workflows build hosts.ini dynamically before running the playbooks. The single-node workflows do this through shared helper scripts under .github/scripts. They use localhost with ansible_connection=local and do not set ansible_host. This lets the workflows exercise the same playbooks without requiring SSH access back into the runner itself.

Those workflows also create a Python virtual environment once at the start of the job and export its bin directory to subsequent steps, rather than re-activating the virtual environment in every shell snippet. Common 5G Core log retrieval and repeated cleanup targets are likewise centralized in helper scripts so the workflow definitions stay aligned.

The current integration-test inventory patterns are as follows:

• Quick Start, Quick Start AMP, SD-RAN, OAI, and srsRAN run as single-node tests, with both [master_nodes] and the blueprint-specific host group pointing at localhost.

This means the checked-in inventory examples and the CI-generated inventories are similar in structure, but they do not use identical host aliases.

Finally, note that the current GitHub Actions integration tests run a variety of simulated 5G workloads, including gNBsim, OAI 5G RAN (in simulation mode), and srsRAN (in simulation mode). The UERANSIM blueprint remains part of OnRamp and is validated by the broader integration test suite, but it is not currently exercised by the GitHub Actions workflow set. Of the workloads that are tested in CI, gNBsim provides the most rigorous testing of the Core’s control plane, and serves as Aether’s primary validation of that functionality. More information about gNBsim can be found in the Emulated RAN section of this Guide.