node-starter-kit VS javascript-testing-best-practices

Here is link number 1 - Previous text "API"

I'm deploying by either manually by running yarn deploy script or firing it via GitHub Actions when a PR is created, updated, or merged to the main branch.

Example: github.com/kriasoft/node-starter-kit

Nope. Just plain GraphQL.js + Knex.js (example), often typed manually since it's not where most of the time spend on when building an API server (though it can be automated via a scaffolding script if there are too many db tables). Generating TypeScript definitions off the actual db schema using knex-types (example).

Examples: - https://github.com/kriasoft/node-starter-kit - basic Node.js API starter kit - https://github.com/kriasoft/graphql-starter - monorepo template with GraphQL, React, Relay

I can help you developing a (GraphQL API) server for your web and/or mobile app as well as CI/CD workflows, optimized for serverless infrastructure in Google Cloud Platform. The initial version (first iteration) will be ready and live in under three days! Code examples:

https://github.com/kriasoft/node-starter-kit

You may want to browse through https://github.com/kriasoft/node-starter-kit to pick up some common patterns (e.g. transactional emails, OAuth 2.0 authentication, user sessions, views, db migrations, etc.).

😎 You want to take your JS testing skills to the next level, here is a nice repo -> javascript-testing-best-practices

Surprised nobody referred this

Yoni Golberg's JavaScript Testing best practices guide is always a good resource to consult, for both beginners and experienced developers: https://github.com/goldbergyoni/javascript-testing-best-practices

I really like how testing is done in Rails. Why did you choose the snapshots approach? I never have seen it for this purpose, they say it's bad practice even for the frontend (check testing practices for node btw), so, why?

JavaScript Testing Best Practices, by Yoni Goldberg is a GitHub repository. It gives good practices about testing.