Skip to main content

Test Book Explorer

The Test Book Explorer is a read-only reference view that shows, for each test book, exactly what it tests and how. It answers three questions an operator typically asks before trusting an automated run:

  1. What cases are in this book, and which are automated?
  2. How is each case actually performed?
  3. What ends up in the completed document, and where does it come from?

The Explorer is reached from the Roaming Test Books screen via Explore books, and lets you switch between IR.38, IR.48, and VoLTE.

The Test Book Explorer showing the IR.48 book: eight cases with a summary of automated and manual counts, and a table of each case with how it is driven

The Explorer showing the IR.48 book — each case listed with whether it is automated or manual and a description of how it is driven.

Tests​

The Tests view lists every case in the book with:

  • the case number and title (matching the GSMA specification),
  • whether the case is automated or manual, and
  • a plain description of how it is driven — for example "data session + charging-record check", "voice call", "barring activation and call attempt", or "tester records the result" for manual cases.

This is the quickest way to see, at a glance, how much of a given book OmniRoam performs for you and what remains a manual check.

How It Runs​

The How it runs view shows the step sequence a full run of the book will perform, in order — readying the device, the data sessions, the throughput check, the voice and SMS drives, the supplementary-service drives, and so on. It reflects the cases currently in scope, so it is an accurate preview of what a run will do before you start it.

This view is useful for understanding the shape of a run and for confirming that a customised scope will perform the steps you expect.

Form Fields​

The Form fields view lists every cell in the completed GSMA workbook that OmniRoam fills, each annotated with:

  • the sheet and cell in the GSMA template,
  • the GSMA field label (read from the template itself), and
  • the source of the value — for example the subscriber MSISDN, the test date, a per-case pass/fail verdict, or a measured value such as data volume.

Because this list is derived from the same logic that produces the document, it cannot drift out of step with the actual export: what the Explorer says will be filled is exactly what gets filled. See Completed Test-Book Documents for the document itself.

Download Template​

The Explorer also offers a Download Template action, which downloads the blank GSMA workbook for the selected book — the official template with the vendor's example/placeholder content removed, ready to fill in by hand if needed. This is the empty counterpart to the completed document a run produces (see Completed Test-Book Documents).

Why It Matters​

A roaming partner accepting a completed test book needs confidence that the results are real and that the document faithfully represents what was tested. The Explorer makes the mapping transparent: every automated case can be traced from the GSMA case number, through the way it is driven, to the exact cell it lands in on the final document.

Last updated on