Testing & Quality

Unit, integration, E2E, contract tests, test data, coverage, and performance/chaos testing.

  • 4 Subtopics
  • 5 Tracked terms
  • Last 30 days Feed window

Inside Testing & Quality

Where the coverage comes from

The 50 sources publishing most on Testing & Quality over the last 30 days, out of 1,583 articles in the feed. Click a source for its articles on this topic and its profile.

  1. 1 @Thepracticaldev dev.to 1,164 articles 2+ hour ago 98%
  2. 2 Medium medium.com 109 articles 3+ hour ago 73%
  3. 3 @Hackernoon hackernoon.com 41 articles 2+ day ago 100%
  4. 4 @Startearly_Ai startearly.ai 11 articles 4+ day ago 100%
  5. 5 @Httweets hindustantimes.com 7 articles 2+ week ago 100%
  6. 6 The Manila Times manilatimes.net 7 articles 1+ week ago 100%
  7. 7 @Techbullion techbullion.com 7 articles 4+ day ago 100%
  8. 8 @Devopsdotcom devops.com 6 articles 3+ day ago 100% 2
  9. 9 @Dzoneinc dzone.com 6 articles 1+ day ago 100%
  10. 10 @Momenticai momentic.ai 6 articles 1+ week ago 100%
  11. 11 Cekura cekura.ai 4 articles 2+ day ago 100%
  12. 12 @Yahoofinance finance.yahoo.com 4 articles 4+ day ago 100%

What this topic collects on

An article joins this feed when it matches these terms. Each one is also a search of its own.

Latest in Testing & Quality

DEV Community
dev.to > tessainsley > where-ai-review-pays-the-codebase-matters-more-than-volume-233k

Where AI review pays: the codebase matters more than volume

2+ hour, 7+ min ago   (329+ words) The question I keep getting is how a team can review the growing volume of AI-generated code. Most answers start with throughput: faster review tools, more automated checking, larger batches. That assumes the problem is volume. The review I read…...

DEV Community
dev.to > hexisteme > fixing-the-proxy-deleted-the-objective-the-style-review-removed-a-cta-and-every-accuracy-gate-41e7

Fixing the Proxy Deleted the Objective: The Style Review Removed a CTA and Every Accuracy Gate Passed

2+ hour, 45+ min ago   (181+ words) Originally published on hexisteme notes. Closing this out took more than restoring the CTA. Four changes, each aimed at a different point where the same shape of failure could recur: And I split the downstream metric so "no data yet…...

DEV Community
dev.to > dhseadev > stress-test-pen-test-yes-tests-3e7c

Stress Test? Pen Test? Yes Tests!

4+ hour, 9+ min ago   (686+ words) Published on DHSeaDev. A hard-won lesson from shipping a browser-based TCG. When we stress-tested Prismwar, our original gate suite reported everything was fine. Then we ran a mutation campaign, and 31 out of 70 carefully crafted bugs survived without raising a flag....

DEV Community
dev.to > aurelionakamura > i-built-a-redos-scanner-that-proves-each-bug-offline-and-hands-you-a-verified-fix-3a5e

I built a ReDoS scanner that proves each bug offline — and hands you a verified fix

5+ hour, 14+ min ago   (442+ words) A regular-expression denial-of-service bug is a regex whose backtracking engine can be pushed into super-linear (often exponential) time by a short, hand-crafted input. The textbook shape is a quantifier inside a quantifier: The scary part is that these patterns look…...

DEV Community
dev.to > debashish_ghosal > the-model-wrote-the-right-rule-and-my-replay-rejected-it-the-extraction-vs-replay-split-4304

The Model Wrote the Right Rule and My Replay Rejected It: The Extraction-vs-Replay Split

4+ hour, 40+ min ago   (528+ words) CauterRule is an open-source sidecar that learns standing rules from repeated agent failures. It extracts lessons from trajectories, replay-tests them, and tries to separate reusable guidance from noisy overgeneralization. For two releases we treated "the pass rate is low" as…...

DEV Community
dev.to > balbaks > i-ran-my-scanner-against-5-real-cves-it-missed-4-then-i-reverted-my-own-fix-4dhk

I ran my scanner against 5 real CVEs. It missed 4. Then I reverted my own fix.

4+ hour, 51+ min ago   (657+ words) Why this post is different from the last one The last write-up in this series announced four tools. This one is about what happened when I stopped writing tests for my own tools and started checking one of them against…...

DEV Community
dev.to > abhishek_jain_cd78ebe598d > -3-ways-i-use-ai-to-auto-generate-playwright-locators-278c

# 3 Ways I Use AI to Auto-Generate Playwright Locators

5+ hour, 17+ min ago   (381+ words) If you've maintained a Playwright suite for more than a few months, you know the real cost isn't writing tests — it's the constant locator rot. A designer tweaks a class name, a component gets refactored, and suddenly a dozen tests…...

DEV Community
dev.to > mahirhir > my-checker-blamed-the-other-tool-and-the-defect-was-in-the-one-doing-the-blaming-3cpo

My checker blamed the other tool, and the defect was in the one doing the blaming

6+ hour, 15+ min ago   (601+ words) A verifier went red and named a neighbouring tool as the cause. Three of eight rows could not be matched, and the reason code said the rows had the wrong shape. Two things were wrong with that. The neighbouring tool…...

DEV Community
dev.to > antonioprosperi2svg > inside-beeladybug-visual-logic-collision-debugging-codepen-challenge-5bg5

Inside BeeLadybug: Visual Logic & Collision Debugging (CodePen Challenge)

6+ hour, 37+ min ago   (616+ words) 🐞 BeeLadybug (v2.4.0) — Visual Debugging & System Monitoring Following up on my previous post about BeeLadybug, I wanted to map out its internal architecture for this week's CodePen Challenge using a clean Mermaid flowchart! BeeLadybug serves as the primary visual inspector for BeeEngine…...

DEV Community
dev.to > yyygyf > a-csv-diff-should-reject-duplicate-ids-before-it-reports-changes-332l

A CSV diff should reject duplicate IDs before it reports changes

6+ hour, 15+ min ago   (105+ words) Authorship: this article and the linked toolkit were prepared by Codex on behalf of the account... Tagged with javascript, testing....