Test suites

A one-off run is useful for a quick check. A suite is a repeatable set of tests you run whenever the configuration changes.

Test configurations

A saved test, called a test configuration, bundles what a run needs:

• A Name and an optional Description.
• An input file, from My Files, Templates, or Paste Text; a pasted sample is saved to My Files.
• A Test Pipeline, which determines the signal type.
• A Run duration (seconds), from 1 to 60.

Because the inputs are saved, you can re-run the same test without re-selecting files. A saved test cannot be edited: to change its file, pipeline, or duration, remove it with Delete test configuration and add a new one.

Suites

A suite groups related test configurations and belongs to the configuration version that is loaded. From the Suites sub-tab:

• Select Add suite to create a suite with a Name and an optional Description.
• Expand a suite and select Add test configuration to save a test into it. The New test configuration dialog takes the fields above; select OK to save it.
• Use Edit suite to rename a suite or change its description, and Delete suite to remove it together with its tests, after confirming.

Starting a new version with Create New Version copies the source version's suites and tests to the new version. See Versions & publishing.

Run tests from a suite

• Run a single test. Select Run test on a test row. The run appears under the Tests sub-tab, and the sample-file mismatch warning applies as it does to a one-off run.
• Run the whole suite. Play all in parallel starts every test at once. Play all serially starts one test, waits for it to finish, then starts the next; a failed test does not stop the remaining tests. Either way, Telflo switches to the Tests sub-tab, and each run appears in the history labelled with the suite and the test.

A run started from a suite uses the test configuration's saved duration and the collector version selected in the toolbar. While a run is in progress, the run actions are disabled and show Another run is in progress.

Run a suite to confirm that a configuration change did not break a check before you publish and deploy it.

Suites belong to the editor; the CLI and API have no suites. To repeat the same check from a script or a CI job, keep a telflo test spec file with the configuration: the spec can carry the rules itself, or, once the rules are saved to the Validation sub-tab, hold only the signal, pipeline, and sample and run with telflo test --saved. See Pipeline tests.

Requirements

Suite runs test the configuration as it currently appears in the editor; a configuration version must be loaded.