Describe the test pyramid and why unit tests form the foundation.

• A. Mostly end-to-end tests with few unit tests.
• B. Test types are interchangeable; order is irrelevant.
• C. Many fast unit tests at the base, fewer integration tests, and even fewer end-to-end tests; unit tests verify isolated logic cheaply.
• D. Unit tests are optional and can be skipped.

Answer: (C)

The test pyramid is about balancing test types by cost and speed: many fast, cheap unit tests at the base, fewer integration tests in the middle, and even fewer end-to-end tests at the top. Unit tests form the foundation because they validate isolated pieces of logic quickly and deterministically, often by isolating the unit from its dependencies. This makes them cheap to write, easy to run repeatedly during development, and very effective at catching regressions early. They also enable safe refactoring since changes to a unit’s internal implementation are checked against its expected behavior in isolation.

In contrast, integration tests verify how components interact, which is important but costlier and more brittle, and end-to-end tests exercise the entire system, offering broader coverage but at the highest cost and longest feedback loop. So the best approach is not to maximize high-level tests, but to place a large number of fast unit tests at the base, with progressively fewer tests as you move up the pyramid. The other options describe approaches that ignore the benefits of fast feedback and reliable isolation, or treat unit tests as optional, which undermines the practical advantages of this structure.