Microservices Architecture in Node.js - Automated Testing
summary
Adds live scooter location to a Node.js microservice, first stored in a DB, later moved to Redis and then extracted into a separate live-location service; unit tests (Jest, Mocha, Jasmine, Chai) mock internals and kept passing while a bug (sending state in request body instead of query string) slips into production. Recommends API tests for tolerance to implementation changes, integration tests to catch inter-service contract mismatches, CI/CD that runs unit/api/integration on push, plus canary, synthetic user testing, and fault injection in production.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker
- 3:28Microservices overview
- 5:21Testing challenges
- 10:40Video failure and bug
- 13:21Unit testing
- 17:36Limitations of unit tests
- 21:00API testing
- 26:06Integration tests
- 30:13Testing strategy
- 33:58Testing in production
- 38:42Conclusion and Q&A
related talks
44mMicroservices - the lean way (NodeJS)
52mMicroservices the Lean Way NodeJS
27mProgressive Microservices with NodeJS
48mMicroservices with NodeJS
42mMicroservice Testing Techniques
47mDivide and Conquer – Microservices with Node.js
43mBreak Up the Monolith: Testing Microservices
34mMicroservices using Node.js and RabbitMQ
