Unit and component
Behaviour of one unit with its collaborators replaced. Fast enough to run on every change.
Quality is a system.
Not a phase after development, and not a larger end-to-end suite. A set of checks placed where the risk actually lives.
- Risk before coverage theatre
- Fast checks carry most of the load
- Journeys stay few and deliberate
Each layer has a job.
If two layers assert the same thing, one of them is waste or a lie.
Contract and API
The promise between producer and consumer, checked before a downstream system has to fail.
Integration
A real boundary, with controlled data. Not the entire company in one fixture.
End-to-end, smoke, and exploratory
A few journeys that prove the product holds together, plus human exploration where a script would only repeat itself.
The kinds of evidence worth naming.
We use these words precisely. A label without a decision is decoration.
Functional and regression
Does the change do what was agreed, and did it break a promise already in production?
Accessibility and visual
Can people operate it, and did the interface move in a way a screenshot would catch?
Performance, load, and stress
Only when a capacity or latency risk is real. A load test aimed at vanity is still waste.
Security and reliability
Abuse cases, permissions, and the behaviour of the system when a dependency is late or wrong.
What a better system feels like.
Not a promise of zero defects. A promise that the next defect is cheaper to see.
Earlier arguments
Requirement gaps show up in examples and contracts, not in a Friday incident.
Shorter diagnosis
A failure points at a layer. People stop rerunning the whole suite to feel busy.
Release notes a leader can trust
The open risks are listed. The checked risks are listed. Nothing is implied.
Questions we expect.
Does every product need every test layer?
No. The risk decides. A layer without a question is cost.
Is the pyramid a quota?
No. It is a way to talk about feedback speed and cost. Some systems need a different shape, and we say so.
Where do flaky tests belong?
In the engineering intelligence practice: visible history, a quarantine with an expiry, and a person who verifies the fix.
Bring the suite that nobody trusts.
We will tell you whether the problem is scope, data, environment, or a missing layer.