Running tests

The Tests sub-tab is where you run your configuration against sample data and review the history of past runs.

Sample input files

A test needs an input — a file of sample telemetry to feed through your pipeline. When you start a run, you choose where the file comes from:

• My files — files you've previously uploaded to your organization.
• Templates — ready-made sample telemetry provided by Telflo.
• Upload — upload a new sample file on the spot.

Run a single test

1. Open the Testing tab → Tests.
2. Click Run to open the Select Test File dialog.
3. Choose an input file (from My files, Templates, or Upload).
4. Choose the pipeline to run it through. The pipeline determines the signal type (traces, metrics, or logs) for the run.
5. Set the duration in seconds (1–60; default 5). Increase it for pipelines with long windows — for example batch or tail_sampling — that would otherwise produce no output within the default window.
6. Start the run.

Telflo remembers your last-used duration, so the one-click Run button reuses it without re-asking. After the first run, you can re-run the same file and pipeline with a single click.

Fixture check. If the shape of your sample file doesn't look like the signal type you selected (for example, metrics data on a traces pipeline), Telflo warns you before running and lets you Run anyway or cancel.

Run status

Each run appears in the history and progresses through states as it executes (for example, queued → running → finished). If a run can't be started — the testing service is unavailable, rate-limited, or you're offline — it's marked Error rather than left hanging, so the history always reflects reality. You can select any run to view its captured output and results.

Output checks

Sometimes you already have collector output and just want to check it. Use the Output check flow:

1. From the Tests sub-tab, open the Output check dialog.
2. Choose the signal type and paste the output text.
3. Telflo evaluates it and records the result alongside your other runs.

Requirements

• A saved version of the configuration must be loaded (save first if prompted).
• An organization must be selected.
• Runs use the collector version chosen in the editor toolbar.

Next

• Define pass/fail checks for output in Validating configs.
• Save and group reusable tests in Test suites.