From red specs to the implementation Added in 1.7.0
Turn red Bobcat specs into the Critter Stack implementation they describe, until they pass: scaffold the declared-but-unimplemented slices with wolverine scaffold (dry run, --json notice codes, --strong-typed-ids, what each slice pattern becomes), read the slice's shape out of the spec's vocabulary calls (GivenEvents, WhenReceived, WhenPosted, ThenEvents, ThenReadModel, ThenRefusedWith, ThenMessageSent), then write the command handler, aggregate, events and projection in house style (aggregate handler workflow, declarative returns, store-agnostic [WriteModel]/EventsToAppend). Covers reading Bobcat's gathered failure messages (IndeterminateRoutesException, NotImplementedException TODO, the act failed, wrong values, projection timeouts), matching the handler's refusal style to the spec's refusal step, the order to work in, the run loop (dotnet test --filter-class, bobcat watch), and never editing a spec to make it pass.
Use when specs are red because the implementation is missing or wrong, after an Event Model import, or when working spec-first slice by slice.
Skill details
- Skill name:
critterstack-sdd-code-from-specs - Applies to:
wolverine,marten,polecat,fisher - Tags:
sdd,bobcat,specifications,event-modeling,scaffold,handlers,projections,code-generation,StubEventStream - Added in: 1.7.0
- License: Proprietary. Copyright JasperFx Software LLC.