800 automated tests. Nobody looks at them.

Test automation isn't a goal in itself. Without a strategy, tests pile up, become flaky, and the team loses trust.

A team proudly shows us their suite. Eight hundred automated tests. Runs every night. Impressive.

Then we ask: and what do you do with the results? Silence. Someone says: "we don't really look at it anymore." Eight hundred tests, and nobody looking at them.

How it gets there

Not all at once. It happens step by step, and each step looks reasonable on its own.

It starts well: one enthusiastic person writes the first tests. They work, the team is happy. More tests get added, because more feels better. Nobody asks whether these tests still add anything, because adding tests feels like progress.

All those tests slow the suite down, so it gets scheduled to run overnight. Flaky tests start appearing, because nobody actively maintains the suite. The morning report is partly red, and the first few times someone checks. By the tenth time, nobody does.

One day the suite has become a ritual. It runs. Nobody looks. And when something breaks in production, it turns out afterward that a test could have caught it. If anyone had actually looked.

The four stages

We broadly see teams move through four phases. Do you recognise yours in any of these?

Experimenting

Loose tests, written by one person. Run locally, break often, nobody really trusts them. Better than nothing, but it doesn't scale.

Growing without control

There's a framework, there are conventions. Tests run in CI. But flaky tests and maintenance start to weigh, and the suite grows faster than the attention it gets.

Building trust

Stable suite, clear test pyramid, fast feedback. A failing test really does mean something is broken. The team trusts the outcome.

Quality as part of development

Testing sits in the definition of done. Every release passes the quality gate. Quality is no longer a phase, but a reflex of the whole team.

The question you should be asking

Not: how many tests do we have? But: do we trust them?

If your suite grows but the trust doesn't, you're not building a safety net. You're building maintenance.