Conversation
…nt users New post at /blog/coding-agent-test-fixtures-that-cant-lie/. Written by the agent from Drew's two January 2025 GraphQL test-fixture posts, not from a live session; the post says so up front and carries aiWritten: true. Thesis: a CLAUDE.md rule against mocking the function under test is an input the agent weighs, but a mock-resolver type generated from the GraphQL schema is not. A wrong fixture fails to compile. Links both of Drew's posts as the detailed method and his typechecking-graphql-mock-resolvers repo. Hero image composed with PIL: a green-but-meaningless test next to a fixture with one letter wrong that tsc rejects. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
✅ Deploy Preview for effulgent-alfajores-60f09f canceled.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
An agent-written post that reframes your two GraphQL fixtures posts for people who now have agents writing their tests. Draft only, nothing published.
Title: Make your coding agent write test fixtures that can't lie
Description: Agents write tests that pass and prove nothing. A GraphQL mock resolver type-checked against your schema can't: a wrong fixture fails to compile. (145 chars)
URL: /blog/coding-agent-test-fixtures-that-cant-lie/
The pitch: a CLAUDE.md rule against mocking the thing under test is an input the agent weighs. A
MockResolverstype generated from the schema is not. Both your posts are linked as the detailed method, plus thetypechecking-graphql-mock-resolversrepo. Nothing is re-voiced or put in your mouth; the post says out loud that it was written from your two posts, not from a session.Autocomplete evidence: "claude code test" and "coding agent test" both return full suggestion lists ("claude code testing agent", "coding agent test prompt"), so the searcher's nouns are agent + test.
"graphql test fixtures", "mock resolvers graphql" and "how to make claude write good tests" return zero suggestions, so GraphQL stays out of the title and lives in the description, H2s and tags instead.
Needs your eyes:
{ AbilitiesListItem: { effect: () => "paralyzed" } }and post 2's tighter type requires the top-level entry to be a function. I show the second form and flag the difference. Tell me if I read that wrong.AbilitesListItemmisspelled and the tsc error. No error code shown, so nothing to get wrong.Verified:
npx astro buildclean, post page and homepage card with the AI badge both present, strikethrough renders as<del>, no em dashes.🤖 Generated with Claude Code