PlumbSpecification · 0.8.3
What Plumb 0.8.3 proves
Every story in Plumb's specification, with what its own test suite proved when this release was cut. There is no separate list of open issues: the 38 stories not proven here are what is left.
By chapter
| dev00-1 · bring plumb to a project | 3 of 5 proven | |
| dev03 · open a session | 2 of 3 proven | |
| dev06-1 · say it in the reader's words | 0 of 4 proven | |
| dev07-1 · run the suite under observation | 3 of 6 proven | |
| dev07-2 · check the tests bite | 4 of 4 proven | |
| dev07-3 · collect what the run did | 3 of 3 proven | |
| dev07-4 · decide whether it is proven | 2 of 3 proven | |
| dev07-5 · report it | 3 of 3 proven | |
| dev07-6-2-1 · send what a run produced | 3 of 4 proven | |
| dev07-6-2-2 · hold a series | 0 of 2 proven | |
| dev07-6 · append the run to the series | 3 of 5 proven | |
| dev07 · run plumb — the proving pipeline | 0 of 6 proven | |
| dev08-1 · contribute a module | 4 of 5 proven | |
| dev10 · close the session | 3 of 4 proven | |
| A developer's workflow | 1 of 15 proven |
One run, at one tag
This is the board Plumb's own suite produced when this release was cut, joined with its specification. Anybody can produce the same thing for their own project with the free tools, on their own machine: the specification is checked by goldspec, and the board is plumb's.
What paying adds is what a single run cannot say. Every release of Plumb also sends this run to our hosted history, under our own account, the way a paying customer's build host sends theirs. From that history the paid service:
- keeps every run, for the whole team, in one place;
- names what stopped passing, oldest first, with the test that broke it and the run it last passed in;
- names tests that still pass but now reach a different part of the system;
- says how far along each project is against before, and which have stopped reporting.
How to read this
A story is one thing somebody does. Under it are its requirements: what the user needs, what the system does, and how well. A story is proven when a test that cites it ran, passed, and reached the system through one of its declared entry points, so a passing test over code nothing calls does not count. A story nothing cites is shown rather than left out, because a board that omitted it would read as finished.
Something you need that is not here, or here and not working, is filed through support. If it belongs in the product it becomes a requirement on this page, and you are told when a release proves it.