Where does the testing pyramid place the majority of tests?

• A. Unit tests at the base, integration tests in the middle, end-to-end tests at the top.
• B. End-to-end tests at the base.
• C. Integration base.
• D. No tests are needed.

Answer: (A)

The idea being tested is that testing should be layered with the most numerous, fast tests at the bottom and progressively fewer, slower tests as you go up. Unit tests form the base because they test individual pieces of code in isolation. They’re quick to run, cheap to maintain, and give precise feedback about whether a small piece of logic is correct. Above them sit integration tests, which verify how different modules or components work together. They’re essential to catch issues that unit tests miss, but they’re slower and more complex to set up. At the top are end-to-end tests, which exercise complete user flows across the entire system. They are the slowest and most brittle, so you keep only a focused set of these to validate critical paths.

Putting it together, the majority of tests should be unit tests at the base, with integration tests in the middle, and end-to-end tests at the top. The other options run end-to-end tests too early, imply an illogical base, or suggest no testing at all, which doesn’t align with how the pyramid shapes testing effort and risk.