Fake GraphQL Query Generator

How to use

1. 1️⃣
   Choose your options above
2. 2️⃣
   Click Generate
3. 3️⃣
   Copy your result

Detailed instructions

1. Type your GraphQL type name into the Resource field using PascalCase, such as "Product" or "OrderItem".
2. Select an operation type from the dropdown: choose "all" for the full CRUD set, or pick a specific type like "mutation" to generate only those operations.
3. Set the Fields per Type number to control selection set size — use 3–5 for lean test fixtures or 7–10 for documentation examples.
4. Click Generate and review the output panel, which contains one complete GraphQL operation block per selected type.
5. Copy the output and paste it into your .graphql file, test fixture, MSW handler, or GraphQL Playground tab.

Use Cases

• •Generating MSW graphql.query() and graphql.mutation() handlers with realistic operation names like GetUser or UpdateOrder
• •Scaffolding Jest or Vitest snapshot fixtures before a backend GraphQL schema is finalized
• •Populating Insomnia or Postman GraphQL collections with sample operations for a new API resource
• •Creating concrete query and mutation examples for API reference docs without needing a live schema
• •Prototyping Apollo Client useQuery hooks in Storybook stories while the backend is still in development

Tips

• →Set resource to match your exact type name — the generator uses it as the operation name prefix, so "BlogPost" produces GetBlogPost and CreateBlogPost, keeping output paste-ready.
• →Use fieldCount of 3–4 when generating fixtures for unit tests; bloated selection sets make snapshot diffs noisy and harder to maintain.
• →Generate the "all" operation type first to get the full picture, then re-run with a specific type selected to get a cleaner block for documentation or a single test file.
• →The list query's pageInfo and edges structure is Relay-compatible — if you're using Apollo Client with a Relay-style cache policy, the pagination logic maps directly without modification.
• →Combine multiple runs with different resource names to build a complete mock API layer: generate User, Post, and Comment operations separately, then assemble them into a single MSW handler file.
• →If your schema uses snake_case field names rather than camelCase, do a quick find-and-replace on the output before committing — the generator always produces camelCase to match GraphQL convention.

FAQ