Software Engineering

Test-Driven Development

Test-driven development as a working discipline rather than a claim, across unit, integration and end-to-end, on both halves of a full stack application.

The course project

The Tested Application

An application built test-first, with a suite that runs in CI and a written argument for what is deliberately not tested.

course

9 modules · 18 lessons

Each module ends with a practice test, a graded build, and a step of the course project.

Part I: The Discipline

Why Test

Not to prove it works. To be able to change it later.

Red, Green, Refactor

Write the test first, and find out what you actually meant.

Anatomy of a Good Test

Arrange, act, assert, and one reason to fail.

Part II: The Layers

Unit, Integration, End to End

Three sizes of test, and how many of each.

Testing Python and Django

pytest, fixtures, and the test client you already met.

Testing React

Test what a person can see and do, not what the component holds.

Part III: Boundaries

Test Doubles

Standing in for the parts you should not really call.

Coverage and Confidence

A measurement, not a target.

Part IV: In Practice

Tests in the Pipeline

A suite nobody runs is a suite nobody has.

All courses