Fewer, better tests — and the judgement to know which ones.
Watch a free preview30-day refund, no questions asked
Training a team?
Volume pricing from five seats, with assignment, reminders and completion reporting included.
See team plans →Each maps to the same taxonomy your organization’s roles are defined in, so progress here moves your skill profile.
Most codebases have too many tests of the wrong kind. This course is about the judgement: what to test, at what level, and how to write suites that catch regressions without becoming the reason nobody wants to refactor.
3 modules · 12 lessons · 6h 9m
The judgement call that determines everything else.
Engineering Manager, Developer Experience, Northgate Labs
Ben's job is to make other engineers faster, which has made him a careful observer of where time actually goes. He teaches testing, tooling and code review — the unglamorous middle of software engineering — and he makes a persuasive case that this is where seniority actually lives.
1,884 reviews
Rolled this out to fourteen people. Twelve finished, which for us is unheard of. The pacing is right and nobody complained about the length, which is the real test.
Solid content, but I came in from a non-technical background and the assumed knowledge in module four caught me out. The prerequisites could be clearer about that. Everything before it was excellent.
Genuinely good, with one caveat: the first module moves slowly if you already know the basics. Skip to module two if you do — the rest is excellent and the case studies are specific rather than generic.
Types that catch real bugs without making the codebase unreadable.
Daniel Roth
62.8K
Measure, then fix — in that order, every time.
Daniel Roth · Ben Kowalski
47.1K
Designed around real postmortems, because that is where the lessons are.
Arjun Mehta
51.3K
