Generated code can satisfy the example and still violate the contract. Write tests around meaningful behaviors rather than the implementation's current output. A remaining balance should reach zero at exact payment and stay zero after overpayment. If every test uses an unpaid invoice, a helper that ignores payments can pass. In this lesson you write an editable test set for integer cents. The checker runs the expectations against the correct rule and checks whether your cases catch three seeded implementation errors. It accepts any valid case values that expose the boundaries. Copying a failing implementation's output into expected would simply preserve the bug.
A worked artifact for a separate fictional task. Compare its actions with the contract.