Test automation in backend projects
summary
TypeScript microservices project grows from ~36 services with 5% coverage to ~180 services with 100% unit and integration coverage across new code, using Mocha/Chai, Cucumber/Gherkin examples and fixture generators. Tests run in minutes; team adopts beforeEach resets, moves samples out to fixture files, asserts call arguments and call counts, and adds linters. Outcome: many latent bugs (missing type checks, assertions hidden in mocks) are caught, code review quality improves and deployments become reliably safer.
AI-written summary · about
chapters (10)
- 0:00Introduction and motivation
- 3:35Starting with 100 percent coverage
- 8:32Maintaining test quality and confidence
- 15:31Improving test descriptions and structure
- 24:47Fixing inherited test anti-patterns
- 32:41Applying architecture principles to tests
- 34:05Why integration tests matter
- 41:32Managing data fixtures efficiently
- 45:03Static analyzers and logging
- 46:08Final checklist for test development
related talks
01h 28mShift-Left Testing
57mEnd-to-End Automated Testing in a Microservices Architecture
18mEffective Test Automation Framework Design
47mFull-Stack Test Automation
38mScaling Automated Testing & Architecture from Startup to Enterprise
50mFrontend-as-a-Service Automated Testing: Layers and CI Pipelines
45mBuilding a successful test automation architecture in a microservices environment
45mTesting the web without testers — success or failure