Stephen Vickers

Testing isn’t exactly glamorous, but it can be the difference between “ship it” and “why is prod on fire?”. Here’s how I test real Deno services: unit tests, integration tests with a real database, and coverage; all without bolting on loads of extra tools.

Dependency injection in Deno isn’t some ivory‑tower pattern; it’s how you stop your codebase turning into a tangle of new calls and untestable side‑effects. Wire things up once, inject at the boundaries, and suddenly your Deno app starts behaving like a grown‑up system you can actually refactor without breaking everything.

After a decade of NodeJS and, well, everything that entails, I gave Deno a go because it spoke TypeScript natively and had a nice dinosaur logo. Now I’m a complete convert, my apps are better, my tests are better, and apparently now I want to talk about it as well.