Philosophy

Stop Testing the Code, Start Testing the Product

November 10, 2026

A Manifesto for End-User Empathy

For the last two decades, software engineering has been dominated by a single religion: the cult of the unit test. We were taught in university, in bootcamps, and by industry thought leaders that the only way to guarantee a stable product was to achieve 100% test coverage. We spent hours mocking databases, stubbing network requests, and writing elaborate assertions just to prove that if you pass a specific string into a specific function, it returns a specific array.

And yet, despite millions of engineering hours poured into these tests globally, products still broke in production on a daily basis. The checkout button was rendered off-screen. The API response format changed, causing a silent frontend crash. The code worked perfectly according to the assertions, but the product was fundamentally broken for the user.

We spent 20 years testing implementation details while completely ignoring the user experience. We must stop obsessing over how the machine reads the code, and start obsessing over how the human reads the screen.

The Ephemerality of AI Code

In the era of human-written code, testing the implementation made some sense. Human code was incredibly expensive to write and notoriously slow to change. If an engineer spent three weeks writing a state management system, you wanted tests locked into that system because it wasn't going to change for years.

But Artificial Intelligence has fundamentally altered the economics of software development. AI writes code instantly, and more importantly, it refactors code instantly. If an AI agent can rewrite your entire frontend architecture over the weekend to migrate from Redux to Zustand, the code is no longer the anchor. The code is ephemeral. It is just a transient instruction set for the browser.

Why would you write a rigid unit test to assert that a generated function returns a specific nested object structure, if the AI is just going to completely rewrite that function tomorrow? If you tie your quality assurance to ephemeral code, you will spend all of your time updating tests instead of shipping features.

Bridging the Gap Between Engineering and Product

When you test the code, you are speaking a language that only engineers understand. You are arguing about test coverage percentages, cyclomatic complexity, and mock injections. But when you test the product, you are speaking the language of your users.

Intent-driven testing allows product managers, designers, and engineers to align on a single source of truth: what the user actually sees and interacts with. If the user can check out successfully, the architecture beneath it doesn't matter. The code is just a means to an end. It is time we stopped testing the means and started testing the end.

Author

Tanay Agarwal

Tanay Agarwal

Software Engineer