“Think about this, like, you run it five times, and out of five, how many times does it succeed? And … maybe in several cases it hits 100% all the time, which is great, but in others not. And depending on how you change your context, it will influence which tests actually work or not. I find it personally helpful to think about this as error budgets, I give a set of tests … that I really care about, so it's only allowed … to fail minimally, and other pieces are okay. So that's how you have to think about testing context, you cannot do, like, exact testing all the time.”
Patrick Debois, Product DevRel Lead. Speaks from developer-relations work at Tessl and from teams he has seen adopt coding agents; a vendor employee, so he describes other organizations' practice second-hand and promotional framing is possible.
Tessl sells AI or agent tools or services, so it has a reason to publish flattering numbers about AI. The passage stays in the archive; read it with that in mind.
How this was checked
Checked against the source by a first reader, then confirmed independently by a second reader who fetched the source without seeing the first reader's notes (Independent review agent (Claude Sonnet), blind second pass from passage text and citation only, no repository access, 2026-11-04).
Around 13:04 in whisper and captions. The ellipses cover 'you know,' and 'and error budgets'. Whisper's 'which tests actually work' matches the passage; the captions have 'test', which is a plain mishearing.
How to cite this passage
Patrick Debois (Tessl), “Context Is the New Code”, AI Engineer (YouTube), 2026-05-03, at 13:04. https://www.youtube.com/watch?v=bSG9wUYaHWU Archived at https://the-ai-record.com/passages/tessl-testing-context-run-five-times-error-budgets-2026