Notes on test evidence, process documentation, and what we learn while building Walkstamp.
The script asks whether it passed. The key user can answer whether it is right. Those are different questions, and the project only has a field for one of them.
The report describes the outcome. Reproduction requires the input. That is why half of the tickets in user acceptance testing come back with "could not reproduce".
Most ERP test cases are scripts, not scenarios. A script is an instruction; a scenario is a condition — and the condition is exactly the part nobody writes down.
The migration fixes orchestration, traceability and the interface. It does not fix — and does not claim to fix — who produces the proof of what was executed.
Factories took forty years to profit from the electric motor. The delay was not the motor's fault — it belonged to whoever kept the old layout. It is happening again.
Invoices are still authorized with the wrong tax calculation. Anyone using "it cleared the tax authority" as an acceptance criterion has a test that tests nothing.
Pasting screenshots into a document is fast, and usually good enough. The problem shows up months later, when someone asks for the proof and has four questions.
Six questions that separate real proof from a pile of screenshots. And why the problem is not the team, but the moment the record is created.
