logos-blockchain-testing/book/src/scenario-builder-ext-patterns.md

# Core Content: ScenarioBuilderExt Patterns

> **When should I read this?** After writing 2-3 scenarios. This page documents patterns that emerge from real usage—come back when you're refactoring or standardizing your test suite.

Patterns that keep scenarios readable and reusable:

- **Topology-first**: start by shaping the cluster (counts, layout) so later
  steps inherit a clear foundation.
- **Bundle defaults**: use the DSL helpers to attach common expectations (like
  liveness) whenever you add a matching workload, reducing forgotten checks.
- **Intentional rates**: express traffic in per-block terms to align with
  protocol timing rather than wall-clock assumptions.
- **Opt-in chaos**: enable restart patterns only in scenarios meant to probe
  resilience; keep functional smoke tests deterministic.
- **Wallet clarity**: seed only the number of actors you need; it keeps
  transaction scenarios deterministic and interpretable.

These patterns make scenario definitions self-explanatory while staying aligned
with the framework’s block-oriented timing model.
-												Initial import of Nomos testing framework

											
										
										
											2025-12-01 12:48:39 +01:00
+								# Core Content: ScenarioBuilderExt Patterns
-												docs: comprehensive documentation improvements

- Rename to 'Logos Blockchain Testing Framework Book'
- Rebrand protocol references from Nomos to Logos
- Add narrative improvements (Core Concept, learning paths, callouts)
- Expand best-practices and what-you-will-learn pages
- Add maintenance guide (README.md) with doc-snippets documentation
- Add Notion documentation links
- Fix code example imports and API signatures
- Remove all icons/emojis

											
										
										
											2025-12-18 19:47:29 +01:00
+								> **When should I read this?** After writing 2-3 scenarios. This page documents patterns that emerge from real usage—come back when you're refactoring or standardizing your test suite.
-												Initial import of Nomos testing framework

											
										
										
											2025-12-01 12:48:39 +01:00
+								Patterns that keep scenarios readable and reusable:
 								- **Topology-first**: start by shaping the cluster (counts, layout) so later
 								  steps inherit a clear foundation.
 								- **Bundle defaults**: use the DSL helpers to attach common expectations (like
 								  liveness) whenever you add a matching workload, reducing forgotten checks.
 								- **Intentional rates**: express traffic in per-block terms to align with
 								  protocol timing rather than wall-clock assumptions.
 								- **Opt-in chaos**: enable restart patterns only in scenarios meant to probe
 								  resilience; keep functional smoke tests deterministic.
 								- **Wallet clarity**: seed only the number of actors you need; it keeps
 								  transaction scenarios deterministic and interpretable.
 								These patterns make scenario definitions self-explanatory while staying aligned
 								with the framework’s block-oriented timing model.