Testing a resolver's functions directly vs. executing queries against a built schema

This page summarizes the projects mentioned and recommended in the original post on /r/graphql

Our great sponsors
  • SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • TypeGraphQL

    Create GraphQL schema and resolvers with TypeScript, using classes and decorators!

  • I found this comment saying the way to test resolvers is by executing queries against a built schema. However, at my work we currently test resolvers by testing its functions directly like in this contrived example:

  • apollo-server-integration-testing

    Test helper for writing apollo-server integration tests

  • Thanks! Putting it like that it definitely makes sense. Now I am wondering if I should use something like https://github.com/zapier/apollo-server-integration-testing or execute vs. the schema. Any thoughts?

  • SurveyJS

    Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

    SurveyJS logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts