Test suites
Save reusable tests and run them together as a suite.
A one-off run is great for quick checks, but as a configuration matures you'll want a repeatable set of tests you can run every time you change it. That's what suites are for.
Test configurations
A saved test — a test configuration (or definition) — bundles everything a run needs:
- A name (and optional description).
- An input file (from My files or Templates).
- A target pipeline / signal type.
- A duration.
- Any validation rules for its output.
Because the inputs are saved, you can re-run the exact same test on demand without re-selecting files each time.
Suites
A suite groups related test configurations. From the Suites sub-tab you can:
- Create a suite and give it a name.
- Add test configurations to it.
- Edit or remove tests within it.
Running tests from a suite
- Run a single test — press the play action on a test row. The run appears under the Tests sub-tab so you can watch it and inspect the result.
- Run the whole suite — play all tests in the suite at once. Telflo executes every test configuration in the suite and surfaces each run in the history.
Running a suite is the fastest way to confirm a configuration change didn't break anything before you publish and deploy it.
Requirements
As with single runs, suite runs operate on the current saved version of the configuration and require an organization to be selected.