Specs & Groups
Load Test specs are organized in a two-level hierarchy: Spec Groups at the top (folders that share an environment scope) and individual Specs inside them. The sidebar on the left of the Load Test panel is where you create, rename, duplicate, and delete both of them.
The Sidebar
At the top of the sidebar are two actions:
- •New Spec Group — opens an inline input to name a new group
- •Clone (download icon) — clones a remote git repository as a new spec group, wiring up all specs it contains in one step
Below those, the tree lists every spec group as a collapsible folder. Expand a group to see its specs; each spec row shows its name and step count. Click a spec to load it into the main panel.
Spec Group Menu
The three-dot menu on a group exposes these actions:
| Action | What it does |
|---|---|
| Add Spec | Creates a new empty spec inside the group |
| Rename | Rename the group inline (max 50 characters) |
| Environments | Opens the group environment panel — Manual / OS Secret / Vault variables shared by every spec inside the group |
| Git | Opens the group's git panel: commit, push, pull, history — same workflow as Flow and Project git |
| Delete | Removes the group and every spec inside it (confirmation required) |
Spec Menu
Per-spec actions are available on the three-dot menu of a spec row:
| Action | What it does |
|---|---|
| Rename | Edit the spec name inline |
| Duplicate | Creates a copy inside the same group — steps, configs, thresholds and lifecycle scripts are all cloned |
| Delete | Removes the spec (confirmation required) |
What a Spec Holds
Selecting a spec reveals its full editable contents in the main panel. Internally the spec is a single document that stores:
- •Name & creation timestamp
- •Per-test-type configs — one LoadTestConfig per test type (load / stress / spike / soak / custom)
- •Steps — the ordered HTTP step sequence with per-step scripts, assertions and extractions
- •Thresholds — pass/fail rules shared across every test type
- •Before All / After All scripts — optional lifecycle JavaScript
Note: environment variables are not stored on the spec itself — they live on the spec group so multiple specs in the same group can share credentials, base URLs, and other values. See the Variables & Environments section for the full model.