--- title: Why Shift Testing Left Part 2: QA Does More After Devs... description: Shifting testing left empowers more developers to run and maintain tests, without eliminating the role of QA. QA becomes a strategic leader in defining testing... canonical: https://daily.dev/posts/why-shift-testing-left-part-2-qa-does-more-after-devs-run-tests-oboxxecyg twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Why Shift Testing Left Part 2: QA Does More After Devs Run Tests | daily.dev og:description: Shifting testing left empowers more developers to run and maintain tests, without eliminating the role of QA. QA becomes a strategic leader in defining testing... og:url: https://daily.dev/posts/why-shift-testing-left-part-2-qa-does-more-after-devs-run-tests-oboxxecyg og:image: https://api.daily.dev/og/posts/oBOXxEcyg.png og:image:alt: Why Shift Testing Left Part 2: QA Does More After Devs Run Tests 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. # Why Shift Testing Left Part 2: QA Does More After Devs Run Tests **[The New Stack](https://daily.dev/sources/newstack)** · 6 min read · 6 upvotes · 2 comments ## Summary Shifting testing left empowers more developers to run and maintain tests, without eliminating the role of QA. QA becomes a strategic leader in defining testing strategy, maintaining automation, and optimizing test execution. Shifting left enhances development velocity, reduces bugs in production, and allows developers to verify their work immediately. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community discussion Top comments from developers on daily.dev. **@swapnilshirke** · 0 upvotes > This is absolutely right! **@viktor13** · 0 upvotes > The part this gets right that most shift-left writeups miss: QA's job moves from running tests to owning the testing system - strategy, flake policy, what's worth automating at all. The trap in practice: orgs shift the test-writing left but keep QA accountable for quality without authority over the process. If devs own the tests and QA owns the strategy, someone still has to own the flake budget - otherwise "more devs run tests" just means more unowned red builds. ## Similar posts on daily.dev - [Don’t just attend KubeCon \+ CloudNativeCon, Merge Forward your experience\!](https://daily.dev/posts/don-t-just-attend-kubecon-cloudnativecon-merge-forward-your-experience--l0rpp73x8) · CNCF · 1 upvotes · 0 comments - [Announcing H2 2026 KCDs](https://daily.dev/posts/announcing-h2-2026-kcds-m96goajm1) · CNCF · 1 upvotes · 0 comments - [Two months of Open Community Groups](https://daily.dev/posts/two-months-of-open-community-groups-asf52zhbs) · CNCF · 0 upvotes · 0 comments --- Tags: [#testing](https://daily.dev/tags/testing), [#qa](https://daily.dev/tags/qa) [View this post on daily.dev](https://daily.dev/posts/why-shift-testing-left-part-2-qa-does-more-after-devs-run-tests-oboxxecyg) ```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":"Why Shift Testing Left Part 2: QA Does More After Devs Run Tests","url":"https://daily.dev/posts/why-shift-testing-left-part-2-qa-does-more-after-devs-run-tests-oboxxecyg","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/why-shift-testing-left-part-2-qa-does-more-after-devs-run-tests-oboxxecyg"},"datePublished":"2024-05-15T16:18:24.188Z","dateModified":"2024-05-15T16:18:22.464Z","description":"Shifting testing left empowers more developers to run and maintain tests, without eliminating the role of QA. QA becomes a strategic leader in defining testing...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ca5319265c223286d6e205b272a6fd5e?_a=AQAEuiZ","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ca5319265c223286d6e205b272a6fd5e?_a=AQAEuiZ","isAccessibleForFree":true,"articleSection":"The New Stack","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":"The New Stack","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/newstack","url":"https://daily.dev/sources/newstack"},"commentCount":2,"discussionUrl":"https://daily.dev/posts/why-shift-testing-left-part-2-qa-does-more-after-devs-run-tests-oboxxecyg","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":6},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":2}],"keywords":"testing,qa","timeRequired":"PT6M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"The New Stack","item":"https://daily.dev/sources/newstack"},{"@type":"ListItem","position":3,"name":"Why Shift Testing Left Part 2: QA Does More After Devs Run Tests"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/why-shift-testing-left-part-2-qa-does-more-after-devs-run-tests-oboxxecyg","comment":[{"@type":"Comment","text":"This is absolutely right!","datePublished":"2026-06-05T09:32:16.997Z","url":"https://daily.dev/posts/oBOXxEcyg#c-RZtWV0dSQ","author":{"@type":"Person","name":"swapnil shirke","url":"https://daily.dev/swapnilshirke","image":"https://lh3.googleusercontent.com/a/ACg8ocIcYhcmg3nP3a6AeycGVremWEL-mqcQlNZJcXj7sRz60TTQ8EpI=s96-c"}},{"@type":"Comment","text":"The part this gets right that most shift-left writeups miss: QA’s job moves from running tests to owning the testing system - strategy, flake policy, what’s worth automating at all. The trap in practice: orgs shift the test-writing left but keep QA accountable for quality without authority over the process. If devs own the tests and QA owns the strategy, someone still has to own the flake budget - otherwise “more devs run tests” just means more unowned red builds.","datePublished":"2026-07-15T08:25:13.877Z","url":"https://daily.dev/posts/oBOXxEcyg#c-uILeo5rxV","author":{"@type":"Person","name":"Viktor","url":"https://daily.dev/viktor13","image":"https://lh3.googleusercontent.com/a/ACg8ocIc26dkBXmdcP-rbl8qJslbOVNRfu_MNGt-1M53PirnENWvvyytKQ=s96-c"}}]} ```