Question 1

How do I set up GraphQL Faker to mock a GraphQL API?

Accepted Answer

Install it globally via npm, run 'graphql-faker --open' with an SDL file (or use the default), and use the interactive editor to add directives like @fake to fields. This starts a local server on port 9002 serving the mocked API.

Question 2

GraphQL Faker vs Apollo Server mocking: which should I use?

Accepted Answer

GraphQL Faker is better for declarative, no-code mocking using SDL, while Apollo Server offers more programmatic control with custom resolvers. Choose GraphQL Faker for quick setup, Apollo for complex logic.

Question 3

Can GraphQL Faker handle mutations with fake data?

Accepted Answer

Yes, you can apply @fake or @examples directives to mutation fields in the SDL to simulate backend responses. However, it's static mocking and doesn't support state changes across requests.

Question 4

How to extend an existing GraphQL API with GraphQL Faker?

Accepted Answer

Use the --extend flag with the URL of the real GraphQL server and provide an SDL file with additional types or fields decorated with directives. It proxies requests, merging real and fake data seamlessly.

Question 5

Is GraphQL Faker good for automated testing?

Accepted Answer

It's useful for development and manual testing, but its static data generation may not suit complex test cases requiring dynamic behaviors. For automated tests, consider tools like Jest with custom mocks.

Question 6

What are the best alternatives to GraphQL Faker for mocking?

Accepted Answer

Alternatives include Mock Service Worker (MSW) for intercepting network requests, GraphQL Tools' mock functions, and built-in mocking in Apollo Server. Each varies in flexibility and setup complexity.

GraphQL Faker

What is GraphQL Faker?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions