Build a feature from a spec, tests first, then let Stryker.NET list what the spec forgot

Thu, 29 Oct 2026 23:12:00 +0000

A pricing rule arrives as a ticket: promo codes, a cap on one of them, a minimum spend on another, and “obviously only one code per order”. The agent writes the endpoint in a minute. It looks right. Two weeks later a customer with a 30.00 basket gets told the minimum isn’t met, because the check says <= where the ticket meant <, and nobody can say which of the two the ticket actually meant.

Stryker-Net on Tokenise

Build a feature from a spec, tests first, then let Stryker.NET list what the spec forgot