Get the numbers out of the report
I want the report available as a CSV: the same columns in the same order,
every row that is in the table, and the amounts still reading as money.
Every requirement marked done on this page was demonstrated able to FAIL before it was made to pass.
3 requirements · 3 done and proved · 0 holding up the handover
What happened in this round
The checks were tested against the code as it was before this change, and at least one of them noticed the difference. They are measuring something.
DONE — AND PROVEDThe CSV header is the table's columns, in order
This check has been recorded failing — the run that failed it is in this repository's evidence.
It was red first. This check has been recorded failing — the run that failed it is in this repository's evidence.
What the check itself printedreports.to_csv() does not exist
DONE — AND PROVEDEvery row of the table reaches the CSV
This check failed on the code as it was BEFORE this change, and passes on it now.
It was red first. This check failed on the code as it was BEFORE this change, and passes on it now.
What the check itself printedreports.to_csv() does not exist
DONE — AND PROVEDAmounts keep two decimal places
This check failed on the code as it was BEFORE this change, and passes on it now.
It was red first. This check failed on the code as it was BEFORE this change, and passes on it now.
What the check itself printedreports.to_csv() does not exist
What this page does not claim — Wringer's own words, unedited
- Evidenced means the bound gate passed and has demonstrably failed before. It does not mean the criterion is what the user needed, that the gate covers the criterion's whole meaning, or that coverage cannot narrow later — `wring health` watches that across time.
- The gate-to-criterion binding is a human's declaration. Wringer checks the binding's consequences, never its wisdom.
- Human criteria are answered by people. Nothing here scored them.
- A sensitivity receipt says the gate's result differed between the two trees, not that the difference was the change. A gate whose own command arrived with the change reads sensitive for that reason alone — the citation beside it is how you tell.
For engineers
- acceptance record:
wringer.acceptance.v1 - verifications in this loop: 0 (order unknown — rendered as a set)
- vacuity verdict:
proven