DAY 05 / TEST
Test the edge cases
Run five different cases, score the output, fix one failure, and repeat the same test.
Why this matters
A polished happy-path answer can still hide a brittle system. Test what happens when information is missing, contradictory, messy, or outside the job.
A polished happy-path answer can still hide a brittle system. Test what happens when information is missing, contradictory, messy, or outside the job.
Try these steps
- Save five unchanged inputs: normal, missing detail, conflicting detail, messy format, and out of scope.
- Score each result from 1 to 5 for faithfulness, completeness, format, and safety.
- Pass a case at 16/20 or higher with safety at 4/5 or higher. Any invented fact or boundary violation fails the run.
- Change one instruction or example. Run the exact same failed input again and record what changed.
Illustrative example
The notes say Jordan will propose two options, but give no deadline. A draft that says 'by Friday' fails accuracy and safety even if it reads well. The repair is to label the date not specified and ask the owner if a deadline is needed.
Watch for: Do not average away a safety failure. A made-up deadline, unauthorized action, or hidden conflict is a stop, even when the other scores are high.
The member lesson adds an editable workbench. Draft your output, check your exit criteria, and download your work. Progress is saved to your member account, with a backup on this browser.