AEONCloud
Sign in
Running tests

Reports and verdict exports

Generate signed conformance reports in PDF, JSON, and JUnit XML — contents, signature verification, retention, and sharing with certification bodies.

6 min read

Formats

FormatFor
PDFCertification bodies, customers, audit trails
JSONDashboards, internal tooling, diffing runs
JUnit XMLCI test reporting (GitHub, GitLab, Jenkins)
CSVSpreadsheet analysis of large campaigns

Generate

bashbash
aeon reports get --exec 4821 --format pdf   --output ./cert.pdf
aeon reports get --campaign nightly --run 214 --format junit --output ./junit.xml
aeon reports diff --a 4820 --b 4821    # verdict deltas between two runs

What the PDF contains

  • Device and build identity, including artifact checksum.
  • Lane identity, SDR model, firmware, and calibration timestamp.
  • Abstract test suite version and 3GPP release.
  • Per-case verdict, duration, and failure clause reference.
  • PICS/PIXIT snapshot used for the run.
  • Detached signature over the whole document.

Verify a signature

bashbash
aeon reports verify ./cert.pdf
# signature: valid  signer: AEON Cloud Reports  signed: 2026-07-14T09:12:03Z

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 Logs, PCAPs, and evidenceNextCoverage and requirement traceability