Owned local sample / Recorded 8 September 2026
See the bug.
Then inspect the evidence.
An invoice and shipping fixture with deliberately seeded faults. Compare the outcomes to see why one passing test cannot tell the whole story.
A passing test misses the shipping fault.
The fast-check property test passes, while unit, API, combinatorial property, browser and Gherkin checks fail. The sample deliberately changes the shipping boundary.
| METHOD | TASK RESULT | CHECKS PASSED | CHECKS FAILED |
|---|---|---|---|
| Unit tests | Failed | 3 | 1 |
| API checks | Failed | 2 | 1 |
| Property checks · combinations | Failed | 0 | 1 |
| Property checks · fast-check | Passed | 1 | 0 |
| Browser checks | Failed | 0 | 1 |
| Gherkin scenarios | Failed | 1 | 1 |
Six of twelve mutations survived in the fixed sample. This educational fixture was executed locally. It contains no customer data, cloud execution or model-generated results. These outcomes demonstrate the included tests and known faults; they do not establish customer results or live provider qualification.
Reproduce the unit examples yourself.
The evidence pack includes the specification, source, tests, measured outcomes, selected native reports and SHA256 checksums. Extract it and use Node 20 or later to run the included unit examples:
node --test sample/tests/rules.test.cjsProduct names in the exported files were changed to Cue April. The recorded outcomes are unchanged.
Your next release starts here
Keep building.
Put testing to work.
Give Cue April your next testing challenge. Let your AI quality lead coordinate the checks, so your team can focus on what comes next.
Create your account, connect a repository and review your proposed setup before approving a run.