Configure Suites

A suite defines what to test, where to test it, and when to run it.

Suite configuration model

Each suite includes:

• template_id: UUID of a template from the catalog
• targets: one or more endpoints (or tags) in the same chain
• schedule_type + schedule_config: when to run
• config: template-specific inputs
• enabled: whether scheduled execution is active

Create a suite in the UI

The dashboard walks you through this step by step.

1. Open Test Suites (/chains/:chainId/suites).
2. Click New Suite .
3. Select a catalog template from Suite Catalog (/suites/catalog).
4. Pick target endpoint(s).
5. Set schedule mode.
6. Fill template parameters.
7. Save.

Schedule types

The schedule controls how often your suite runs automatically.

• manual: run only when triggered via UI or API
• interval: run every N minutes (schedule_config: { interval_minutes: 5 })
• on_every_n_blocks: run on new block events (requires active observer)
• on_timestamp: run at specific timestamps

Tip

Start with manual, run once, then switch to interval or on_every_n_blocks after your first stable results.

Multi-endpoint comparisons

If you have more than one endpoint, you can compare their behavior in each run. To set this up:

1. Choose at least two endpoints.
2. Mark one as reference.
3. Include candidate endpoints.
4. Configure thresholds if the template supports it.

Comparison verdicts are available on run results.

See Comparisons and Multi-Endpoint Comparison.

Choosing first templates

Not sure which templates to start with? Here’s a safe starting point:

• Basic RPC correctness checks
• Latency and error-rate assertions
• Optional cross-endpoint consistency checks

Avoid transaction-writing suites until you intentionally configure Wallets (Pro).

Validation checklist

Before your first run, verify these settings to avoid unexpected failures.

• Suite targets only endpoints from the same chain
• Parameters match chain characteristics
• Schedule is appropriate for your load and SLOs
• Alert routing is configured if this suite is critical

Next step

Run the suite and inspect results: Reading Results