logos-blockchain-testing/book/src/workloads.md

# Core Content: Workloads & Expectations

Workloads describe the activity a scenario generates; expectations describe the
signals that must hold when that activity completes. Both are pluggable so
scenarios stay readable and purpose-driven.

## Workloads

- **Transaction workload**: submits user-level transactions at a configurable
  rate and can limit how many distinct actors participate.
- **Data-availability workload**: drives blob and channel activity to exercise
  data-availability paths.
- **Chaos workload**: triggers controlled node restarts to test resilience and
  recovery behaviors (requires a runner that can control nodes).

## Expectations

- **Consensus liveness**: verifies the system continues to produce blocks in
  line with the planned workload and timing window.
- **Workload-specific checks**: each workload can attach its own success
  criteria (e.g., inclusion of submitted activity) so scenarios remain concise.

Together, workloads and expectations let you express both the pressure applied
to the system and the definition of "healthy" for that run.

```mermaid
flowchart TD
    I[Inputs<br/>topology + wallets + rates] --> Init[Workload init]
    Init --> Drive[Drive traffic]
    Drive --> Collect[Collect signals]
    Collect --> Eval[Expectations evaluate]
```

## See Also

- **[RunContext: BlockFeed & Node Control](node-control.md)** — Learn how to use BlockFeed in expectations to observe blocks in real-time, and how to access node control for chaos testing
- **[Examples](examples.md)** — Concrete scenario patterns combining workloads and expectations
- **[Extending the Framework](extending.md)** — Implement custom workloads and expectations