featkpr
Private demo

Every goal featkpr keeps for BookStack, and the routes that show it.

A goal is one thing a person comes to get done: a book created, an export downloaded, a token deleted. Features group goals; each goal is anchored on the routes where it can be seen, and featkpr drafts how complex it is.

Complexity against proof #

Rows are the complexity featkpr drafted from what each goal's routes do (inputs, roles, calls, branches). Columns are how far its tests got. Pick a cell to see its goals.

Two counts, both true. The Flows board groups its flows by the 89 features they end at, one group each. The goal records here are wider: every goal read from the code and the crawl. Here: 165.

proven32passed, not proven33a test written4no test yet96
simple1 goals 0001
moderate44 goals 134225
complex108 goals 1823166
hard12 goals 1614

Proven: every test on it passed, and failed when sent as the wrong user. Passed, not proven: its tests passed, one or more not proven yet. A test written: not run yet. No test yet: read from the code and the crawl only.

Search the goals #

Each goal says what changes, the routes where it can be seen and what kind of evidence each route is. Open one for the features on its routes and the flows that end on it, linked by route.

What each goal does, as a mechanic (the kind of action behind it, named the same way in every app): BookStack’s goals by mechanic, and what a mechanic is.

See your own app's goals #

On the call we walk BookStack's goals and what keeps them bounded, then talk about yours. Tim replies by hand.

Ask for a private demo

↑ ↓ to move, Enter to open, Esc to close