<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/the-test-pyramid-is-a-relic-of-a-bygone-era-2lbugkx7z" -->

---
title: The Test Pyramid is a relic of a bygone era | daily.dev
description: Argues that the classic Test Pyramid, which recommends minimal end-to-end test coverage in favor of heavy unit and integration testing, is outdated. The...
canonical: https://daily.dev/posts/the-test-pyramid-is-a-relic-of-a-bygone-era-2lbugkx7z
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: The Test Pyramid is a relic of a bygone era | daily.dev
og:description: Argues that the classic Test Pyramid, which recommends minimal end-to-end test coverage in favor of heavy unit and integration testing, is outdated. The...
og:url: https://daily.dev/posts/the-test-pyramid-is-a-relic-of-a-bygone-era-2lbugkx7z
og:image: https://api.daily.dev/og/posts/2LBugkX7z.png
og:image:alt: The Test Pyramid is a relic of a bygone era
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# The Test Pyramid is a relic of a bygone era

**[QA Wolf](https://daily.dev/sources/qawolf)** · 6 min read · 0 upvotes · 0 comments

## Summary

Argues that the classic Test Pyramid, which recommends minimal end-to-end test coverage in favor of heavy unit and integration testing, is outdated. The pyramid was built around old constraints where E2E tests were slow, flaky, and expensive due to poor test infrastructure, not because E2E testing itself was flawed. With modern infrastructure—parallel execution, pre-booted environments, automatic data resets, and flake handling—E2E tests can be fast and reliable, making around 80% coverage of critical user flows achievable and worthwhile. The piece advocates running as many E2E tests as infrastructure allows, provided they run in parallel with minimal flakes.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.qawolf.com/blog/the-test-pyramid-is-a-relic-of-a-bygone-era>

## Questions this post answers

### What percentage of critical user flows should be covered by end-to-end tests?

Around 80% coverage of critical user flows is a reliable target for end-to-end testing. This level catches high-impact regressions without creating excessive maintenance burden, based on experience maintaining thousands of tests across hundreds of teams. Coverage gaps tend to appear below that threshold, especially in flows that cross multiple services or depend on stateful data.

_Teams weighing how much E2E coverage is enough can compare testing strategies and tools on daily.dev._

### Why do end-to-end tests get a reputation for being slow and flaky?

End-to-end test flakiness usually comes from the test environment, not the tests themselves. Sequential execution slows feedback, shared environments leave leftover data or session state that breaks other tests, and noisy logs make it hard to tell whether a failure is a real bug, a timing issue, or environmental flake, forcing teams into constant manual cleanup and debugging.

_Developers debugging flaky test suites can find infrastructure and testing discussions on daily.dev._

## Similar posts on daily.dev

- [The Test Pyramid Is a Lie \(and What I Do Instead\)](https://daily.dev/posts/the-test-pyramid-is-a-lie-and-what-i-do-instead--ak2scchgz) · Milan Jovanović · 40 upvotes · 0 comments
- [Medium](https://daily.dev/posts/medium-vglich5gj) · Medium · 0 upvotes · 0 comments

---

Tags: [#testing](https://daily.dev/tags/testing), [#cicd](https://daily.dev/tags/cicd)

[View this post on daily.dev](https://daily.dev/posts/the-test-pyramid-is-a-relic-of-a-bygone-era-2lbugkx7z)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"The Test Pyramid is a relic of a bygone era","url":"https://daily.dev/posts/the-test-pyramid-is-a-relic-of-a-bygone-era-2lbugkx7z","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/the-test-pyramid-is-a-relic-of-a-bygone-era-2lbugkx7z"},"datePublished":"2026-09-06T08:56:29.236Z","dateModified":"2026-09-06T11:25:59.635Z","description":"Argues that the classic Test Pyramid, which recommends minimal end-to-end test coverage in favor of heavy unit and integration testing, is outdated. The...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b0d9eed5023828824be53f6846edcbff?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b0d9eed5023828824be53f6846edcbff?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"QA Wolf","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"QA Wolf","logo":"https://media.daily.dev/image/upload/s--B9OvVIWd--/f_auto,q_auto/v1788684983/logos/qawolf?_a=BAMAMicg0","url":"https://daily.dev/sources/qawolf"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/the-test-pyramid-is-a-relic-of-a-bygone-era-2lbugkx7z","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"testing,cicd","timeRequired":"PT6M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"QA Wolf","item":"https://daily.dev/sources/qawolf"},{"@type":"ListItem","position":3,"name":"The Test Pyramid is a relic of a bygone era"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/the-test-pyramid-is-a-relic-of-a-bygone-era-2lbugkx7z#faq","mainEntity":[{"@type":"Question","name":"What percentage of critical user flows should be covered by end-to-end tests?","acceptedAnswer":{"@type":"Answer","text":"Around 80% coverage of critical user flows is a reliable target for end-to-end testing. This level catches high-impact regressions without creating excessive maintenance burden, based on experience maintaining thousands of tests across hundreds of teams. Coverage gaps tend to appear below that threshold, especially in flows that cross multiple services or depend on stateful data. Teams weighing how much E2E coverage is enough can compare testing strategies and tools on daily.dev."}},{"@type":"Question","name":"Why do end-to-end tests get a reputation for being slow and flaky?","acceptedAnswer":{"@type":"Answer","text":"End-to-end test flakiness usually comes from the test environment, not the tests themselves. Sequential execution slows feedback, shared environments leave leftover data or session state that breaks other tests, and noisy logs make it hard to tell whether a failure is a real bug, a timing issue, or environmental flake, forcing teams into constant manual cleanup and debugging. Developers debugging flaky test suites can find infrastructure and testing discussions on daily.dev."}}]}
```

