The pyramid's core idea still holds: write tests at several granularities, and have fewer of them as they get broader and slower. Google's first-guess mix is 70% unit, 20% integration and 10% end-to-end, but they stress that the exact mix varies by team. The trophy (static analysis, unit, integration, end-to-end) was designed for JavaScript apps and puts most weight on integration tests because they resemble real usage; its author says it was not designed with microservices in mind. The honeycomb, from Spotify's engineering team, weights integration tests most heavily and is the version that backend and microservice teams cite. Fowler and Kent C. Dodds both note that the labels matter less than having fast, reliable tests that fail for useful reasons.

Sources: Google Testing Blog, Kent C. Dodds, Fowler, Spotify Engineering