Acceptance Testing multiple NestJS Microservices by running them a single process communicating via a memory fake.

How to make sure that memory-based fakes really behave like the production implementations they replace

Writing memory-based black-box acceptance tests for NestJS apps, testing features rather than implementation details

Unit tests couple us to implementation detail, restrict refactoring and don't assert that features work. Prefer bigger-scoped tests.

Microservices incur significant overheads in costs of change, runtime and complexity. Start with a monolith and break it down when needed.

How I wrote tests for a VS Code extension that relies on a React.js WebView as its UI, using Playwright, Mocha and some HTTP hacking

Fakes are complete implementations of an API used to replace IO-bound adapters with memory-bound doubles to facilitate Acceptance Testing

Learning Tests are an easy and useful methodology for integration with new and unknown APIs, reducing stress and improving feedback times.

How I learned Flutter to create an iOS app for usage during concerts with my band, using TDD and Acceptance Testing.

How I used React with TypeScript and Firebase to build my own client management system, using TDD and Acceptance Testing.

Fixture test data create stale and outdated data, and make tests unreliable. Object Builders are a better way, here's how to use them.

How I helped Versatile remove fear of change in a key subsystem by introducing TDD and refactoring to Hexagonal Architecture.

When there are too many dirty pots and plates in the sink, it's impossible to clean them. It's the same with software and technical debt.

Prototypes are a lie; when it's good enough for production, it *becomes* production. Here's how to make them easily maintainable.

Hexagonal Architecture allows us to separate pure logic from external constraints and enables writing fast, integrative acceptance tests.