Scaling Testing at a Startup: Integration Testing GraphQL Services with Jest
summary
BigSpring shows how Jest runs integration tests against TypeScript Node.js GraphQL resolvers using the Apollo test server (Zapier integration) and TypeORM talking to Postgres, restoring a production schema and spinning up Postgres and Redis in GitHub Actions. A recurring login-capitalization bug is reproduced and then prevented by tests. CI run time is about 2m13s, tests move coverage from near-zero to measurable percent, using Jest integration tests and a step to restore production schema for realistic validation.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 4:03Product and testing challenges
- 7:14Aspirations vs reality
- 9:19Impetus to improve
- 12:09Sustainable integration tests with Jest
- 14:39Scaling tests with GitHub Actions
- 17:28Measuring progress and goals
related talks
41mTesting GraphQL: From Zero To Hundred Percent
19mFunctional Testing of GraphQL APIs: Simple Checks That Catch Real Bugs
20mJest Testing
38mPerformance Testing sucks! How to get started testing RESTful APIs and GraphQL
38mHow to Stop Hating Tests with Jest, Supertest and Cypress
47mTest automation in backend projects
48mModern Testing Patterns
49mTesting a Large GraphQL API With Aplomb