Class BowireStepScenario
- Namespace
- Kuestenlogik.Bowire.Mocking
- Assembly
- Kuestenlogik.Bowire.dll
Named-scenario state-machine gating for a stub (mock matcher, #408) —
the analog of WireMock Scenarios. A scenario is a named state; a stub gated
on RequiredState only matches while the scenario is in that
state, and a match moves the scenario to NewState. Lets the
same request return different responses across a lifecycle (e.g.
not-found → created → found).
public sealed class BowireStepScenario- Inheritance
-
BowireStepScenario
- Inherited Members
Constructors
BowireStepScenario()
public BowireStepScenario()Properties
Name
Scenario name. Multiple scenarios per recording are independent.
[JsonPropertyName("name")]
public string Name { get; init; }Property Value
NewState
State to move the scenario to after a successful match. Null = no transition.
[JsonPropertyName("newState")]
public string? NewState { get; init; }Property Value
RequiredState
State the scenario must be in for this stub to match. Null = the
scenario's initial state (Started) — so a stub with a scenario
name but no required state gates on the start state.
[JsonPropertyName("requiredState")]
public string? RequiredState { get; init; }