lecture 2 of 170 completed

Designing a repository several teams build in

One tests folder works for one team. At eight teams, structure becomes an ownership contract and config becomes composition.

What you'll learn

Why structure becomes an ownership question at scale
Why the extended test object is your framework's front door
How teams extend fixtures without touching shared code

A shared fixture gets a new required dependency. Two weeks later a team on the other side of the organisation has 200 failing tests and no idea why. Nobody was careless. The shared layer had no owner and no contract.

At senior level, repository structure is not about tidiness. It answers one question: who may change what, without asking?

The shape that works.

members only

Keep reading with the full course

The Foundations track and the first 5 lectures of each framework are free. This lecture is part of the paid course, which unlocks every lecture, all three frameworks, and downloads.

See the options →