Expand description
User stories to acceptance-test plans.
A story says what the user does (“When the dial is 80 %”) and, optionally, what they see (“Then the kettle is heating”). Planning walks the story through the expectations: each step works out which expectations fire, and their Thens become the checks to run. So a story only has to tell the journey; the expectations supply what must be true at each step. Planning also refuses stories that rely on behaviour nobody has specified, or that contradict the expectations.
Structs§
- Check
- Plan
- One acceptance test: arrange
start, check it, then perform each step and check it. - Plan
Step - Planned
Enums§
Functions§
- coverage
- For each expectation, the (plan, step) pairs that exercise it; step
Noneis the start. - coverage_
plans - Generated plans for expectations no plan in
plansexercises, following each one’s shortest route from the flow graph. Routes that can’t be made into a clean plan are skipped. - plan_
stories - A plan for every scenario of every story.
- untested
- Warnings for expectations no plan exercises, each with a route that would.