How to properly test Nexus mutations and queries when code is broken out into a more piecemeal setup?

[haysclark]

I have created a PR in the "examples" repo that contains a new plugins-prisma-and-jwt-auth-and-shield-piecemeal folder. The project in this folder is a one-off of plugins-prisma-and-jwt-auth-and-shield and illustrates how to put Nexus under test, while also avoiding a monolithic Query or Mutation file. Each query and mutation is broken out into an individual file and has a unique "spec".

Unfortunately, one major testing challenge is that with so many test files, you can NOT run the tests successfully unless using jest --runInBand. Even with this setting, tests CAN fail from time to time if the DB gets bogged down or responds too slowly.

Additionally, there are some challenges accessing ctx properties added by runtime plug-ins. Possibly, plugins should have a more symmetrical setup and have a destroy options to teardown any objects created in a plugins create step?

If anyone has any feedback, I'd be greatly interested!

prisma-labs/graphql-framework-experiment-examples#89

[haysclark]

Adding issue pertaining to current Nexus testing challenges: https://github.com/graphql-nexus/nexus/issues/1326