--- title: "Discussion on \"Twelve Green Tests, One Missing Key\" | Hashnode" description: "Discussion on \"Twelve Green Tests, One Missing Key\". Two of the twelve asserted the broken wire format — so the suite had no way to disagree with the bug." url: "https://hashnode.com/posts/twelve-green-tests-one-missing-key/6af6fab07163ab7dc34e34b2" --- [Feed](https://hashnode.com/feed) / Discussion # [Twelve Green Tests, One Missing Key](https://mediaforge-studio.hashnode.dev/twelve-green-tests-one-missing-key?utm_source=hashnode&utm_medium=feed) Two of the twelve asserted the broken wire format — so the suite had no way to disagree with the bug. 9h ago · 5 min read · mediaforge-studio.hashnode.dev Read the article - [#testing](https://hashnode.com/tag/testing) - [#typescript](https://hashnode.com/tag/typescript) - [#webdev](https://hashnode.com/tag/webdev) - [#programming](https://hashnode.com/tag/programming) ## Written by [dafili](https://hashnode.com/@vaultcheck) @vaultcheck · Chengdu, China [View profile](https://hashnode.com/@vaultcheck) Indie developer building command-line tools for Linux auditing and B2B data extraction. Indie developer building practical CLI tools for Linux auditing and B2B data extraction. I care about zero-dependency design, honest engineering, and building tools that solve real operational pain points. Currently maintaining Vaultcheck and NPILift. ## Responses 1 Markdown supported · ⌘↵ to post [Tarun Sharma](https://hashnode.com/@101beardo) [5h ago](https://hashnode.com/posts/twelve-green-tests-one-missing-key/6af6fab07163ab7dc34e34b2/comment/6af72e8a6de7ba9a52435126) To your question: asserting on the parsed object is where this kind of drop hides. One more layer that would have caught it is typing the outbound tool with the provider SDK's type instead of reading it through Record, since the cast erases the shape and the compiler cannot see a missing type or function key. A contract test that validates the serialised body against the published tool JSON schema covers it too.