Testing Without Mocks in TypeScript

What your seat includes

Taught live in a small group, remote over video, inside EkoFlow, our open source development environment.

• Four weeks, two evenings a week, live in a small group over video
• Your own codebase converted one seam at a time, with the work between sessions reviewed by a person
• Nullable infrastructure you write yourself, so the database, the clock and the outside world answer to you
• An architecture test that keeps the design honest after you stop looking
• The measurements from our own conversion, so you know what it costs before you spend it
• The Solo plan on this platform, yours forever

The path

Each stage is built around doing the work, with a facilitator who asks rather than lectures. Read about how we teach

1. 1

   Week 1, The line: what is logic and what is infrastructure

   Why a suite full of mocks goes green while production burns: every mock is a guess about code you did not run. Draw the line through your own codebase, logic on one side and the world on the other, and write the first test that touches real logic with no test double anywhere. Sociable tests, and what they catch that isolated ones cannot.

2. 2

   Week 2, Nullables: your own code, switched off at the edges

   A thin wrapper around the database, the clock and HTTP, each with a createNull that returns the same class with its lowest level switched off. Configurable responses, so a test says what the world answers. Zero impact instantiation, so nothing touches a socket. Your tests stop mocking your dependencies and start running them.

3. 3

   Week 3, Output tracking and the tests spies used to fake

   What your code sends is a fact you can track rather than a mock you assert on. Output tracking for writes, emails and events, behaviour simulation for pushing the world back in, and the error paths, timeouts and race conditions you could never reach when the seam was a mock.

4. 4

   Week 4, Keeping it true: architecture, integration and speed

   One narrow integration test per wrapper, run against the real database, so the thin layer you trust is checked where it meets reality. An architecture test that forbids logic from reaching past the line. Then measure: what the suite costs now, what it cost before, and how to keep it in seconds as the codebase grows.