---
title: "Test Config | Speedscale Docs"
description: "Customize how the replay is performed."
canonical: "https://docs.speedscale.com/reference/configuration/"
---

[Documentation index](https://docs.speedscale.com/reference/llms.txt) | [Markdown](https://docs.speedscale.com/reference/configuration/index.md) | [Canonical page](https://docs.speedscale.com/reference/configuration/)

# Test Config

Speedscale's load generator relies upon a basic set of config items to determine how it will behave at runtime.

You can view these in the [UI](https://app.speedscale.com/config):

![test-config](https://docs.speedscale.com/assets/images/test-config-8ef506d8cd999fa2d39f39ae678a359f.png)

Or via the CLI:

```bash
# get all test configs
speedctl get testconfigs -o pretty

# pull a test config to the local cache
speedctl pull test-config my-config

# push a test config after modification
speedctl push test-config my-config
```

<a id="structure"></a>

### Structure

There are several sections within a Test Config:

1.  **Traffic** - Set general configuration for how a replay should run
2.  **Load Pattern** - Set how load should be applied throughout the replay
3.  **Cluster** - Set infrastructure specific settings
4.  **Sidecar** - Set sidecar secrets for replays running inside a Kubernetes cluster
5.  **Assertions** - Set expected responses from the application
6.  **Goals** - Set thresholds which will constitute a failed test report
7.  **Readiness** - Set which readiness families block the verdict, their floors, weights and boundaries, and the acceptance policy (see the [Readiness guide](https://docs.speedscale.com/guides/readiness/test-config-settings/))
8.  **Advanced** - A text representation of the test config

Some sections contain more details on the following pages.

<a id="replay-seed"></a>

### Replay seed

`replaySeed` is a top-level string field that seeds the variation a replay configures, so one value makes that variation repeatable.

```json
{
  "id": "my-config",
  "replaySeed": "run-42"
}
```

When `replaySeed` is set, it replaces the test config ID as the seed for [chaos](https://docs.speedscale.com/concepts/chaos/) rules and replaces the snapshot ID as the seed for a load plan and for which sessions a sessions stage replays.

Explicit seeds still win. A chaos rule with its own `seed` uses that seed, and `generator.loadSeed`, including zero, wins over `replaySeed` for the load plan and sessions stages.

When `replaySeed` is absent or an empty string, nothing changes: chaos rules seed from the test config ID, and the load plan and sessions stages seed from the snapshot ID.

A replay with chaos rules records the chaos seed it used as a replay settings event named `ChaosSeed` in the report.

To set it from proxymock, edit `replaySeed` in `proxymock/testconfigs/<name>.json`, or use the MCP `test_config` tool with `action=set` and `fields` of `{"replaySeed": "run-42"}`. A `null` value removes the field.

The same seed, test config, recording and Speedscale version reproduce the planned arrivals and the chaos choices.

Randomness inside your application, operating system scheduling, response timing and which replica serves a request are outside that boundary, so two runs with the same seed can still differ in those.
